Automated Guardrails for Google Ads: ROAS Floors, CPA Caps, and Spend Pacing

Every advertiser has a version of the same story: a campaign quietly went sideways — ROAS slid, CPA crept up, or spend burned with nothing coming back — and nobody noticed until the weekly check-in. The money was gone days before anyone looked.

Guardrails are the fix: limits you define once — a ROAS floor, a CPA cap, a spend condition — that are checked continuously and enforced automatically. Not a dashboard you have to remember to open. A rule that acts.

What you can build guardrails on

AdTrigger's ad metrics engine reads your own campaign performance from Google Ads and lets you trigger on any of it:

• Efficiency — ROAS, CPA, CPC, CPM, CTR
• Volume — spend, clicks, impressions
• Outcomes — conversions, conversion value

Each condition is measured over a window you choose: Today, Yesterday, or the last 7, 14, or 30 days. Conditions combine with AND/OR logic in a single rule, and rules are checked hourly.

Guardrail 1: the ROAS floor

WHEN ROAS over the last 7 days drops below 3.0 → THEN pause the campaign.

The window is the important decision. "Today" reacts fastest but is noisy — one slow morning can trip it. A 7-day window smooths daily variance and catches genuine decay: creative fatigue, rising auction prices, a landing page that quietly broke. Pick the window that matches how fast your account actually moves, not the most dramatic one.

Rules are state-based, which is what makes this a guardrail rather than a kill switch: if the campaign recovers above the floor, the rule re-enables it automatically. You're not choosing between "let it bleed" and "remember to turn it back on."

Guardrail 2: the CPA cap

WHEN CPA today rises above your break-even number → THEN pause the campaign.

You know your margin; a campaign that acquires customers above it is losing money with extra steps. The cap turns that arithmetic into enforcement. This is the guardrail to set on a short window — when acquisition cost breaks through break-even, every additional hour is real money.

Guardrail 3: the zero-conversion burn

WHEN spend today is above $100 AND conversions today are 0 → THEN pause the campaign.

This is the one that catches broken things rather than underperforming things: a disapproved ad still accruing display spend, a checkout that stopped firing the conversion tag, a landing page returning errors. Neither condition alone is alarming — spend without context is just spend, and a slow conversion morning happens. Together they're a fire alarm. That's why compound AND logic matters: the guardrail encodes the combination that means something is wrong.

The same trick in reverse: scaling winners

Guardrails protect the downside, but the identical mechanism works on the upside: WHEN ROAS over 7 days is above 5.0 → THEN increase the budget. A campaign that's printing shouldn't wait for Monday's meeting either.

Why rules instead of scripts or spreadsheets

• No code to maintain. A guardrail reads the way you'd say it out loud. When your break-even changes, you edit a number, not a script.
• Every action is logged with why. Each pause and re-enable lands in an audit log with the trigger reason — which metric, which threshold, which window. Month -end spend questions get answers, not shrugs.
• Both edges are handled. The rule that pauses on breach is the same rule that restores on recovery. Half-automated guardrails (alert emails you act on eventually) leave the expensive half to memory.

Getting started

Ad metrics triggers are available on the Starter plan and up. Connect Google Ads, pick the campaign, and write the first guardrail — the ROAS floor is the usual place to start, and the ad performance use case page has step-by-step playbooks for every rule in this post, including CPA caps for dropshipping margins and spend pacing.

None of these rules make your ads better. They make sure you find out — and act — within the hour instead of at the weekly check-in. For most accounts, that gap is where the wasted spend lives.