Building a Tracking-Health SOP for Your Agency

The agencies that never get blindsided by broken tracking don't have better media buyers — they have better systems. A tracking-health SOP turns “someone should probably check that” into a defined process that runs the same way every time. Here's how to build one.

1. Onboarding: establish the baseline

When a new client comes on, document their tracking setup and confirm it works before you touch anything. Use a 15-minute audit and record: pixels and datasets, conversion actions, current EMQ, and any existing issues. This baseline protects you later — if performance dips, you can prove whether tracking was the cause and whether it was broken before you arrived.

2. Pre-launch: QA every campaign

Before any new campaign spends, run a pre-launch tracking QA checklist. Make it a required step in your launch process, not an optional one — the same checks, every time, with a named owner.

3. Ongoing: monitor continuously

This is where most SOPs fall apart. “Check tracking weekly” sounds fine until you have 20 accounts and it quietly stops happening. Two options:

• Manual: a scheduled weekly review of every account's pixel status, EMQ, and conversion tracking. Works for a few accounts; collapses at scale, and a weekly cadence still means a break can run for days.
• Automated: continuous monitoring that alerts you the moment something breaks, so the “check” happens every 30 minutes without anyone lifting a finger. This is the only version that truly scales.

4. When something breaks: a response playbook

1. Confirm it's tracking, not performance (check backend revenue, both platforms).
2. Diagnose the cause (recent deploy? consent change? paused action?).
3. Fix and verify end to end.
4. Communicate to the client — proactively, in plain language.
5. Log it so you can spot patterns across accounts.

5. Assign ownership

Every step needs a name attached. “The team handles it” means no one does. Assign who runs onboarding audits, who owns pre-launch QA, and who responds to alerts.

The system, not the heroics

A good SOP replaces heroics with reliability — you stop depending on someone remembering to check. Taglertis the engine for the “ongoing monitoring” step: connect every client account once, and it runs the checks continuously and alerts you when something breaks, turning the hardest part of the SOP into something that just happens. See also monitoring across many accounts.