TagDrishti was built because every analytics leader I’ve worked with at enterprise scale has the same nightmare: the conversion number on the Monday dashboard looks fine, and three weeks later the CFO asks why revenue attribution is off by ₹40 lakh. The root cause, eight times out of ten, is a tag that silently stopped firing. This guide is the onboarding sequence I walk every new customer through on their kickoff call.

What TagDrishti Does and What It Replaces

TagDrishti monitors every tag on your website in real time. It watches Google Analytics, Facebook Pixel, Google Ads, LinkedIn Insight, TikTok Pixel, and every other tag fired through GTM or loaded directly. When a tag fails, you get an alert in Slack or email within 60 seconds.

Most enterprise teams try to solve this with four tools stitched together:

GTM Preview mode, which only sees your browser, not production.
Scheduled synthetic checks, which run every 15–60 minutes and miss intermittent failures entirely.
Spreadsheets of tag ownership, which go stale the day after a GTM publish.
The GA4 Realtime report as a “canary,” which is noisy, delayed, and gives zero signal when a specific event is dropping.

TagDrishti replaces all four with one real-user-monitoring (RUM) layer that captures every tag fire and every failure, on every device, in every region. Total setup time: about five minutes.

Step 1: Create Your Account

Go to accounts.tagdrishti.com/sign-up.
Sign up with your work email or Google account. No credit card is required for the 14-day trial.
You land on the dashboard at dashboard.tagdrishti.com. It is empty because no domain is connected yet.

Tip for enterprise teams: sign up with a shared analytics team email (e.g. [email protected]) so the account does not disappear when the first person leaves. This is the single most common account-recovery ticket we see.

Step 2: Add Your First Domain

Click Add Domain in the top-right corner of the dashboard.
Enter your website URL. Example: www.example.com. TagDrishti strips the protocol automatically.
Choose your plan. Starter ($49/month) covers one domain with up to 100,000 sessions per month. Pro ($149/month) covers three domains and 500k sessions. The trial gives you full Pro access for 14 days.
Click Create Domain. The dashboard generates your unique monitoring script.

Step 3: Install the Monitoring Script

Copy the script tag from the dashboard. It looks like this:

<script
  src="https://cdn.tagdrishti.com/monitor.js"
  data-site-id="YOUR_SITE_ID"
  defer
></script>

Paste this script into the <head> section of every page on your site. The placement matters: it must be in the <head>, not the <body>. The defer attribute ensures it does not block page rendering.

Installation Methods by Stack

Direct HTML: Paste the script tag directly into your HTML template or CMS header. Works with WordPress (use the header injection plugin or your theme’s custom code area), Shopify (edit theme.liquid), Webflow (project settings → custom code → head), and any static site.

Do not install through GTM. We deliberately do not ship a GTM install path. Loading the monitor via a Custom HTML tag means a broken GTM container also breaks the thing watching it, which defeats the point. Install directly in your site's HTML <head> using one of the methods above.

Next.js / React: Add the script to your root layout using <Script> from next/script with strategy="afterInteractive".

Adobe Experience Manager / Sitecore / enterprise CMS: Work with the platform team to add the snippet to the global head include. Expect one sprint cycle for the change-control ticket.

Step 4: Verify Data Flow

After installing the script, open your website in a browser and navigate a few pages.
Return to the TagDrishti dashboard. Within 60 seconds, you should see the first data arrive.
The Tag Health panel shows a list of every tag detected on your site, with a fire count and success rate for each.
If no data appears after 2 minutes, check: Is the script in the <head>? Is the data-site-id correct? Is an ad blocker active in your test browser? Open the browser console and look for tagdrishti requests in the Network tab.

Step 5: Read the Four Core Dashboards

Tag Health: Lists every tag with its name, vendor, fire count, and success rate. A green badge means above 95% success. Yellow means 80–95%. Red means below 80%. Click any tag to see per-page breakdown, error types, and a 7-day trend chart.

Live Feed: A real-time stream of tag fires as they happen. Useful for verifying a fix or watching a deployment roll out. Each entry shows the tag name, page URL, status, and timestamp. Enterprise teams usually pin this panel on a dashboard TV during GTM publishes.

Web Vitals: Core Web Vitals (LCP, CLS, INP) measured per page, with the contribution of each tag to performance metrics. This panel populates after 24 hours of data collection.

Consent: Shows which tags fire before and after consent. Requires at least one Consent Management Platform (CMP) on the site. This panel flags any tag that fires before consent is granted. That is the single highest-severity compliance finding you can have.

Step 6: Configure Slack and Email Alerts

Go to Settings → Alerts in the dashboard.
Click Add Slack Channel. This opens the Slack OAuth flow. Authorize TagDrishti to post in your chosen channel.
Set your alert threshold. Default: alert when any tag’s success rate drops below 90% for more than 10 minutes. You can customize this per tag.
Test the integration by clicking Send Test Alert. You should see a message in Slack within 5 seconds.

Email alerts are enabled by default for the account owner. Add additional recipients under Settings → Alerts → Email.

Pro tip: Route alerts to a dedicated #analytics-alerts channel. Never route them to #general. I have seen more monitoring projects fail from alert fatigue than from missed alerts.

The Seven-Day Calibration Window

TagDrishti calibrates its anomaly detection baseline over the first 7 days. During this period, it learns your site’s normal tag behavior: which tags fire on which pages, at what rate, and with what success percentage. After calibration, anomaly detection activates and alerts become much more precise.

You do not need to configure anything during this window. The script collects data, the dashboard shows real-time metrics, and alerts fire based on the static thresholds you set. After 7 days, the system switches to adaptive thresholds that account for traffic patterns (weekday vs weekend, time of day, regional variation, known weekly cycles for B2B sites).

Five Mistakes Teams Make in the First Week

Script in <body> instead of <head>. You will see partial data. Move it to <head> immediately.
Routing alerts to #general. The first false positive trains your team to mute the channel. Dedicate a channel and keep the signal high.
Setting thresholds too tight on day 1. Before calibration completes, strict thresholds fire constantly. Use defaults for the first week.
Not adding the team. Invite at least the analytics lead, the dev lead, and the marketing ops owner. One-person accounts become stale fast.
Ignoring the Consent panel. If you have any EU traffic, the Consent panel is your compliance canary. Review it before you review Tag Health.

If you manage multiple sites, read the Agency Operations guide for multi-domain monitoring with per-client alert routing. If you’re responsible for compliance, jump to Consent Compliance after finishing setup.

Start monitoring in five minutes

14-day free trial with full Pro access. No credit card required.

Start Free Trial →

Getting Started with Tag Monitoring