Alerts Catch What's Broken. Compliance Rules Will Catch Human Error: A First Look at What's Coming to Ads Tracker HQ
Compliance Rules is the next major capability coming to Ads Tracker HQ, currently in development: a way for publisher ad ops teams to define their own setup standards - naming conventions, required trafficker and salesperson assignments, pricing and budget thresholds - and have every order and line item in their GAM network evaluated against those standards daily. Violations surface as a systematic compliance listing, and any rule can optionally fire as a standard alert.
The daily alerts you know answer one question every morning: is anything broken? Pacing off, revenue down, ad units dark. Compliance Rules answers the question that comes before it: is everything set up the way we agreed? Different question, different failure mode, and - until now - a layer most teams could only police with spot-checks. Here's a first look at how it works, the kinds of rules teams will run, and where it fits in the daily coordinator's morning.
Monitoring vs Compliance: Two Different Questions
Performance monitoring - the daily alerts across campaigns, revenue, and inventory - watches for anomalies: numbers moving against baseline, delivery falling behind pace, ad units going quiet. It's detective work on outcomes.
Compliance is a different discipline. It watches for drift from standards: the order created without a salesperson assigned, the line item named outside the convention, the direct-sold entry priced below the agreed floor. Nothing is "broken" yet - delivery is fine, revenue is fine - but the setup has quietly departed from how the team agreed things should be done, and the costs land later: fragmented reporting rollups, stalled reconciliations, inventory sold off-policy. (We wrote up the full anatomy of that quiet damage in our companion piece on GAM setup standards and human error.)
Most teams police this layer with periodic spot-checks - which sample instead of cover, and lapse exactly when campaign volume spikes. The one-line summary of why we're building this: alerts catch what's broken. Compliance Rules will catch human error - before it breaks something.
How Compliance Rules Works
Compliance Rules lives in the Ads Tracker HQ admin, alongside the alert configuration your team already manages. The working shape - with the honest caveat that details may evolve before release:
You define the rule. A name, a description, and the compliance condition - built from entity properties with AND logic, so "order has a salesperson assigned AND has a trafficker assigned" is a single rule. The rule fails when the condition is false.
You scope it. Include and exclude scopes let a rule apply only where it should - so a naming rule can cover direct-sold orders without flagging house campaigns, and a pricing threshold can exempt the legacy advertiser with grandfathered terms.
You set the severity. Not every violation is equal. A missing salesperson on a live revenue order is a different matter than a stale draft with an off-convention name - severity levels let the listing reflect that.
It evaluates daily. Every order and line item is checked against your rules as part of the same daily sync that powers the morning alerts. No extra integration, no new access - the same read-only service account that can see your data and can never change it.
Violations surface as a listing - and optionally as alerts. By default, results arrive as a compliance listing: a systematic accounting of what's drifted, reviewed on your schedule. For rules where drift is urgent, a per-rule "also alert on violation" toggle routes failures through the standard alert workflow - notify, snooze, acknowledge - with a custom violation message if you want one.
That listing-versus-alert distinction is deliberate. Compliance findings are mostly hygiene work: real, worth fixing, rarely a fire. Forcing them all through alerting would train your team to ignore alerts - so the design keeps the urgent path available per-rule without flooding the channel that matters at 8 AM.
The Rules Teams Will Run First
The common thread: every one of these is a standard your team already has. Compliance Rules doesn't invent your policies - it makes the ones in your wiki enforceable.
Where It Fits in the Daily Coordinator
The product thesis has been the same since day one: the daily coordinator runs the checks overnight and hands your team a short, prioritized list each morning - so the day starts at "fix it" instead of "find it." Compliance Rules extends that from performance into setup quality: the same morning ritual, now covering both what broke and what drifted.
For lean teams, that combination closes a specific gap. The checking work that automation already absorbed - pacing, revenue, inventory - freed senior attention from surveillance. But setup hygiene stayed manual, sampled, and honestly neglected, because nobody has spot-check hours during a busy quarter. Moving it into the daily evaluation makes standards a property of the network instead of a hope. (And if your standards themselves need defining before they can be enforced - thresholds, conventions, escalation - that's exactly the groundwork a free ad ops audit maps.)
Status, honestly: Compliance Rules is in development now. We're not promising a ship date - we'd rather get the rule builder right than rush it - but it's coming to Ads Tracker HQ as part of the platform, at no separate charge, for all subscribers. If you want your team ready for it, the practical path is to start with the daily alerts today: the 30-day free trial gets the monitoring layer working now, and the compliance layer arrives on an operation that's already systematized.
FAQ - Compliance Rules
What is Compliance Rules in Ads Tracker HQ?
An upcoming capability, currently in development, that lets publisher ad ops teams define their own GAM setup standards - required trafficker and salesperson assignments, naming conventions, pricing and budget thresholds - and have every order and line item evaluated against them daily. Violations surface as a compliance listing, and any rule can optionally also fire as a standard alert.
How is compliance different from the daily alerts?
Alerts watch performance for anomalies - pacing behind, revenue down, ad units dark - answering "is anything broken?" Compliance Rules watches setup for drift from standards - missing assignments, off-convention names, off-policy pricing - answering "is everything set up the way we agreed?" Nothing is broken yet when a compliance rule fails; the point is catching human error before it becomes a reporting, reconciliation, or yield problem.
Do compliance violations create alerts?
Only if you want them to. By default violations appear as a listing - a systematic accounting reviewed on your schedule, because most compliance findings are hygiene work, not fires. Each rule has an optional "also alert on violation" toggle that routes failures through the standard notify, snooze, and acknowledge workflow, with a custom violation message. That keeps the urgent path available per-rule without flooding the morning alert channel.
Does Compliance Rules require new access to our GAM network?
No. Evaluation runs as part of the same daily sync that powers the existing alerts, using the same read-only Google service account - provided by ProOps, added to your GAM by you, with a read-only role you assign. It can read setup data to evaluate your rules; it cannot change, pause, or traffic anything.
When does Compliance Rules launch, and what will it cost?
It's in development now - no ship date promised yet. When it arrives, it comes to Ads Tracker HQ as part of the platform for all subscribers at no separate charge, consistent with how HQ capabilities have shipped to date. Teams that want to be ready can start with the daily monitoring today via the 30-day free trial.