A seed list allows you to test where an email will land across different email clients and devices as well as see how your campaigns are rendered in different browsers and email clients.
The seed list feature in Blueshift requires you to upload a list of users (for example, internal users), and subsequently use it in a campaign. When the campaign is launched, it sends a copy of the first message to each user in the seed list.
The seed list behavior for different types of campaigns is as follows:
| One-time campaigns | First message from the campaign. |
| Recurring campaigns | First message for each run. |
| Segment triggered campaigns running daily | First message every day. |
|
First message from the campaign on launch. When you pause and re-launch a campaign, the first message post re-launch is sent to the seed list users. However, an additional 6 hour timeout window is applied from when the last seed list was sent. For example, if the seed list was sent at 10 AM and the campaign was paused and re-launched at 2 PM, the seed list is sent at T+6 hours, which is at 4 PM. If you re-launch the campaign at 5 PM, the seed list is triggered upon the next send because the timeout window has elapsed. |
Set up seed lists
- Follow the same Customer List setup process but select "Seed list" as the option.
- Associate the Seed list to use with the campaign in the Monitoring section of the Properties tab for the campaign.
Subject lines for seed list emails
The Subject line for an email sent to the seed list has the following format:
- Seed List - {$original subject line} : ( {$seed list name}, {$customer email address} )
- BCC - {$original subject line} : ( {$customer email} )
For example, if the Subject line is "Best scooters in town", the customer email address is 'firstname.lastname@company.com' and the seed list is 'Default Seed List', the subject line has the following format:
- Seed List - Best scooters in town: (Default Seed List, firstname.lastname@company.com)
- BCC - Best scooters in town: (firstname.lastname@company.com)
Comments
0 comments