Send proofs send-test-deliveries
Once your message content has been defined, you can preview and test it by sending proofs to test profiles. If you inserted personalized content, you can check how this content is displayed in the message, using test profile data.
To detect possible errors in the message content or personalization settings, send proofs to test profiles before sending it to the target audience. A proof should be sent each time a change is made, to validate the latest content. Sending proofs is an important step in validating your campaign and identifying potential issues. The proof recipients can check various elements such as links, opt-out links, images, or mirror pages, as well as detect any errors in the rendering, content, personalization settings and delivery configuration.
Simulate content with test profiles simulate-content-test-deliveries
Before sending a proof, make sure you define a target audience for you delivery. Learn more
To start testing your message content:
-
Edit the content of your delivery.
-
Click the Simulate content button.
-
Click the Send proof button to send proofs.
-
Select your proof recipients.
Depending on the message channel, proofs can be sent to the following types of recipients:
-
For SMS and emails, you can use test profiles, which are specific additional recipients in the database. You can also use the substitution from main target mode, which sends the proof to an email test address or phone number, and use personalization data of an existing profile. This allows you to experience the message as the recipients would, giving you an accurate representation of the content that the profile will receive.
-
For push messages, you can use subscribers, which are fictitious subscribers added to the database. They are created in the Campaign console. Learn more in Campaign v8 (client console) documentation
Detailed configuration for each mode is available below.
-
Use test profiles test-profiles
Test profiles are additional recipients in the database. They are created from the Customer management > Profiles menu. Learn more
The steps to send proofs to test profiles are detailed below.
-
From the content of your delivery, click the Simulate content button, and the Send proof button.
-
From the Mode drop-down list, choose Test profiles to target fictitious recipients that will receive the proof or SMS delivery.
-
If you have already selected profiles to preview the message in the content simulation screen, those profiles are pre-selected as proofs recipients. You can clear your selection and/or add additional recipients using the Add test profile(s) button.
-
When browsing the test profile or profile lists, you can use filters to refine your search. For example, you can define a rule to find all test profiles whith the Prospect status. Learn how to add rules using the query modeler.
-
To also send the final message to the recipients of the proof, select the Include test population in the main target option.
-
Once the test profiles are selected, you can send the proof.
Substitute profile data substitution-profiles
Use profile substitution to send proofs to a specific email address or phone number, while displaying data from an existing profile of the Adobe Campaign database. This mode can only be selected if the audience of the delivery has been defined.
To substitute profile data from the main target, follow the steps below:
-
From the content of your delivery, click the Simulate content button, and the Send proof button.
-
From the Mode drop-down list, choose Substitute from main target to send a proof to a specific email address or phone number while displaying data from an existing profile.
note caution CAUTION If you have not selected an audience for your delivery, the Substitute from main target option will be greyed out and you will not be able to select substitution profiles. -
Click the Add address button and specify the email address or phone number that will receive the proof.
note note NOTE You can enter any email address or phone number. This allows you to send proofs to any recipients, even if they are not users of Adobe Campaign. -
Select the profile from the target you defined for your delivery to use as substitute. You can also let Adobe Campaign select a random profile from the target. The profile data from the selected profile will be displayed in the proof.
-
Confirm the recipient and repeat the operation to add as many email addresses or phone numbers as needed.
-
To also send the final message to the recipients of the proof, select the Include test population in the main target option.
-
Once the substitution profiles are selected, you can send the proof.
Send proofs to app subscribers subscribers
When designing with push notifications, proofs can be only sent to your app subscribers. To select them, follow the steps below.
-
From the content of your push delivery, click the Simulate content button, and the Send proof button.
-
If you have already selected subscribers to preview the delivery in the content simulation screen, those profiles are pre-selected as test subscribers.
You can clear your selection and/or add additional subscribers using the dedicated button.
-
To also send the final push notification to the test subscribers, select the Include test population in the main target option.
-
Once the subscribers are selected, you can send the proof.
Send the proof send-test
To send the proof to the selected recipients, follow the steps below.
-
Click the Send proof button.
-
Confirm the sending.
-
Send as many proofs as necessary until you have finalized the content of your delivery.
Once done, you can prepare and send your delivery to the main target. Learn how in the dedicated sections below:
Access sent proofs access-test-deliveries
Once the proofs have been sent, you can access their logs from Simulate content screen.
These logs allow you to access all the proofs sent for the selected delivery, and to visualize specific statistics related to their sending. Learn how to monitor delivery logs
You can also access sent proofs from the delivery list, like any delivery.
