One way to ensure that a base template, campaign template or journey template is correctly defined is to send yourself or other people proofs: rendered versions of the template, as it will appear to contacts when sent as part of a campaign.
Table of contents
Instructions
You can send proofs from two places in Iterable:
- When editing a template, campaign content or journey content
- When using the Preview with Data screen for a base template, campaign template or journey template
To send a proof, click the Send Proof button:
This button provides four options:
To Yourself - Sends a proof of the template to you (the user who is currently logged in to Iterable), using data from your Iterable profile to resolve any merge parameters.
-
To an Internal List - Sends proofs to the users included on an internal list of your choosing.
-
As Random Users - Sends proofs to you (the user who is currently logged in to Iterable), but using data from random contacts in your project.
-
To Another Address - Sends a proof to the email addresses that you specify.
IMPORTANT
- Merge parameters such as
{{viewInBrowserUrl}}and{{unsubscribeUrl}}, which produce links, do not behave in proofs as they do in campaigns. - When sending proofs from the Preview With Data screen, Iterable uses the loaded user data when sending the proof, including any manual edits you have made. This allows you to modify the data and send proofs to preview how it will look in a live campaign.
- In-app message and push notification proofs ignore Selective In-App or Selective Push settings (unless they're sent while creating or editing a campaign).
Comments
0 comments
Article is closed for comments.