How to Automatically Pause Campaigns When ROAS Drops Too Low

Every e-commerce business running Google Shopping or Performance Max campaigns faces the same problem: return on ad spend fluctuates constantly, and by the time you notice a campaign has become unprofitable, you have already lost money. Competitors launch promotions that drive up CPCs, products go out of stock, seasonal demand shifts — and manual monitoring cannot keep up with the pace of change.

ROAS protection automation continuously monitors your campaign performance and takes action the moment profitability drops below your threshold. Campaigns are paused automatically when they stop making money and re-enabled when performance recovers.

Why This Approach Works

Every dollar you spend on advertising should generate more than a dollar in return. When it does not, you are burning cash. Manual monitoring creates two problems: a reaction delay (campaigns haemorrhage budget for 12-24 hours before anyone notices) and a recovery delay (paused campaigns sit idle because nobody checks whether performance has recovered). On a campaign spending $500/day with a ROAS of 1.0 instead of 3.0, a single day of reaction delay costs roughly $330 in wasted spend.

Automated ROAS protection eliminates both delays — pausing campaigns when ROAS drops below your floor and re-enabling them when performance recovers. Using a 7-day lookback window is critical. Daily ROAS is too volatile; a 7-day window smooths out variance while remaining responsive enough to catch genuine declines within a business week.

How to Set This Up in AdTrigger

Setting up ROAS protection in AdTrigger takes about five minutes. Here is the step-by-step process:

1. Connect your Google Ads account. Link your Google Ads account to AdTrigger using OAuth. This grants read access to your campaign metrics and write access to pause and enable campaigns.
2. Create a new rule and select your campaign. Choose the Google Shopping or Performance Max campaign you want to protect. The rule will monitor and act on this same campaign — metrics are read from the campaign, and actions are applied to it.
3. Set the pause condition. Configure the condition as: ROAS is less than 3.0 over the Last 7 days. Set the action to pause the campaign. A ROAS of 3.0 means you earn $3 for every $1 spent — adjust this threshold based on your margins. If your average product margin is 40%, a ROAS of 2.5 is your break-even point, so 3.0 gives you a comfortable buffer.
4. Create a companion recovery rule. Create a second rule on the same campaign: ROAS is greater than 3.5 over the Last 7 days, with the action set to enable the campaign. The recovery threshold (3.5) is deliberately higher than the pause threshold (3.0) to create a buffer zone that prevents the campaign from rapidly toggling on and off — a pattern known as flapping.
5. Review and activate. Check that both rules are configured correctly and activate them. AdTrigger will begin monitoring immediately, with metrics cached every 15 minutes to minimise API calls to your ad platform while still providing timely responses.

Every action AdTrigger takes is recorded in a full audit trail, so you can see exactly when a campaign was paused, why it was paused (which metric threshold was breached), and when it was re-enabled.

Maximising Your Return on Ad Spend

Once you have the basic protection rule in place, there are several ways to get more value from this automation:

• Layer in additional conditions with AND logic. Instead of pausing solely on ROAS, add a compound condition: ROAS is less than 3.0 AND total spend over the last 7 days exceeds $200. This prevents the rule from pausing a campaign that has barely spent anything — low-spend campaigns often show volatile ROAS that corrects naturally as more data accumulates.
• Use budget reduction before full pauses. For high-value campaigns where pausing entirely risks losing audience signals, consider a softer approach: reduce budget by 40% when ROAS drops below 3.0, with a minimum floor of $50/day. Then pause only if ROAS drops below 2.0. This two-tier approach preserves some presence while cutting exposure on underperforming campaigns.
• Set different thresholds for different campaign types. Brand campaigns and prospecting campaigns naturally have lower ROAS than retargeting campaigns. Apply ROAS floors that match each campaign type — perhaps 2.0 for prospecting and 5.0 for retargeting — rather than a single blanket threshold.
• Monitor conversion value alongside ROAS. A campaign with a 4.0 ROAS on $50/day generates less profit than a campaign with a 3.2 ROAS on $500/day. Use the conversion value metric in your conditions to ensure you are optimising for total profitability, not just efficiency ratios.

Common Pitfalls to Avoid

• Setting the lookback window too short. Using "Today" or "Yesterday" as your lookback window makes the rule hyper-reactive to daily fluctuations. A single day of low conversions — perhaps due to a payment gateway issue or a public holiday — could trigger a pause that removes you from auctions during the recovery period. The 7-day window is the right balance for most e-commerce campaigns.
• Using the same value for pause and recovery thresholds. If you pause at ROAS below 3.0 and re-enable at ROAS above 3.0, the campaign will flap — pausing and enabling repeatedly as ROAS oscillates around the threshold. Always set your recovery threshold at least 15-20% above your pause threshold.
• Forgetting to account for conversion lag. Google Ads attribution models often take 24 to 72 hours to assign all conversions. A campaign that appears to have a 2.5 ROAS today may actually have a 3.5 ROAS once delayed conversions are attributed. Use a 7-day or 14-day lookback to minimise the impact of attribution lag on your rules.
• Applying ROAS rules to new campaigns. Campaigns in their learning phase typically have lower initial ROAS as the platform's algorithm optimises targeting. Avoid applying ROAS protection rules until a campaign has been running for at least two weeks and has gathered sufficient conversion data.
• Not reviewing the audit trail. AdTrigger logs every action, but those logs are only useful if you review them. Check the audit trail weekly to understand how frequently your rules are firing and whether your thresholds need adjustment. If a campaign is being paused and re-enabled every few days, your thresholds may be too tight for that campaign's natural volatility.

Key Takeaway

ROAS protection is the single most impactful automation you can apply to an e-commerce advertising account. It eliminates the two most expensive gaps in manual campaign management — the delay in spotting underperformance and the delay in restarting recovered campaigns. By setting a ROAS floor with a 7-day lookback and a buffered recovery threshold, you create a system that continuously protects your margins without requiring daily attention. Available on AdTrigger's Professional and Enterprise plans, this automation pays for itself the first time it catches a campaign decline before you would have noticed it manually.