Zero migration off Tealium.
Keep utag.js, your existing load rules, your data-layer extensions, your CMP integration. We add a separate <script> tag to <head> and start observing.
no rip-and-replaceTagDrishti vs Tealium iQ Audit
Tealium can’t watch Tealium go down.
Tealium iQ’s built-in tag audit and load-rule reporting both run inside the iQ container. When iQ has a problem (slow utag.js delivery, a misfired load rule, a CMP gating Tealium itself), the same system that’s broken is the system reporting on it. TagDrishti runs as a separate, 12 KB script outside the iQ container.
# for tealium iq customers · works alongside utag.js · no migration
# the_circular_dependency_problem
iQ ships strong governance for what fires through utag.
Load rules, extensions, scope configurations, the consent layer. The audit view tells you which tags are mapped, what triggers them, and what data is in the data layer. That’s a configuration audit. It is not a runtime monitor.
# the_gap
If utag.js itself fails to load (CDN incident, CSP block, ad blocker classification, third-party cookie deprecation), iQ has nothing to report because utag never executed. The dashboard says “no recent events,” which looks identical to “low traffic.” A real-user monitor running outside the container sees the same pageview without utag, and that absence is the signal.
Where each script sits in the page.
┌─ Browser pageview ───────────────────────────────────────────┐
│ │
│ <head> │
│ ├── tagdrishti.js ◄── independent monitor │
│ ├── utag.js ◄── Tealium iQ container │
│ │ ├── extensions, load rules │
│ │ ├── GA4, Meta, LinkedIn, TikTok tags │
│ │ └── audit/reporting also runs here │
│ └── ... │
│ │
│ If utag.js fails: iQ audit blind, TagDrishti alert <2s │
│ If iQ console fails: same, we already shipped the events │
└──────────────────────────────────────────────────────────────┘
What Tealium iQ does well.
iQ’s load-rule editor, scope configuration, and the consent gating in the EU-mode profile are excellent for governing what should fire. The data-layer extension model is genuinely powerful for normalising inputs across vendors. We do not replace any of that. What we add is a runtime witness that operates independently of iQ, so configuration correctness and runtime delivery are checked separately.
Side-by-side, capability for capability.
| Capability | Tealium iQ Audit | TagDrishti |
|---|---|---|
| Detects when utag.js itself fails to load | No (the audit runs inside utag) | Yes. Independent script, alerts in <2s |
| Real-user runtime monitoring | Limited to events that reach utag | Every real-user pageview, every session |
| Multi-TMS coverage | Tealium iQ only | GTM, Adobe Launch, Tealium iQ, Segment, Piwik PRO |
| Vendor pixel auto-detection | Tags configured in iQ | 80+ vendors detected by network signature |
| Alert latency | Reports run on schedule (typically daily/weekly) | Median <2 seconds to Slack/PagerDuty/email/SMS |
| Revenue impact attached to alerts | No | Yes. Estimated $ at risk per failure |
| Consent Mode v2 monitoring | Configuration-side via EU mode | Runtime: detects tags firing pre-consent, all 4 signals |
| Magecart / unknown-script detection | Outside iQ’s scope | Real-time inventory + SRI verification |
| Pricing model | Enterprise, custom quote (typically 5–6 figures/yr) | $99 / $899 / $3,999 per month, public |
| Time to first alert | Days to weeks (depends on Tealium AM) | 5 minutes. Paste <script>, alerts on next pageview |
Why Tealium customers add us, not replace.
Most TagDrishti customers running Tealium do not migrate off iQ. The two tools sit alongside one another: iQ owns the configuration, the data layer, and the consent gating. TagDrishti owns the runtime witness, the cross-TMS view, and the alert latency. The configurations that already work in iQ keep working. The script gets pasted in <head> once, and iQ continues serving utag from the same page.
Two-source truth.
When something looks wrong, you have two independent observers (iQ’s view and ours) to triangulate. Discrepancies are usually the first signal that a vendor pixel is firing outside iQ.
triangulateMulti-vendor reality.
If your group acquired a property running GTM or Adobe Launch and you can’t migrate it to Tealium tomorrow, TagDrishti monitors all of them in one dashboard with consistent alerting.
cross-TMSA real failure mode iQ can’t catch on its own.
# ios_safari_itp_failure
An iOS Safari ITP update reclassifies your CDN-hosted utag bundle as a tracker. utag.js never loads on Safari iOS for ~30% of your traffic. iQ’s audit dashboard reports “configured tags firing normally” because the events that are arriving (from Chrome, Edge, Android) all look healthy. The audit can’t see the absence of the Safari pageviews. TagDrishti’s script loads from a different origin, runs first, and reports the device-segmented gap: “Safari iOS pageviews flat-lined at 11:42 UTC. utag.js did not execute on 4,118 of 13,602 sessions in the last hour.” That alert lands within the hour; iQ’s daily report would surface it ~24 hours later.
Common questions.
Will TagDrishti’s script slow down our site?
It loads with defer, gzipped to 12 KB, and does not block render or DOMContentLoaded. We measure our own footprint and surface it on the dashboard so you can verify on a Lighthouse run. If your CSP is strict, you’ll need to allow our regional origin. The install snippet shows the exact directives.
Does it conflict with Tealium’s collect.js or sGTM endpoints?
No. We’re observe-only at the page level. We read what fires, we don’t intercept or rewrite. Server-side pipelines (collect, sGTM) keep working unchanged. We can also receive server-side events via /api/server-events if you want to validate sGTM-to-vendor delivery.
How does it handle the Tealium data layer?
We read utag_data on first paint and again on every utag.link() / utag.view() call, so the events you see in our dashboard mirror what utag saw at the same moment. This gives you a clean diff if iQ ever reports an event that didn’t actually reach a vendor.
Can we white-label this for our clients?
Yes. The Agency plan ($899/mo, 10 client seats) and Agency Plus plan ($3,999/mo, 50 client seats) both include white-label client status pages. One secure URL per client, your agency’s logo, your colours. The client sees green/amber/red without a TagDrishti login.
What about the multi-region setup Tealium customers usually need?
Same. We run regional ingestion endpoints in APAC, EU, and US so EU sessions never leave EU and APAC sessions never leave APAC. The region is locked at first event and can only be changed via support, matching how Tealium customers typically govern data residency.
independent witness · 12 KB · works alongside iQ
Add the witness without touching Tealium.
One <script> tag in <head>. Your existing iQ configuration keeps doing its job. We start observing on the next real-user pageview.
30 days, no credit cardno Tealium migrationwhite-label on Agency