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 Export

Every tag event, network request, consent change, and performance measurement can be streamed to your own BigQuery dataset. The export includes 70+ 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 white-label PDF reports branded with your agency logo and colours. Reports include tag health summaries, consent compliance status, performance impact data, security monitoring results, and actionable recommendations. Reports can be scheduled weekly or monthly and delivered automatically to client email addresses.

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.