Skip to main content
S
suresh876654578888
Level 1
April 25, 2026
Solved

Is there a Debug/Preview Mode in Adobe Tags (Launch) similar to GTM Debugger? How to Set It Up?

  • April 25, 2026
  • 5 replies
  • 74 views

I am familiar with Google Tag Manager’s preview/debug mode and how it helps validate tag firing, data layer, and events.

I am now working with Adobe Tags (Adobe Launch / AEP Data Collection) and want to understand:

  • Is there an equivalent to GTM’s preview/debug mode in Adobe?
  • What tools are recommended for debugging (AEP Debugger, browser console, etc.)?
  • How do you set up and use the debugger step-by-step?
  • How can I test dev/staging environments similar to GTM preview mode?

Any documentation, tutorials, or best practices would be helpful.

Best answer by manpreetkaur27

Just to add to what others have mentioned, for debugging in a prod environment, it’s best to use the Adobe Experience Platform Debugger. 

Sharing the doc here in case it helps:
https://experienceleague.adobe.com/en/docs/experience-platform/debugger/home

5 replies

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
April 25, 2026

Hi ​@suresh876654578888 

for debug mode on a prod environment, you best use the Adobe Experience Platform debugger, in which you can replace the current launch library with your non-prod library.

from there on, I am typically relying on Omnibug (https://omnibug.io) to validate the requests, not just of Aa but pretty much any other marketing pixel out there .

Cheers from Switzerland!
    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    April 26, 2026

    I agree with ​@bjoern__koth  there is no “traditional” preview mode… but the deployment structure of Adobe Launch has multiple Dev libraries, one Staging and one Prod… 

     

    Each rule and data element have their own revision number, you can build a library using the combination of items you need to test, and use that build to test.

     

    You can use the Adobe Experience Platform debugger, or I prefer to use a different plugin called Resource Override which means I don’t have to set it up each time… I can leave it on as long as I want.

      manpreetkaur27
      Adobe Support
      manpreetkaur27Adobe SupportAccepted solution
      Adobe Support
      April 27, 2026

      Just to add to what others have mentioned, for debugging in a prod environment, it’s best to use the Adobe Experience Platform Debugger. 

      Sharing the doc here in case it helps:
      https://experienceleague.adobe.com/en/docs/experience-platform/debugger/home

      H
      hegi90
      Level 3
      April 28, 2026

      And the most simple way to debug is 

      _satellite.setDebug(true)

      which shows you which rule is triggered or where the condition was not met. 

      manpreetkaur27
      Adobe Support
      manpreetkaur27Adobe Support
      Adobe Support
      April 29, 2026

      Hi ​@suresh876654578888 
      I’m just following up to check whether any of the responses have helped address your question. If so, please consider marking the best answer.

       

      Terms & ConditionsAccessibility statement

      Loading footer...