Content Blocks within a Portal (Formerly Mailing Snippets)

Much like mailings and decision letters, portals can feature content blocks (formerly mailing snippets). The data point that should reference the content block must be placed in a query within the portal. Rather than using conditional logic or Liquid markup within the portal, a content block can dynamically display the content that might otherwise require a variety of filters and if/elseif statements.


Before adding a content block to a mailing, first create the content block content.

In the portal that should display the content block content, first ensure that the export that will be used within the content block merge field is present in one of the portal's queries. To insert a content block as a merge field within a Portal:

  1. Navigate to the appropriate portal view where the content block should be displayed. This may be the default view of the portal.
  2. Insert a new Static Content block or edit an existing block. Navigate to where the content block content should be merged.
  3. Enter the following text:
    where NAME OF EXPORT is the name of the export in the portal query, and KEY OF content block is the key of the content block that contains the codes to merge into the message.
  4. Click Save.

For example, it may be desired to dynamically merge in Staff Assigned details, images, and other content related to the staff assignment within a portal. The merge field for this content block may resemble the following:

{{program | snippet: "faculty_signatures"}}

Internally, the static content block may then be formatted similar to:


When previewing this portal, the content block merge field dynamically displays the content block corresponding with that record's data currently present in the "staff_assigned" export. For instance, if a sample record has a staff assignment of Gonzo Muppet, the content block with information on this Staff Assigned displays:


Was this article helpful?
4 out of 7 found this helpful