Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!
SOLVED

UAT test for email campaign in ACC

Avatar

Level 1

Hello community,

 

We are deploying this ACC for our company, and the first channel integration is Email. In the UAT testing, ADOBE recommend us to do the test with their domain. Do you think that it's good? Why shouldnt we do the UAT test with our own domain? 

 

What are the usual test cases that you have done in this phase of UAT? 

 

Looking forward to the answers,

many thanks

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi @Beth-March2023 

That's correct, domain delegation is only for production environment and not lower environments. In lower, Adobe provides a UNIQUE sender domain across all its customer base.

What performance do you want to test: marketing communications or transactional communications. In both cases, we recommend that you use the "Test SMTP" delivery property to avoid sending physically the email by mistake. With such option, deliveries will be prepared but not sent. Most of our are also deploying a Safety Net Typology Rule on lower environments to authorise ONLY a subset of email addresses purely used for testing.

More on the delivery property in ACS: https://experienceleague.adobe.com/docs/campaign-standard/using/administrating/configuring-channels/... 

For ACC the explanation is here

https://experienceleague.adobe.com/docs/campaign-classic/using/sending-messages/key-steps-when-creat...

Hope this helps,

Thanks

Denis

View solution in original post

4 Replies

Avatar

Correct answer by
Employee Advisor

Hi @Beth-March2023 

That's correct, domain delegation is only for production environment and not lower environments. In lower, Adobe provides a UNIQUE sender domain across all its customer base.

What performance do you want to test: marketing communications or transactional communications. In both cases, we recommend that you use the "Test SMTP" delivery property to avoid sending physically the email by mistake. With such option, deliveries will be prepared but not sent. Most of our are also deploying a Safety Net Typology Rule on lower environments to authorise ONLY a subset of email addresses purely used for testing.

More on the delivery property in ACS: https://experienceleague.adobe.com/docs/campaign-standard/using/administrating/configuring-channels/... 

For ACC the explanation is here

https://experienceleague.adobe.com/docs/campaign-classic/using/sending-messages/key-steps-when-creat...

Hope this helps,

Thanks

Denis

Avatar

Level 1

Thanks Denis! 

 

I have a few more questions: 

1. First, if testing with ADOBE unique domain, how can we validate that our domain works well in sending? 

2. Is there any other case, or testing with ADOBE's unique domain is the only way? 

3. For email testing, we want of course, to test two main things: Data (how the data flow, can we retrieve the right information..), and creative (if they render well in different email clients). 

I am wondering if we have to create a big sample data or 10-20 profiles is enough. 

4. Does this SMTP testing mean that we can test with real data, but the emails won't be sent physically? 

 

Many thanks again!

Beth 

Avatar

Employee Advisor

1. for testing the domain, you need to verify/test this on the PROD instance

2. for STAGE environments, the Adobe domain is the only option

3. for the creative part 10-20 profiles would definitely be enough. For the data flow rather not

But for data flow testing, I would rather recommend to do this on PROD but in a workflow where the E-Mail activity is disabled.

4. yes