Seed list

The seed list is a list of recipients that can be targeted in every campaign without requiring additional segmentation. Add your internal team members to this list to ensure internal teams receive all campaigns.

Enable seed list

To enable this functionality in your project, navigate to Channels > Engagement Rules & Categories and enable the Seed List toggle, then click on Save. A new Seed List page will be listed under Settings.

Add users to seed list

To add a user to the seed list, navigate to Data > User Profiles and click the Options menu > Add to Seed List.

Alternatively, a profile can be added to the seed list directly from the profile details page via the Actions menu.

Once added, navigate to Settings > Seed List to see all the users included in this list.

Remove users from seed list

To remove a user from the seed list, you can click the Options menu> Remove from Seed List either from Data > User Profiles page or from Settings > Seed List page.

You can also remove them directly from the Profile Details page under the Actions menu.

Target seed list in a campaign

Once the seed list is enabled for the project, the option to send to the seed list will be available on the Segment tab under the Send to Seed List section. Check the box to send the campaign to all recipients included in the seed list.

Seed List in Single Stage and Multistage Campaigns

Seed lists works differently in single-stage and multi-stage campaigns.

In a single-stage campaign, the seed list applies to the whole campaign. Seed list users receive the campaign on every channel they are reachable on, regardless of the campaign’s segment. If the campaign targets specific apps or websites, seed list users need a device registered on one of the selected apps or websites. If the campaign uses A/B testing, seed list users always receive Variant A.

In a multi-stage journey, the seed list only affects entry to the workflow. Seed list users skip the campaign’s segment and audience conditions and are added at the start of the workflow. Seed list users still need to be reachable to enter. If the campaign targets specific apps, seed list users need a device registered on one of those apps. See Application Targeting under Build a multistage journey for more information.

After entry, seed list users move through the workflow like any other user. They are not sent a copy of every message in the workflow. The messages a seed list user receives depend on the actions in the workflow and on that user’s own profile data and behaviour.

For example, a workflow contains the following actions:

1. A message action sends a push on day 1.

2. A delay action holds users for one day.

3. A decision action checks whether the user is in the segment has not deposited.

   • Yes: a message action sends a second push.

   • No: the journey ends.

Two seed list users enter this workflow:

• Seed list user A makes a deposit after the day-1 push. At the decision action, they are not in the has not deposited segment. They follow the No path and do not receive the day-2 push.

• Seed list user B does not make a deposit. At the decision action, they are in the has not deposited segment. They follow the Yes path and receive the day-2 push.

Both users are on the seed list, but they receive different messages. This happens because their profile data is different when they reach the decision action.

Other actions in the workflow also apply to seed list users in the same way as other users. For example:

• Decision and multi-decision actions: These evaluate each seed list user’s own profile data and behaviour. Each seed list user follows only the path that matches. They are not sent down every path.

• Split actions: These send seed list users down a random path, in the same way as other users. Seed list users do not automatically follow a particular path.

• Delay actions: Seed list users wait like everyone else.

• Cancel journey: If a seed list user triggers the cancel event, they leave the workflow.