Journey start

To create a campaign journey, go to Journeys > Campaigns and click +CAMPAIGN. Add a Name for your campaign and click CREATE CAMPAIGN.

The Campaign Studio opens on the Journey Tab.

Start trigger

The Journey start trigger is the starting point for a journey. Every outbound campaign will have a start trigger. When you create a campaign, it contains only the start trigger.

The start trigger specifies who (which user) can enter the journey.

For segment-based campaigns, i.e., one-time, recurring, and segment-triggered campaigns, you must specify at least one triggering segment. If a user meets the segment criteria, they qualify for the journey.

You can view the count of eligible users for the selected segment in the start node of the journey builder.

Multiple triggering segments

One-time, recurring, and segment-triggered campaigns support multiple triggering segments. To enable multiple triggering segments for campaigns on your account, contact your CSM or Blueshift Support.

Once enabled, the Journey Start node lets you define two segment groups:

Include — Customers in any of these segments qualify for the campaign.
Exclude — Customers in any of these segments are excluded, even if they also belong to an included segment.

You must select at least one Include segment. Only user-targeting segments can be combined. Transaction segments cannot be mixed with user-targeting segments or selected in multiples.

Transaction segments and exclude logic

When a transaction segment is used in Include, you cannot add user-targeting segments to Exclude. Transaction segments operate on individual transaction records, not user profiles, so exclude logic does not apply across entity types.

You can include at most one transaction segment in the Include group.
You cannot add user-targeting segments to the Exclude group when a transaction segment is used in Include.

Example:

Include: Transaction segment (Recent Purchases)
Exclude: Not allowed — user segment (Unsubscribed Users)

Workaround: To exclude specific users, add exclusion conditions within the transaction segment definition, or apply filters using a Decision Split in the campaign journey.

When more than one Include segment is selected, the Journey Start node displays Multiple Segments instead of an individual segment name.

Reporting for multiple triggering segments

When a campaign uses two or more Include segments, Blueshift automatically creates a combined segment that represents their union. Campaign metrics, such as sends, clicks, and impressions, are reported for that combined audience.

Reporting at the campaign level is unchanged.
If you use one Include segment, reporting is unchanged, even if you add Exclude segments.
In reports that show segments, campaigns that use multiple Include segments are shown as Multiple Segments.
Metrics are reported for the combined audience across the selected Include segments.

Reporting for campaigns with multiple triggering segments

One-time, recurring, and segment-triggered campaigns support multiple triggering segments. To enable multiple triggering segments for campaigns on your account, contact your CSM or Blueshift Support.

For more information, see Multiple triggering segments.

Action-based campaigns

For action-based campaigns (i.e., event-triggered campaigns), you must specify the action that enables a user to enter the journey. You can select from (a) an API call, (b) an event, or (c) an interest alert.

Note

You cannot use the "view", "pageload", or "identify" events to trigger an event-triggered campaign. Instead, you can create a segment of users based on the view event (for example, users who have viewed a particular item) and use this segment in a segment-based campaign.

Global campaign filter

For event-triggered and segment-triggered campaigns, you can specify campaign-level filter criteria that will be applied to all triggers in the journey using an AND logic.

The global campaign-level filter is applied to every trigger in the campaign.
If the trigger also has filter criteria defined, the campaign-level filter is applied using AND logic.
When a trigger includes a delay, the user is evaluated for the trigger only after the delay completes.
You can use attributes from the triggering event or from the customer in the filter criteria.

Note: These filters aren't available for API or interest-alert-triggered journeys.

Active Journeys filter

The Active Journeys filter is a campaign-level filter that lets you control whether users can enter this journey based on their concurrent activity in other journeys. Use it to manage cross-journey overlap and avoid sending conflicting or redundant messages.

Configure the filter under the Filters tab in the Journey Start node. You can select journeys by name or by tag, and apply one of the following match conditions:

Matches all of these — The user must be active in all the selected journeys to enter this journey.
Matches none of these — The user must not be active in any of the selected journeys to enter this journey.
Matches any of these — The user must be active in at least one of the selected journeys to enter this journey.

Example scenario

In a Cart Abandonment Recovery journey, add the Post-Purchase Thank You and Win-back Campaign journeys under Matches none of these. Users currently active in either of those journeys will not enter the Cart Abandonment Recovery journey to avoid overlapping messaging.