Skip to main content
Navigation

Troubleshooting

Common issues and how to resolve them.

TagDragon tab doesn’t appear in DevTools

If you can’t find the TagDragon tab after installing:

  1. Make sure Developer mode is enabled in chrome://extensions/
  2. Verify the extension is loaded (not removed or disabled)
  3. Restart Chrome completely — close all windows and reopen
  4. Open DevTools (F12) and check the tab bar for TagDragon
  5. If the tab appears but is collapsed, click the >> arrow in the DevTools tab bar to find it

No requests are being captured

If the panel opens but shows no requests:

  • DevTools must be open — TagDragon only captures requests while DevTools is open on the inspected page. The extension popup shows a warning when DevTools is closed.
  • Navigate or interact — Requests appear when you navigate to a new page, reload, or trigger tracking events (click, form submit, add to cart, etc.)
  • Check the Pause button — If capture is paused, click the play button to resume
  • Check provider filters — Open the provider filter popover and make sure the providers you expect aren’t hidden

A provider isn’t being recognized

If a request from a known provider appears as “Unknown”:

  1. The URL pattern may not match — check the Provider Reference for supported URL patterns
  2. The provider may have changed their tracking endpoint — open an issue to report it
  3. You can check the raw request URL in the Query tab to verify the endpoint

Extension conflicts with other tools

TagDragon uses the Chrome DevTools API and should not conflict with other extensions. However, if you experience issues:

  • Obveesance / Dataslayer / Ghostery — These tools may also intercept network requests. They generally coexist fine with TagDragon, but if you see unexpected behavior, try disabling them temporarily
  • Other DevTools extensions — If another DevTools panel extension is causing issues, try disabling it to isolate the problem

Performance issues on high-traffic sites

If TagDragon feels slow with many requests:

  1. Open Settings (gear icon) and configure:
    • Max requests limit — Lower the maximum (default: 500)
    • Auto-prune — Enable it to automatically remove old requests
  2. Use the Provider Filter to hide providers you don’t need
  3. Use Compact Rows mode for a denser, faster display
  4. Use Pause to stop capturing when you’re analyzing specific requests

Adobe Environment Switcher isn’t working

If the Adobe Environment Switcher doesn’t show environments:

  • The page must load an Adobe Launch (Tags) container — the switcher detects the library URL automatically
  • Legacy DTM containers are not supported — only Adobe Launch/Tags
  • The Launch property must be configured with multiple environments (DEV, ACC, PROD) in Adobe Experience Platform
  • Try reloading the page after selecting an environment
  • Check that no other extension is overriding the same requests

DataLayer tab shows no pushes

If the DataLayer tab is empty:

  • The page must use one of the supported data layer sources (GTM, Tealium, Adobe, Segment, or W3C digitalData)
  • DevTools must be open before or during page load — data layer pushes are intercepted in real-time and can’t be retroactively captured
  • Try reloading the page with DevTools open
  • Check that the source isn’t filtered out in the DataLayer filter bar

If the Consent Panel changes don’t seem to take effect:

  • Some sites cache consent state in localStorage or sessionStorage — try clearing those via the Application tab in DevTools
  • The consent override injects scripts into the page; if the page has strict CSP headers, the injection may be blocked
  • Some CMPs override consent state on every page load — you may need to apply the override after the CMP initializes
  • Try reloading the page after applying overrides

Extension not working in incognito mode

By default, Chrome extensions are disabled in incognito mode:

  1. Go to chrome://extensions/
  2. Find TagDragon
  3. Click Details
  4. Toggle Allow in incognito to enabled
  5. Reopen incognito windows

DataLayer correlation tab is empty

If the Correlation sub-tab shows no network requests linked to a push:

  • Forward window too short — By default, TagDragon looks 2 seconds ahead for network requests triggered by a push. If your site has slow tag loading, increase the forward window in DataLayer settings
  • Push happened before DevTools opened — Correlation only works for pushes captured in real-time. Reload the page with DevTools open
  • Provider is hidden — If the provider that should fire is hidden in the Provider Filter, its requests won’t appear in correlation results

Some requests show as “Unknown”

If tracking requests appear without a provider name:

  • The URL doesn’t match any of TagDragon’s 59 built-in provider patterns
  • The provider may use a new or changed endpoint — check the Provider Reference for supported patterns
  • You can contribute a new provider on GitHub

TagDragon panel is blank after Chrome update

If the panel appears empty after a Chrome browser update:

  1. Go to chrome://extensions/
  2. Find TagDragon and click the Refresh button (circular arrow)
  3. Close and reopen DevTools
  4. If still blank, remove and re-add the extension via Load unpacked from the latest GitHub release

Still having issues?

If none of these solutions help:

  1. Check the FAQ for more answers
  2. Open an issue on GitHub with:
    • Your Chrome version
    • TagDragon version
    • Steps to reproduce
    • Any error messages in the DevTools console

Was this page helpful?

Start typing to search docs...