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:
- Verify that your direct mail provider is really sending the communication.
- Receive the mail at the same time and in the same conditions as your customers.
- Keep an exact copy of the mail that was sent.
- Check that your client list is not misused by your direct mail provider. Indeed, if any other communication is sent to your test profile's address, your client file may have been used without your knowing. This is why the test profile's address should only be used to this purpose.
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:
- Check that your message was successfully sent.
- Get and keep an exact copy of your message.
- Track when it was sent and received.
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, for any enriched fields in a message, the corresponding additional data is randomly picked from a real targeted profile and assigned to the trap test profile. For more on enrichment, see this example .