UAT test for email campaign in ACC | Community
Skip to main content
September 30, 2022
Solved

UAT test for email campaign in ACC

  • September 30, 2022
  • 1 reply
  • 1887 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by costa_n11

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/configuring-email-channel.html?lang=en#:~:text=in%20the%20message.-,SMTP%20test%20mode,-Use%20the%20Enable 

For ACC the explanation is here

https://experienceleague.adobe.com/docs/campaign-classic/using/sending-messages/key-steps-when-creating-a-delivery/steps-sending-the-delivery.html?lang=en

Hope this helps,

Thanks

Denis

1 reply

costa_n11Adobe EmployeeAccepted solution
Adobe Employee
September 30, 2022

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/configuring-email-channel.html?lang=en#:~:text=in%20the%20message.-,SMTP%20test%20mode,-Use%20the%20Enable 

For ACC the explanation is here

https://experienceleague.adobe.com/docs/campaign-classic/using/sending-messages/key-steps-when-creating-a-delivery/steps-sending-the-delivery.html?lang=en

Hope this helps,

Thanks

Denis

September 30, 2022

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 

September 30, 2022

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


Thank you very much for a quick response, Ramon!