Debugging for Server Side Implementation in Headless architecture - Is there any requirement for QA urls/mboxTrace/mboxDebug | Community
Skip to main content
U
user94030
New Participant
June 22, 2022
Solved

Debugging for Server Side Implementation in Headless architecture - Is there any requirement for QA urls/mboxTrace/mboxDebug

  • June 22, 2022
  • 1 reply
  • 1791 views

Hi Team,

 

We have implemented Target Server side using Delivery API and our website follows AEM headless architecture. Wanted to check for the below queries -

1. Will there be any usecases where we will require QA urls to preview the experience or since its server-side and headless, QA urls will not make sense.

2. Will debugging parameters like mboxTrace/mboxDebug/mboxDisable will also not be required in case of server-side and headless implementation

 

Regards,

Disa

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 Gaureshk_Kodag

Hi @user94030 

 

I think, even if it's server side headless implementation you'll still need QA URLs to test experience before taking activity live and debugging parameters should also work.

1 reply

Gaureshk_Kodag
Gaureshk_KodagAccepted solution
Employee
June 23, 2022

Hi @user94030 

 

I think, even if it's server side headless implementation you'll still need QA URLs to test experience before taking activity live and debugging parameters should also work.

U
user94030Author
New Participant
July 1, 2022

Hi @gaureshk_kodag ,

 

Is there any documentation on how to use QA urls in case of using Delivery API. From my observations, APIs don't return any content until you publish it so not sure how we can leverage QA urls.

 

Regards,

Disa

 

Gaureshk_Kodag
Gaureshk_Kodag
Employee
July 1, 2022

Hi @user94030 ,

Here at the end you'll see QA mode pls check if that helps

https://developers.adobetarget.com/api/delivery-api/#operation/execute

 

 

 

 

    Terms & ConditionsAccessibility statement

    Loading footer...