When to Pause vs Cut Budget 20%

Core Difference

Pausing stops all ad spend and impressions for a campaign or ad set. Cutting reduces daily budget by a set amount (often 20%) while keeping the campaign live. The choice depends on what the operator needs to learn.

Pause when the goal is isolation - to remove a variable and see if performance improves elsewhere, or to stop bleeding cash while investigating root cause. Cut when the goal is optimization - to test whether lower spend still generates acceptable ROAS or to reduce waste in a declining channel without losing data.

Pause Triggers

Pause immediately if ROAS has fallen below breakeven for 3+ consecutive days and no clear external cause (iOS update, platform outage, seasonal shift) is visible. Pause if cost per acquisition (CPA) exceeds 1.5x target for 48+ hours. Pause if a campaign is cannibalizing another higher-performing campaign within the same audience segment.

ROAS < 1.0x for 72+ hours with no recovery trend
CPA > 1.5x target baseline for 2+ days
Audience overlap > 40% with a better-performing campaign
Creative fatigue confirmed (CTR down 25%+ week-over-week, same audience)
Platform algorithm signal: quality score drop, relevance score < 5/10 (Meta), or disapproval notice
Testing a new variable (audience, creative, offer) and need clean data

Cut Budget Triggers

Cut 20% when ROAS is still positive (1.2x - 1.5x) but trending downward over 5 - 7 days. Cut when a channel is generating conversions but at lower efficiency than historical baseline, and the operator wants to test whether demand exists at lower spend levels. Cut when scaling has hit a ceiling - impressions are flat or declining despite stable budget, signaling audience saturation.

ROAS between 1.2x and 1.5x with downward slope over 7 days
CPA rising 10 - 20% week-over-week but still profitable
Impression volume flat or declining despite unchanged budget
Audience size shrinking (fewer eligible users) but conversion rate stable
Testing budget elasticity on a proven campaign
Cash flow constraint requiring spend reduction across all channels

Decision Tree Procedure

Step 1: Measure current ROAS and CPA. Compare to 7 - day rolling average and to target baseline. Step 2: Check external factors - platform outages, iOS/Android updates, seasonal calendar, competitor activity, or recent creative/audience changes. If external factor is likely cause, pause and wait 24 - 48 hours before deciding next move. Step 3: If no external cause, check trend direction. Is performance declining, flat, or improving? Step 4: If ROAS < 1.0x or CPA > 1.5x target, pause. If ROAS 1.2x - 1.5x and declining, cut 20%. If ROAS > 1.5x, hold or increase.

Pause Duration and Re-entry

Paused campaigns should be reviewed after 24 - 48 hours. Use the pause window to audit creative quality, audience definition, landing page experience, and offer relevance. Before re-entry, make at least one change - refresh creative, narrow audience, adjust bid strategy, or test new offer. Re-launch at 50% of original budget for 24 hours to confirm recovery. If ROAS returns to target within 48 hours of re-entry, scale back to original budget. If not, pause again and investigate further.

Cut Budget Monitoring

After cutting 20%, monitor for 5 - 7 days. Track whether ROAS improves (lower spend often reduces waste and lifts efficiency), stays flat (demand is inelastic at this price point), or worsens (algorithm deprioritizes lower-spend campaigns). If ROAS improves by 10%+ after cut, the campaign was over-spending. Hold the new budget or cut another 10 - 15%. If ROAS stays flat, the campaign is efficient at both spend levels - consider cutting another 20% or reallocating to higher-ROAS channels. If ROAS drops below 1.2x after cut, revert to original budget within 24 hours.

Documentation and Iteration

Log every pause and cut decision with timestamp, reason code (low ROAS, saturation, testing, cash flow), pre-action metrics, and post-action results. This creates a decision log that reveals patterns - e.g., certain audiences always require pause-and-refresh cycles, or certain channels are consistently over-budgeted. Review the log monthly to refine thresholds. If a campaign is paused more than twice in 30 days, consider sunsetting it entirely rather than cycling through pause-and-relaunch.

Questions

FAQ

Should I pause or cut if ROAS is 1.3x and stable?

Neither. A stable 1.3x ROAS is profitable and not signaling decay. Hold the budget. Only cut if ROAS is 1.3x and declining over 5+ days, or if cash flow requires reduction. Only pause if external factors (platform issue, creative fatigue) are confirmed.

How long should a pause last?

24 - 48 hours minimum. Use the pause to diagnose and change at least one variable (creative, audience, offer, bid strategy). Longer pauses (7+ days) risk losing algorithm momentum and audience familiarity with the ad. If a campaign needs more than 48 hours of investigation, it likely needs sunsetting, not pausing.

Can I cut budget and pause at the same time?

No. Pause removes the variable entirely; cutting keeps it live. Doing both creates noise and prevents clear diagnosis. Choose one action. If you pause, you're isolating. If you cut, you're testing elasticity. Mixing them obscures which action caused the outcome.

What if a campaign has been paused three times in 60 days?

Sunset it. Three pause cycles in 60 days indicates the campaign's fundamentals are broken - audience, offer, or creative no longer resonates. Reallocate the budget to proven channels. Document the reason (audience fatigue, offer mismatch, platform deprioritization) and avoid similar setups in future tests.

Want this on your account?

Thirty minutes. Bring the number that keeps you up.

Book a demo