Skip to main content
Navigation

Use Cases

TagDragon is built for the daily workflows of tag implementers, QA engineers, privacy officers, and analytics developers. Here are the most common use cases and how TagDragon addresses each.

QA & Implementation Testing

Verify tags fire correctly before deployment.

  • Catch broken events — See if tracking requests return 4xx/5xx status codes immediately
  • Missing parameters — Decoded view shows exactly which parameters are sent and which are missing
  • Firing order — Timestamps and sort options reveal whether events fire in the expected sequence
  • Provider isolation — Use the Provider Filter to debug one tag at a time without noise

Workflow:

  1. Pause capture → perform the interaction → resume → review only the triggered requests
  2. Use the status code filter to find non-200 responses
  3. Compare Decoded parameters against your tracking specification

Privacy & GDPR/CCPA Auditing

See exactly what data leaves the browser.

  • Full payload visibility — Every tracking request is decoded showing all parameters including user IDs, client IDs, and personal data
  • Consent mode testing — Override consent states via the Consent Panel and verify which tags respect the settings
  • User ID tracing — Use the User ID filter to find all requests associated with a specific identifier across providers
  • Cookie audit — See which cookies are set and clear them for clean retesting

Workflow:

  1. Open Consent Panel → set all categories to Denied
  2. Navigate the site → verify no user-identifiable data is sent
  3. Grant specific categories one by one → observe which providers activate
  4. Export results as JSON for compliance documentation

Performance Review

Identify redundant tracking and oversized payloads.

  • Request volume — Status bar shows real-time request count and total size
  • Slow endpoints — Average duration metric identifies bottlenecks
  • Payload sizes — Check individual request sizes in the detail view
  • Auto-pruning — Prevents memory issues on sites with hundreds of tags

Workflow:

  1. Navigate to the target page with TagDragon open
  2. Monitor the status bar for total size and average duration
  3. Sort by size/duration to find the heaviest and slowest requests
  4. Use the Provider Filter to identify which tools generate the most traffic
  5. Export data for a performance report

Adobe Stack Debugging

Debug Adobe Launch, Analytics, and Target in one panel.

  • Environment switching — Redirect between DEV/ACC/PROD Launch environments at the network level
  • Adobe-specific decoding — eVars, props, events, and hierarchy variables decoded from sc.omtrdc.net requests
  • ECID inspection — See Experience Cloud ID requests and visitor identification
  • AEP Web SDK — Decode Alloy (alloy.sendEvent) interactions with full XDM schema visibility

Workflow:

  1. Open Adobe Environment Switcher → select DEV
  2. Reload the page → verify Launch loads the DEV build
  3. Check decoded Adobe Analytics requests for correct eVar/prop mappings
  4. Compare Target requests to verify mbox parameters
  5. Switch to ACC/PROD and verify differences

Data Layer Validation

Ensure your data layer pushes conform to team conventions.

  • Validation engine — Define rules for required keys, key types, and forbidden keys
  • Watch paths — Pin specific dot-notation paths for focused monitoring
  • Group by source — See pushes organized by GTM, Tealium, Adobe, Segment, or digitalData
  • Network correlation — See which network requests were triggered by each push

Workflow:

  1. Open the DataLayer tab
  2. Define validation rules for required event properties
  3. Navigate through key user journeys
  4. Review flagged pushes for missing or incorrect data
  5. Use Watch Paths to monitor critical e-commerce properties

Migration Testing

Verify parity when migrating between providers or platforms.

  • Side-by-side comparison — Use the Provider Filter to show only the old and new provider
  • Parameter mapping — Decoded views reveal parameter differences between providers
  • Firing verification — Confirm both old and new tags fire for the same user interactions
  • Export for analysis — Download both providers’ requests for offline comparison

Common migrations:

  • Universal Analytics → GA4
  • Adobe DTM → Adobe Launch
  • Segment client-side → server-side
  • Tealium iQ → GTM

Was this page helpful?

Start typing to search docs...