Automation Guide — October 20269 min read

How to Set Automated Campaign Rules in Meta and Google Based on POAS

The pillar blog says it clearly: the weekly Layer 2 decision for every campaign is Scale / Hold / Kill based on CM2 and POAS, not ROAS.

What the pillar doesn’t cover is how to make those decisions faster, more consistent, and less dependent on someone remembering to check the dashboard every Monday.

Translating your POAS target into platform bid settings

Automated campaign rules, set up inside Meta Ads Manager and Google Ads, let you codify your Scale/Hold/Kill logic into rules that run continuously. The right campaigns get scaled. The wrong ones get flagged or paused. Without waiting for a weekly review to catch what the algorithm is quietly doing to your budget.

Here’s exactly how to build them.

Why Manual Weekly Reviews Miss Things

Your weekly review runs on Monday. A campaign’s POAS dropped below 1.0 on Tuesday last week. By the time Monday arrives, that campaign has spent 6 days below break-even.

Daily spend: ₹5,000
Days below break-even before the review: 6

Spent on a loss-making campaign₹30,000

Automated rules solve the lag problem. They check performance continuously and act, or alert the moment a threshold is crossed, regardless of where you are in the review cycle.

The caveat

Automated rules in Meta and Google work on platform metrics (ROAS, CPA, spend), not on your real POAS, which requires COGS and returns data the platforms don’t have.

The workaround: translate your POAS thresholds into equivalent platform CPA or ROAS thresholds, and use those as your rule triggers.

Step 1

Translate Your POAS Thresholds Into Platform Metrics

POAS break-even → tROAS equivalent

tROAS = POAS Target ÷ Effective Margin %

Where Effective Margin = Gross Margin % − Shipping % − Returns Cost % − Payment %

Example for a beauty brand (effective margin 38%)

POAS break-even 1.0 → 1.0 ÷ 0.38: 2.63x tROAS
POAS target 1.3x → 1.3 ÷ 0.38: 3.42x tROAS
Scale threshold POAS 1.5x → 1.5 ÷ 0.38: 3.95x tROAS

Any campaign running below 2.63x ROAS (sustained) is effectively operating below POAS break-even. Recalculate these thresholds whenever your return rate, COGS, or shipping costs change significantly.

Now you have three platform ROAS levels:

Below 2.63x ROAS

Flag / pause

Below POAS break-even

2.63x–3.42x ROAS

Hold

Don’t scale, don’t kill yet

Above 3.95x ROAS

Scale

Above POAS scale threshold

Ads Manager → Automations → Create Rule

Setting Up Meta Automated Rules

Rule 1: Flag Below-Break-Even Campaigns (Notify Only)

Applies to: All active campaigns
Condition: ROAS (7-day click) < [your break-even tROAS] for 3 consecutive days
Action: Send notification to [email]
Frequency: Daily check

Do NOT auto-pause on this rule. Always investigate before pausing, a campaign below ROAS threshold might be in Learning Phase (normal), recovering from a weekend dip (normal), or genuinely losing money (action required). The notification gives you the flag; you make the call.

Rule 2: Auto-Reduce Budget on Sustained Low Performance

Applies to: Campaigns that have been running 14+ days (outside Learning Phase)
Condition: ROAS (7-day click) < [break-even tROAS] AND active > 14 days
Action: Decrease daily budget by 25%
Frequency: Weekly (not daily, budget changes reset Learning Phase stability)

This rule creates a natural budget reduction for underperformers without fully pausing, giving them time to recover while limiting waste.

Rule 3: Scale High-POAS Campaigns

Applies to: All active campaigns
Condition: ROAS (7-day click) > [scale threshold tROAS] AND cost per result > ₹10 AND active > 7 days
Action: Increase daily budget by 20%
Frequency: Weekly

The ₹10 filter screens out tiny campaigns. The 20% cap prevents over-scaling, large single budget jumps can destabilise Learning Phase even for established campaigns. 20% weekly scaling lets you compound safely.

Rule 4: Pause High-Frequency Creative

Applies to: Ad level (not campaign level)
Condition: Frequency (7-day) > 3.5 AND link CTR down > 20% vs 14-day average
Action: Pause ad, send notification
Frequency: Daily

This catches creative fatigue before it destroys the campaign’s POAS. The dual condition (high frequency AND declining CTR) reduces false positives, frequency alone isn’t always a problem, but frequency + declining CTR is a reliable fatigue signal.

Campaigns → Rules → Create Rule

Setting Up Google Ads Automated Rules

Rule 1: Flag Campaigns Below ROAS Target

Applies to: All campaigns
Condition: Conv. value/cost (ROAS) < [break-even tROAS] for last 7 days
Action: Send email notification
Frequency: Weekly (Monday morning)

Rule 2: Reduce Budget on Sustained Low ROAS

Applies to: Campaigns active more than 21 days (well outside Learning Phase for Google)
Condition: Conv. value/cost < [break-even tROAS] for last 14 days AND budget > ₹500/day
Action: Decrease budget by 20%
Frequency: Weekly

Rule 3: Scale Strong ROAS Campaigns

Applies to: All campaigns
Condition: Conv. value/cost > [scale threshold tROAS] for last 14 days AND Conversions > 20 in last 14 days
Action: Increase budget by 15%
Frequency: Weekly

The 20-conversion minimum prevents scaling a campaign that had 2 conversions at great ROAS, statistical noise, not a real signal.

Rule 4: Pause Campaigns With No Conversions

Applies to: All campaigns
Condition: Conversions = 0 in last 14 days AND Cost > ₹5,000 in last 14 days
Action: Pause, send notification
Frequency: Weekly

What automated rules do versus what you decide

The Hierarchy: What Automated Rules Do vs What You Do

Automated rules should handle

Budget reduction on sustained underperformers (mechanical, well-defined)
Budget increases on clear outperformers (mechanical, data-driven)
Creative fatigue pauses (clear signal-based)
Notification on anomalies (alerting, not deciding)

You should still handle

Campaign structure changes (new ad sets, new audience configurations)
Creative refresh decisions (what to launch next)
Kill decisions on campaigns that have been underperforming for 3+ weeks despite budget reduction
Strategic budget reallocation between channels
Any situation where context changes the interpretation (new product launch, seasonal shift, competitor activity)

The rule of thumb: automate the mechanical. Decide the strategic.

Common Mistakes When Setting Up Campaign Automation Rules

Mistake 1

Using 1-day ROAS as the trigger metric

1-day ROAS is too volatile, daily fluctuations will trigger rules constantly. Use 7-day or 14-day windows for any rule that takes action.

Mistake 2

Auto-pausing without a Learning Phase exclusion

Learning Phase campaigns naturally show below-target ROAS for the first 7 days. Auto-pausing during Learning Phase resets the clock and compounds the problem. Always exclude campaigns active fewer than 7 days from action-taking rules.

Mistake 3

Scaling in single large increments

A 50% budget increase on a single campaign can disrupt Learning Phase and destabilise performance. Scale in 15–20% increments, maximum once per week.

Mistake 4

Not recalibrating thresholds when margins change

If you run a 25% off sale, your break-even tROAS changes immediately. Old automation rules based on normal-price thresholds will scale loss-making promotional campaigns. Recalculate and update thresholds before every promotional period.

Connecting Automation Rules to Real POAS (The Missing Link)

Platform automation rules work on platform metrics, ROAS, CPA, spend. They can approximate your POAS thresholds through the tROAS conversion above, but they can’t see your actual returns data or COGS.

The gap

A campaign might show 3.5x ROAS (above your break-even threshold, triggering an auto-scale rule) while its real POAS is 0.85x because of a 22% return rate the platform doesn’t see.

The solution: Weekly manual POAS review as a checkpoint on top of automated rules.

Automated rules handle the daily mechanics, flagging, budget adjustments, creative pauses. Your weekly Layer 2 review (as outlined in the pillar blog) catches the cases where platform metrics and real POAS diverge.

Automated rules

Prevent wasted days.

Continuous flags, trims and scales on platform metrics.

Weekly POAS review

Prevents wasted weeks.

Real profitability judgment on return- and COGS-adjusted data.

Together: the most efficient campaign management system available to a D2C team.

Conclusion

Automated campaign rules translate your Scale/Hold/Kill framework from a weekly manual process into a continuous system. Budget compounds toward what’s working. Waste gets reduced before the next review. Creative fatigue gets caught before it destroys performance.

Build the rules. Set conservative thresholds. Check the automated actions weekly to ensure they’re firing correctly. And keep the weekly POAS review, automation handles the mechanical, but real profitability judgment still requires the human in the loop.

Rules handle the mechanics. Reviews handle the strategy. Both belong in your system.

Frequently Asked Questions

Can Meta Automated Rules optimise for POAS directly?

Not directly, Meta's rules work on platform metrics (ROAS, CPA, spend). Translate your POAS target into a tROAS equivalent (POAS Target ÷ Effective Margin %) and use that as your platform metric threshold. Weekly POAS review catches cases where platform ROAS and real POAS diverge due to return rates.

How often should automated budget rules fire?

Weekly for budget changes (more frequent changes destabilise Learning Phase). Daily for notifications and creative pause rules. Never more than 20% budget change in a single automated action.

Should I exclude Learning Phase campaigns from automated rules?

Yes. Any rule that reduces budget or pauses campaigns should exclude campaigns active fewer than 7 days or with fewer than 50 purchase events. Learning Phase campaigns show volatile, unrepresentative performance, acting on it reinforces the problem.

How does Flable AI complement automated campaign rules?

Flable shows real POAS per campaign (return-adjusted, COGS-adjusted), the number that platform automation rules can only approximate. Use Flable's POAS data in your weekly review to override or validate what the automated rules have done based on platform metrics.