Every TagDrishti Feature Explained: What It Does, Why It Matters, and What It Catches

Real-Time Tag Monitoring

TagDrishti’s core function is continuous, real-time observation of every tag that executes on your website. The monitoring script loads alongside your existing tags (via a single line of JavaScript or a GTM Custom HTML tag) and observes every tag fire, every outbound network request, and every data layer interaction.

For each tag fire, the system records:

• Tag identity: Which tag fired (GA4, Meta Pixel, Google Ads, TikTok, LinkedIn, Criteo, or any of 100+ supported vendors)
• Fire status: Did the tag execute successfully? Was the outbound request blocked (ad blocker)? Did the endpoint return an error?
• Data payload: What parameters were sent? Were required fields (transaction_id, value, currency, items) present and valid?
• Timing: When did the tag fire relative to page load, user interaction, and consent state changes?
• Context: Page URL, device type, browser, geography, session ID

This data streams to the TagDrishti dashboard in real time. There is no batch delay. If a tag fires (or fails to fire) right now, it appears in the dashboard within seconds.

Anomaly Detection and Alerting

Raw monitoring data is useful for investigation but insufficient for detection. You need to know when something goes wrong without staring at a dashboard. TagDrishti’s anomaly detection compares current tag behaviour against a rolling 7-day baseline, adjusted for day-of-week and hour-of-day patterns.

When a tag’s fire rate, success rate, or data completeness deviates beyond a configurable threshold (default: 20% deviation from baseline), an alert fires. Alerts are delivered via:

• Email (immediate and daily digest options)
• Slack (real-time, posted to a channel of your choice)
• Webhook (for integration with PagerDuty, Opsgenie, or custom systems)

Each alert includes: what changed, when it changed, the magnitude of the change, the probable cause (if detectable), and a link to the affected tag’s detail view in the dashboard.

Consent Compliance Verification

TagDrishti observes the consent state on every page load and correlates it with tag behaviour. For each tag fire, it records whether the user had granted or denied consent at the moment the tag executed. This produces a compliance report that shows:

• Percentage of tag fires that occurred within correct consent boundaries
• Specific tags that fire before consent is initialised
• Non-Google tags that ignore Consent Mode signals
• Sessions where GPC (Global Privacy Control) is present and whether tags respect it

This is not a one-time audit. It runs continuously. When a CMP update, a GTM publish, or a site change causes a consent configuration drift, the system detects and alerts within hours.

Core Web Vitals Per-Tag Impact

TagDrishti measures each tag’s contribution to Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). This is not just the tag’s own load time — it is the tag’s impact on the overall page’s CWV metrics, accounting for main thread blocking, layout shifts from injected elements, and resource contention with other scripts.

The dashboard shows a per-tag performance table with P75 values for each CWV metric. You can see, at a glance, that Hotjar adds 340ms to LCP, Intercom adds 380ms, and your A/B testing tool adds 400ms. When your CrUX scores drop, you know exactly which tag caused it.

GTM Container Change Detection

When a new GTM container version is published, TagDrishti detects the change and logs:

• The new version number
• The timestamp of the publish
• Which tags were added, modified, or removed
• Which triggers and variables changed

It then correlates the publish with tag health metrics. If version 84 was published at 14:00 and your purchase event’s fire rate dropped 50% at 14:05, the system connects the two events and includes the container change in the alert context. This reduces diagnosis time from hours to seconds.

Script Security Monitoring

For sites subject to PCI DSS 4.0 (any site that processes payment cards), TagDrishti maintains a script inventory for payment pages. It lists every script that executes on the checkout page, verifies integrity on each page load, and alerts on any unauthorised additions, modifications, or removals.

This directly addresses PCI DSS 4.0 requirements 6.4.3 (script inventory and integrity verification) and 11.6.1 (change and tamper detection). The alert logs and script inventory reports serve as QSA evidence during assessments.

Synthetic Journey Testing

TagDrishti runs automated browser journeys on a configurable schedule. Each journey simulates a real user path (homepage → product → cart → checkout → confirmation) and verifies that every expected tag fires with correct data at every step.

Synthetic tests catch failures that real-user monitoring misses: low-traffic page issues, multi-step data passing failures, and overnight deployment breakages. Combined with real-user monitoring, synthetic testing reduces mean time to detection from days to under 2 hours.

BigQuery Real-Time Access

Every tag event, network request, consent change, and performance measurement streams in real time to your workspace BigQuery dataset with per-tenant row-level isolation. The export includes 130+ columns across five tables. You query it with SQL, connect BI tools (Looker Studio, Tableau, Power BI), and build custom dashboards that answer your specific business questions.

White-Label Reports

For agencies, TagDrishti generates audit PDFs on demand, branded with your agency logo, accent colour, and name. PDFs include tag health summaries, consent compliance status, performance impact data, security monitoring results, and actionable recommendations. A Monday-morning digest email — also in your agency brand — goes out every week, so clients see the work without you having to assemble a manual report.

Setup

Installation takes under 5 minutes. Add one line of JavaScript to your site header (or a GTM Custom HTML tag). The script auto-detects all tags on the page. No per-tag configuration required. No vendor API keys needed. The monitoring begins immediately. The 7-day baseline calibration runs in the background while you start receiving real-time data from the first page load.

INR Pricing and ROI for Indian Businesses

TagDrishti is priced for the Indian market. The Starter plan is ₹4,999/month, Growth is ₹14,999/month, Scale is ₹39,999/month, and Enterprise starts at ₹99,999/month. All plans include real-time monitoring, anomaly detection, consent compliance verification, Core Web Vitals per-tag measurement, GTM change detection, synthetic journey testing (Growth and above), BigQuery export (Scale and above), and white-label reports (Scale and above).

The ROI math is straightforward. A D2C brand doing ₹5 crore/year in online revenue with a 4% attribution-recovery uplift (typical after fixing broken Meta Pixel CAPI, GA4 purchase events, and consent gating) recovers ₹20 lakh/year of correctly-attributed revenue. The Growth plan at ₹14,999/month is ₹1.8 lakh/year. That is an 11x return in year one, before counting the savings on reduced agency investigation hours, fewer emergency war-rooms, and lower data quality cleanup cost.

For enterprises doing ₹100+ crore/year, a 2% attribution gap recovery is ₹2 crore/year. The Enterprise plan at ₹12 lakh/year is a 16x return — and that is before counting the PCI DSS 4.0 evidence automation, DPDP Act audit readiness, and board-level data quality reporting that enterprise tier provides.

Case Study: A Bengaluru D2C Brand’s First 90 Days

A Bengaluru-based fashion D2C brand installed TagDrishti in January. The brand was doing ₹8 crore/year online across Shopify, Meta Ads, Google Ads, and a growing influencer programme. The CMO suspected attribution was leaking but could not quantify the gap.

Week 1 findings: Meta Pixel CAPI was deduplicating 23% of purchase events incorrectly due to a fbp/fbc cookie timing bug. GA4 purchase events were missing the shipping parameter 18% of the time, which meant Google Ads Smart Bidding was undervaluing shipped orders. Consent Mode v2 was set to denied for 12% of sessions where the user had explicitly consented, due to a CMP race condition with the Shopify theme.

Week 2-3 remediation: The brand’s agency fixed the three issues using TagDrishti’s diagnostic output. Each fix was validated within 2 hours of deployment by watching the dashboard.

Week 4-12 results: Meta reported attribution rose 9% (the actual recovery, not a modelling artefact). Google Ads Smart Bidding CPA dropped 14% as it finally received clean conversion data. GA4 e-commerce revenue matched Shopify backend revenue within 1.5% (previously the gap was 6.8%). The marketing team saved roughly 12 hours/week of manual reconciliation work. Net financial impact: ₹68 lakh of recovered attributed revenue across 90 days, against a ₹45,000 TagDrishti spend.

How TagDrishti Differs From Alternatives

Common Misconceptions About Tag Monitoring

Misconception 1: “GTM Preview Mode is enough”

Preview mode shows you tag behaviour right now, on your machine, in your browser, for your session. It does not tell you what happened to the user who hit /checkout at 03:14 on a low-end Android device with 2G connectivity. Production monitoring is a different problem, solved by different tools.

Misconception 2: “GA4 DebugView catches issues”

DebugView shows individual events for debug-enabled sessions. It does not surface aggregate anomalies, does not cover non-GA4 tags (Meta Pixel, Google Ads, TikTok), and does not correlate issues with GTM container changes. It is a debugging tool, not a monitoring tool.

Misconception 3: “Sentry or Datadog covers it”

APM tools catch JavaScript errors and application performance issues. They do not verify that transaction_id is present on every purchase event, or that Meta Pixel CAPI deduplication is working, or that Consent Mode v2 signals are being respected. Tag monitoring is an adjacent discipline that overlaps with APM at the edges but is not covered by it.

Misconception 4: “The agency monitors our tags”

Most agencies check tags during implementation and then react to client-reported issues. Very few have continuous monitoring infrastructure. This is changing slowly — and agencies who adopt TagDrishti as a productised service are seeing it as a margin-preserving differentiator rather than a cost. But if you have not explicitly asked your agency whether they have real-time tag monitoring and seen their dashboard, the answer is almost certainly no.

Misconception 5: “We can build this internally”

You can. Several enterprises have. The build cost is typically 6-9 months of 2-3 senior engineers, plus ongoing maintenance of vendor endpoint mappings (which change quarterly as Meta, Google, TikTok, and others evolve their APIs). Total cost of ownership is usually ₹1.5-₹2.5 crore in year one, versus ₹12 lakh for Enterprise tier. Unless tag monitoring is your core product, the build-vs-buy math heavily favours buying.

Implementation Checklist for Your First 30 Days

Day 1-2: Install the monitoring script. Verify detection of your top 10 tags (GA4, Meta Pixel, Google Ads, and whatever else is running). Confirm data is flowing to the dashboard.

Day 3-7: Configure alerting. Set Slack channel, email recipients, and alert thresholds. Invite your agency, CMO, head of marketing, and senior analyst as users. Run through your existing tag inventory and tag which are business-critical (purchase, lead, sign-up) versus informational.

Day 8-14: Review the first week of baseline data. Likely findings: one or two tags with attribution issues you did not know about, one consent gating drift, two or three tags materially impacting CWV. Log these as remediation tickets.

Day 15-21: Work through remediation. Validate each fix with the dashboard within 2 hours. Update GTM or site code as needed. Communicate the impact to your CMO with before/after numbers.

Day 22-30: Establish weekly review cadence. Monday-morning dashboard review with agency and marketing team. Use the white-label report (if on Scale tier) as the meeting artefact. Start tracking attribution recovery month-over-month.

Who Should Use Each Tier

Starter (₹4,999/month): Single-site businesses doing ₹50 lakh to ₹3 crore/year online. Basic monitoring, alerting, and consent compliance. Up to 5 tags tracked in detail, 100K events/month.

Growth (₹14,999/month): D2C brands and mid-market e-commerce doing ₹3 crore to ₹20 crore/year. Includes synthetic journey testing, expanded tag coverage (up to 25 tags), 1M events/month, GTM change correlation.

Scale (₹39,999/month): Mid-market to enterprise doing ₹20 crore to ₹100 crore/year. Includes BigQuery real-time export, white-label reports, unlimited tags, 5M events/month, and agency multi-client views.

Enterprise (starting ₹99,999/month): Enterprises doing ₹100+ crore/year or any business with PCI DSS 4.0 or DPDP Act audit requirements. Includes PCI evidence automation, dedicated SSO, custom data retention, SLA, dedicated customer success manager, and regulatory audit support.

FAQ for Decision Makers

Does TagDrishti slow down my site?

The monitoring script is ~15KB gzipped, loads asynchronously, and executes in a worker context where supported. Measured LCP impact is under 25ms at P75, well below the threshold of CWV materiality. INP impact is effectively zero because the script does not block the main thread during user interactions.

Does TagDrishti store sensitive user data?

No. The script observes tag behaviour, not user PII. It does not store email addresses, phone numbers, or payment data. For the compliance verification layer, it records consent state (granted/denied) and tag behaviour correlation, not the consent identity. DPDP Act and GDPR compliant by design.

Can we start with a free trial?

Yes. 14-day free trial, no credit card required. Full access to the Growth tier feature set. If you do not find at least one critical issue during the trial, the product is not working as intended — we have never seen that happen across hundreds of installs, but the trial is structured so you can validate value before committing.

What if we already have a tag management tool?

TagDrishti is complementary to GTM, Tealium, Segment, Adobe Launch, and any other TMS. It does not replace them. It monitors what they deploy. Think of it as observability for your tag layer, regardless of which TMS you use.

How long until we see ROI?

Most customers identify their first critical issue within the first 7 days. Remediation typically takes 1-2 weeks. Revenue-attributable recovery is visible in Meta Ads Manager, Google Ads, and GA4 within 30-45 days of remediation. Our median time to positive ROI is 47 days.

Bottom Line

TagDrishti is not a replacement for GTM. It is the monitoring layer GTM was never designed to provide. For any business where online revenue materially depends on correct tag firing — which is effectively every D2C brand, e-commerce operator, and performance-marketing-driven business in India — continuous production tag monitoring is now as fundamental as application monitoring or error tracking. The question is not whether you need it. The question is whether you build it in-house, wait for the next costly attribution disaster to force the conversation, or install a 5-minute script and get clean data from next Monday onwards.