Does TagDragon send any data to external servers?
No. All processing happens locally in your browser. No data is sent to any external server. TagDragon does not include any analytics or tracking of its own. See Privacy & Security for full details.
Which browsers are supported?
TagDragon is built for Chrome (version 102+) using the Manifest V3 API. It works in all Chromium-based browsers that support Chrome extensions, including Microsoft Edge, Brave, Opera, and Arc.
Can I install it from the Chrome Web Store?
Yes! Install TagDragon directly from the Chrome Web Store listing — click Add to Chrome and you’re done.
Why are some requests not decoded?
A request may not be decoded if:
- The URL doesn’t match any of the 59 supported provider patterns
- The request is not a tracking request (e.g., API calls, static assets)
- The provider’s response format has changed
You can see all raw requests regardless of decoding status.
How do I add a new provider?
See the Contributing section in the GitHub repository. You create a provider file implementing the Provider interface, add it to the PROVIDERS array, and rebuild the extension.
Does it work in incognito mode?
Yes, but you need to explicitly enable TagDragon in incognito mode. Go to chrome://extensions/, find TagDragon, and check Allow in incognito.
How does auto-pruning work?
When enabled in Settings, TagDragon automatically removes the oldest requests when the total count exceeds the configured threshold. This prevents memory issues on high-traffic sites. Default threshold is 500 requests.
Can I customize the theme?
Yes. Click the theme toggle (sun/moon icon) in the toolbar to switch between dark and light mode. Your preference is saved and persists across sessions.
How is TagDragon different from ObservePoint or Dataslayer?
TagDragon is a free, open-source Chrome DevTools extension focused on real-time tag debugging. Unlike ObservePoint (enterprise auditing platform) or Dataslayer (tag debugging tool), TagDragon:
- Costs nothing and requires no account
- Runs entirely locally — no data leaves your browser
- Includes a built-in DataLayer inspector, consent panel, and Adobe environment switcher
- Is open source — you can audit the code and contribute providers
TagDragon is best for daily debugging workflows. For enterprise-scale tag auditing with scheduled scans and reporting, ObservePoint remains the appropriate tool.
Does TagDragon work with Firefox or Safari?
No. TagDragon is built on the Chrome DevTools Protocol and Manifest V3, which is specific to Chromium-based browsers. It works in Chrome, Microsoft Edge, Brave, Opera, Arc, and any browser that supports Chrome extensions.
Can I use TagDragon on production websites?
Yes. TagDragon is a passive observer — it only reads network requests and does not modify page content or make its own requests. The only exception is the optional Adobe Environment Switcher, which redirects Launch library URLs. You can safely use TagDragon on any website without affecting its behavior.
How long does TagDragon store captured data?
TagDragon stores data only for the current session. When you close DevTools or the browser, captured requests are discarded. Your settings, hidden provider preferences, and Adobe environment selections persist in chrome.storage.local, but no request data is retained between sessions.
Where is extension data stored?
All settings, hidden providers, and preferences are stored in chrome.storage.local. This data is local to your browser and never leaves your machine.
How do I report a bug or request a feature?
Open an issue on GitHub. Include your Chrome version, TagDragon version, and steps to reproduce for bugs.