Articles in this section

Blueprints for Campaign Prioritization


Blueprints are a method of creating dynamic Audiences. A collection of records are sent through a series of conditions and decisions to identify more specific segments of records. Campaigns are able to target the segments identified within the Blueprint.

This article describes the process of using Blueprints for Campaign Prioritization and defines the process of Campaign Prioritization.

The example built in this article describes the process of creating a Blueprint to separate records for multiple Campaign contacts. Records will be processed through the Blueprint conditions and contacted through the appropriate Campaign.

Segment and Message must be activated in order to use Blueprints for Campaign Prioritization.


Table of Contents

Campaign Prioritization and Campaign Segmentation


Building a Blueprint

Creating a New Blueprint

Adding a Node

Target Node

Merge and Filter


Moving and Reordering

How Blueprints Execute

Using Campaigns


Campaign Prioritization and Campaign Segmentation

There are two similar concepts that combine Campaigns and Blueprints for more advanced functionality.

Campaign Prioritization uses Blueprints to divide an Audience into specific segments. Different Campaigns are used to target individual segments.

Campaign Segmentation uses Blueprints to divide Audiences into specific segments. The Blueprint is used to identify Personalization content within the same Campaign. Each Segment enabled the appropriate content to render in the Campaign contact.

For more information on Campaign Segmentation, read this article.



Building a Blueprint

Creating a New Blueprint

To create a new Blueprint, navigate to Segment → Blueprints. Click Create Blueprint in the top right. This opens up a dialog box to create a Blueprint.



A Blueprint can be created from scratch. This is done in a very similar manner as creating an Audience. A Blueprint can also be created from an existing Audience. This will use the same conditions and configurations as the selected Audience.

If creating a new Blueprint, the SQL query must be typed out. There is no option to use the Drag-and-Drop Builder. If not familiar with SQL, then create an Audience in Message → Data Management → Audiences and use the Drag-and-Drop Builder to build a new Audience. Then, when creating a Blueprint, select the newly-created Audience to import the query for use.


For more information on creating Audiences with the Drag-and-Drop Builder, follow the first section of the End-to-End Newsletter Creation article.

If creating a new SQL query, the Blueprint will open in the SQL tab view. This is where the data is selected from the external datasource.



If creating a new Blueprint with an existing Audience, the Blueprint will open in the Blueprint view.



This is the Blueprint flowchart interface. This interface is used to create decisions on how data should be handled and targeted. The interface works as a flowchart.

Adding a Node

To add a new Node in the Blueprint, click the + sign beneath the Starting Population. Nodes are each item added to a Blueprint flowchart. There are two kinds of starting Nodes.



Target Node

The circular logo is a Target Node. A Target Node is a method of creating an IF/ELSE statement. A Target Node creates one conditioned Node and one non-conditioned Node.

If the Starting Population does not show the number of records, the Refresh button (next to the Preview button) must be clicked. This returns a count of records accessible by the SQL query.

Clicking the Target Node button creates two more items on the screen. Configure the options for the Target Node.



The Target Name is a descriptive name of the Node. It is a best practice to name the Node with a title that describes all the conditions within the Node. This way, when all Nodes are built, a user does not have to open each individual Node to understand the functionality.

Under the Segments section, configure the conditions to select customers. The example here will detect if a customer has completed their profile setup. The column within the datasource that holds this information is called “ProfileComplete” and is a boolean value. The condition entered here is ProfileComplete = 1.



The Target Node can be as simple as one condition or more complex with multiple conditions. Name the set of conditions and the Node before saving.



Two Nodes are created when choosing the Targeted Node option. The Node that is not greyed out is the conditioned Node. This is the node that applies the logic to target records. The Node that is greyed out is the ELSE Node. All records that do not meet the condition will progress down this path.

Give the greyed-out Node an appropriate name.

This is the basic idea of a Blueprint. A series of Target Steps that filters records down into desired groups.

Click the Refresh button to view the count of records that meet the conditions for each Node.

Click the Target Node button multiple times to add more Conditioned Nodes to the Blueprint. Nodes must be built in order of priority. The visual order of the Nodes are the order that records evaluation conditions.

Clicking the + sign beneath the Target Node. More options are available than before.



Merge and Filter

The options beneath the Target Step now include Merge and Filter options. The Merge option allows multiple paths to combine into one.

The Filter option has a more specific use. The Filter is a Node that can group customers based on the Segments of the previous Node. For example, if a Target Node selects records from the East coast states, the Filter node can group those resulting records into different regions. All records where the state is equal to “GA, FL, SC, NC” are considered the Southeast Region. Using the Filter node, results from a Target Node can be divided into more specific groups.

A Target Node may select records with the use of a large number of conditions. The Filter is a way to split the records

Continue using Target Nodes to filter records to the appropriate target audience.




The Split option is a way to divide records based on a percentage allocation. The Split can divide records among many different nodes. When configuring the Split, the chosen percentages must add up to 100%.



Splits are added to Target Nodes to randomly distribute records through multiple paths. Saving the Split configuration will add Nodes to the Blueprint.



Use Refresh to display the number of records that each Node receives.


Moving and Reordering

With the update of Accelerator 21.2.0, new tools to move and reorder Nodes were introduced. These tools, accessible by the menu in the top left of each node, provide options for changing the order of Nodes. This is important because the order that the Nodes are arranged is the order that they are executed.




The options across the top of the Node, expanded and collapsed by the menu button, perform the following actions:

Move to a New Level is an option that allows a Node to be moved into a different hierarchy level. Using this feature will put the targeted node after any active nodes but before any of the grey, default nodes. Use the other ordering tools to make sure the Node is evaluated in the correct place.

Add Neighbor Node is an option that creates a new Node to the right of the selected Node.

Shift Left shuffles the Node one position to the left, if available.

Shift Right shuffles the Node one position to the right, if available.


How Blueprints Execute

Blueprints follow Waterfall Logic. Nodes are evaluated in order. This means that the organization of Nodes is important. Here is an example:



The starting population for this Blueprint is 12.7k records. The first set of Target Nodes detects if records have completed their profile or not. All records that are marked as not having a complete profile are filtered to the right node. This is the final Node for non-complete records. Those records are done being processed as there is no other node beneath the greyed out node.

Records that are marked as having a complete profile are filtered to the left node. In the above example, there are 6.3k records that are marked with complete profiles.

These records continue through the flowchart. Target Nodes are evaluated in order from left to right. Any records that meet the Welcome Email Target Node will stop processing logic and can be accessed by Campaigns through the Welcome Email Target Node.

Any records that do not meet the criteria of the Welcome Email Target Node will continue to the next Node. This process will repeat until the record matches a Node’s conditions and has no further Nodes to process.

Save the Blueprint.

When selecting an Audience or Blueprint within a Campaign, it can be difficult to tell the two apart. It is recommended that Blueprints contain some identifier in the name. For Example, a Blueprint titled “Weekly Onboarding” would benefit from the following name: “BP Weekly Onboarding”


Using Campaigns

After configuring a Blueprint, Campaigns are used to target records and contact them. Open Campaigns by navigating to Message → Delivery → Marketing.

More instructions on creating Campaigns can be found at the article End-to-End Newsletter Creation.

Create a new Campaign. When selecting an Audience, choose the Blueprint.

To select which records to contact from the Blueprint, select Filter Blueprint on the Campaign Overview screen.



Clicking this button opens the Blueprint.



Each Node of the Blueprint has a checkbox in the top left. Select the Node of records to target. The records selected by that Node and all child Nodes will be targeted by the Campaign. If selecting the “If Profile Complete” Node, all records that pass through that Node are targeted by the Campaign. The child Nodes themselves do not need to be checked if a parent Node is checked.



In the above example, the “Path A” Node is checked. This will only target records that are sent to this Split Node.

Once all the appropriate Nodes are checked, save the selection. When launching the Campaign, only records returned by the checked Nodes are contacted.

Multiple Campaigns can access the Blueprint. They can target the same Nodes or different Nodes.






Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.