When using traps, the message is sent to the test profile just as it is sent to the main target, as a means to identify whether your client file is being used fraudulently.
Traps were originally designed for direct mail deliveries. They allow you to:
For more on adding traps to a direct mail’s audience, see Adding test and trap profiles.
For the other communication channels, you can add trap test profiles to your main target in order to:
To use a test profile as a trap, it must be included in your message’s audience.
When defining a message’s audience:
From the Test profiles tab, select a test profile. Make sure that it has Trap as the intended use.
Once your message content is ready, click the Prepare button. See Preparing the send.
Make sure you selected a main target. Otherwise, your message cannot be sent.
Click the Confirm button. See Confirming the send.
The message is sent to the main target and to the test profile.
You can use traps when sending transactional messages. In this case, the test profile will receive one message per event configuration. For more on transactional messaging, see this section.
When using a test profile as a trap, any enriched fields within a message will have their corresponding additional data randomly selected from a real targeted profile and assigned to the trap test profile. However, be aware that if the real targeted profile is excluded due to typology rules applied during the first message preparation, the delivery preparation will fail. This failure occurs because the enriched field values cannot be substituted for the trap profile. Consequently, exclusion typology rules might not apply correctly to the real recipients.
To prevent this situation, avoid using trap test profiles simultaneously with filtering or fatigue rules in your transactional typology. Learn more on enrichment. For more on enrichment, see this example.