Agency Operations: 10+ Client Sites

I have advised dozens of agencies on turning tag management into a recurring-revenue service line. The ones that hit ₹15L+ monthly recurring revenue from monitoring alone all do the same four things. This guide is the operational playbook.

The Agency Monitoring Problem

You manage tracking for 10, 20, or 50 client sites. Each site has its own GTM container, its own GA4 property, its own set of vendor tags, and its own in-house team that deploys changes without telling you. A tag breaks on one client site at 2 AM. Nobody notices until the client calls four days later and asks why their conversion data is wrong. You spend two hours debugging, find a broken data layer push from a developer deploy, fix it, and lose the client’s confidence anyway.

Meanwhile the pitch your sales team is making, “we’re the analytics experts,” rings hollow, because expertise without observability means you find out about problems at the same time your client does.

This guide covers how to set up TagDrishti to monitor all your client sites from a single dashboard, route alerts to the right team, generate per-client reports, and turn monitoring into a billable service.

Step 1: Set Up the Agency Plan

The Agency plan is $399 per month. It includes:

• 10 domains (additional domains at $29/month each)
• 500,000 sessions per month across all domains
• Per-domain alert routing (Slack channels, email groups)
• White-label PDF reports with your agency branding
• Sub-accounts for client-facing dashboard access
• Priority support with a dedicated onboarding call

1. Sign up at accounts.tagdrishti.com/sign-up.
2. Select the Agency plan during onboarding. If you already have a Starter plan, upgrade under Settings → Billing.
3. Complete billing. Annual plans save 20%.

Step 2: Add Client Domains

1. Click Add Domain from the dashboard.
2. Enter the client domain. Example: www.clientsite.com.
3. Label the domain with the client name. This label appears on reports and alerts.
4. Copy the monitoring script and send it to the client’s developer or install it yourself if you have access.
5. Repeat for each client. Need more than 10? Add them from Settings → Domains → Add Domain at $29 per additional domain per month.

Each domain gets its own monitoring script with a unique data-site-id. Do not share scripts between domains. This corrupts the per-client attribution.

Step 3: Route Alerts Per Client

Generic alerts are useless for agencies. You need the GA4 failure on Client A’s site to go to Client A’s Slack channel, not your #general channel.

1. Go to Settings → Alerts → Alert Routing.
2. For each domain, assign one or more alert destinations:
   • Slack channel: Connect your Slack workspace once. Then map each domain to a specific channel. Example: Client A alerts go to #client-a-monitoring.
   • Email group: Enter the email addresses of the people responsible for that client. Example: [email protected].
   • Webhook: Send alerts to a custom endpoint. Useful for integrating with PagerDuty, Opsgenie, or your internal tooling.
3. Set per-domain thresholds. A high-traffic ecommerce client might need tighter thresholds (alert at 5% deviation) than a low-traffic brochure site (alert at 30% deviation).

Step 4: Schedule White-Label Reports

Clients expect monthly reporting. TagDrishti generates PDF reports automatically.

1. Go to Settings → Reports.
2. Upload your agency logo. Set the report header to your agency name.
3. For each domain, configure report settings:
   • Frequency: Weekly or monthly.
   • Recipients: Client email addresses.
   • Sections: Choose which panels to include: Tag Health summary, incident log, Web Vitals, consent compliance status.
4. Preview a report before activating. The report shows the previous period’s data: tags monitored, uptime percentage, incidents detected and resolved, performance metrics.

Reports are sent automatically on the schedule you set. No manual work each month. The best agencies I work with pair the report with a 20-minute client call every quarter. That turns a PDF into a retention conversation.

Step 5: Create Client Sub-Accounts

Some clients want direct access to their monitoring dashboard. Sub-accounts give them read-only access to their own domain data without seeing other clients.

1. Go to Settings → Team → Sub-Accounts.
2. Click Create Sub-Account. Enter the client contact’s email.
3. Assign the sub-account to one or more domains. The client sees only those domains when they log in.
4. The sub-account uses the TagDrishti dashboard with your agency branding (logo and name from the report settings).

Pricing Models That Actually Close

Bundled

Include monitoring in your existing analytics retainer. No separate line item. Your cost is $29–$40 per domain per month. You absorb this cost and use monitoring as a retention tool and differentiation point. Best for agencies that compete on service quality and have strong existing relationships.

Standalone service

Sell tag monitoring as a separate line item. Typical pricing by agency size:

• Small client (under 50K sessions/month): $200–$300/month. Includes monitoring, alerting, and monthly report.
• Mid-size client (50K–200K sessions/month): $400–$500/month. Includes monitoring, alerting, weekly report, and incident response within 4 hours.
• Enterprise client (200K+ sessions/month): $600–$700/month. Includes everything above plus consent compliance monitoring, Web Vitals tracking, and quarterly tag audits.

Pitch to Clients

Frame the service around data loss prevention, not monitoring. Clients care about their GA4 data being accurate, their ad spend being tracked, and their compliance being maintained. They do not care about tag fire rates in the abstract.

Use this positioning: “We monitor every tag on your site 24/7. When something breaks, we fix it within 4 hours. You never lose conversion data, your ad platforms always have accurate signals, and your consent compliance stays current.”

Show the client a sample report during the pitch. Point to a real incident where early detection saved data. If you are on the trial, use your own site’s data as the demo.

The One-Page SLA Template I’ve Seen Win

Do not over-engineer this. The clients worth signing want clarity, not contract theatre.

• Monitoring uptime: 99.9% measured at the script-load level. (This is TagDrishti’s SLA to you.)
• Alert latency: Sub-60-second detection, 5-minute Slack notification.
• Incident response: Business-hours 2-hour acknowledgement; 4-hour resolution for P1 incidents (revenue-blocking tags).
• Reporting cadence: Weekly dashboard, monthly PDF, quarterly strategic review.
• Scope: Listed tags only. New tags added by the client’s internal team are monitored within 24 hours of TagDrishti detecting them.

The Unit Economics

At $400/month per client across 10 clients, a monitoring service generates $48,000/year in recurring revenue against $4,788/year in TagDrishti cost (Agency plan). That is a 90%+ gross-margin service line.

The operational cost per client is roughly 2 hours/month of attention: a weekly scan of the dashboard and occasional triage when an alert fires. At a $100/hour blended agency rate, that is $200/month of labor cost per client. Net margin is still well above 50%.

The math is the reason monitoring is the single highest-leverage service line an analytics agency can add in 2026.

The agencies that win this are not the ones with the fanciest dashboards. They are the ones with the fastest alert response. Set your team’s incident SLAs and enforce them. Reputation compounds from there.