You can select any one of the contacts in your database and see exactly how your email will look when it has been personalized with their properties.
Search field - On the Contact preview pane, the search field is dynamic, and previously used contacts are stored in the list. In this way you can create text contacts that correspond to the contacts you are targeting with your campaign and make sure that the email looks great for all of them.
If the contact does not have any data for the relevant field the email content editor cannot generate it.
In this case the contact preview only displays that the email template cannot be compiled.
Personalization rules in contact preview
The Contact preview for Personalization rules is the same as the rule preview. The Personalization rule's preview is calculated every time when a Personalization rule is saved or refreshed, which changes then the Contact preview, as well.
Discrepancies can occur between personalization rule preview and the Contact preview:
- The product availability is checked during contact preview, while it is not checked during the rule preview.
- In the Contact preview, the selected contact does not make a difference in the previewed recommendation results, so there is no contact level personalization. Therefore, it does not matter which contact you choose in the contact selector.
- The already purchased items will not affect the results either.
To summarize, what you can check with the previews is the product level filtering criteria that was specified in the Personalization Rule builder.
Contact preview notifications
In case of any occurring issues when generating the previews for the products based on your personalization rules, contact preview can display troubleshooting notifications. These notifications help you better troubleshoot any preview problems.
A notification informs you in a short note about an issue or the cause of the failed preview attempt. There are specific type of notifications for about issues that could lead to a failed contact preview generation.
Error messages
| Trigger | Error Notification Text | Cause of the Issue |
|---|---|---|
| Job Not Found | Recommendations are being calculated at the moment. Try again later. |
A recommendation job is not found for the given Personalization rule. |
| No Destination Table | Recommendations are being calculated at the moment. Try again later. | The BigQuery data table does not exist for the given recommendation job. |
| Job Not Ready | Recommendations are being calculated at the moment. Try again later. | The latest recommendation job is still running. It is in waiting or in progressing status. |
| Job Out Of Date | Recommendations are being calculated at the moment. Try again later. | The latest recommendation job was created before the Personalization rule was saved. |
| Job Failed | Something went wrong. Try again later. | The latest recommendation job has failed. |
| Recommendation error | Something went wrong. Try again later. | An error happened during receiving the recommendations from the Big Query database. |
Warning messages
Warning messages can raise your awareness of potential issues.
| Trigger | Warning Notification Text | Cause of the Issue |
|---|---|---|
| Rule Not Found | The personalization rules used in the campaign could not be found. Replace the personalization rules used in your campaign, then reload the preview. |
The requested Personalization rule is not found. |
| Unsupported Basic Logic | Invalid personalization rules were added to the campaign. Edit the personalization rules used in your campaign or use a different personalization rule, then reload the preview. | The Personalization rules Basic Logic is unsupported. This edge case could become relevant if a new Base logic rule is introduced which causes the preview generation to fail. |
This feature is only available in the VCE editor:
- Only Twig syntax is supported. Personalized content which uses $pers$ and %% placeholders will not be displayed.
- Personalized content from external events will not be displayed.
- Block targeting is only supported with the contact data field in the contact preview. Segment based block targeting will not be displayed correctly in the contract preview.