How many automation rules should I run on Facebook Ads?

Start with 2–3 (defensive rules to protect profit). Scale to 5–6 as you grow (add scale-up rules). Don't exceed 8–10 total; complexity creates conflicts. For €100k+ stores, 6–8 rules is typical and manageable.

Can I run conflicting automation rules in Meta?

Technically yes, but they shouldn't trigger on the same condition. Example: don't have 'pause if ROAS 1.9x' (overlap). Separate pause rules (threshold 2.0x) from scale rules (threshold 2.5x+) to avoid conflict.

Do Facebook automation rules work for CBO campaigns?

Partially. Rules apply to the whole campaign, not individual ad sets within CBO. If you want rule granularity, use ABO (Ad Set Budget Optimization) instead. CBO is simpler but less rule-friendly.

What happens to Meta's learning phase when an automated rule triggers?

If you pause before learning (~€40–50), you interrupt optimization. Meta has to re-learn when you un-pause (costs €10–20 in extra spend). This is OK; you're preventing bigger losses. If you pause after learning phase, no impact.

Facebook Ads Rules Automation: 12 Rules Every €100k/mo Store Runs

At €100k/month ad spend, you can’t manually manage 40–50 ad sets every morning. You’re either automating rules or leaving money on the table.

This is the complete ruleset for stores at this scale: 12 rules, organized in 3 tiers, with specific trigger conditions.

Start with Tier 1 (defensive). Add Tier 2 once you’re confident (optimization). Add Tier 3 only when you have a problem it solves (advanced).

Tier 1: Must-Have Rules (Defensive)

These four rules protect your profit. Every €100k+ store should run them.

Rule 1.1: Break-Even Kill

Trigger: ROAS < 2.0x after €150 spend for 3 days

Purpose: Pause campaigns at break-even threshold

Why €150 spend: Gives Meta ~150 clicks to optimize (past learning phase)

Why 3 days: Prevents killing campaigns on bad days

Action: Pause ad set immediately

Rule 1.2: Zero Conversions Emergency Brake

Trigger: €80 spent with zero conversions in past 48 hours

Purpose: Catch catastrophically bad creative/audience fast

Why €80: If you can’t convert anyone after €80, something is fundamentally broken

Why 48 hours: Gives 2 days of real-world performance data

Action: Pause ad set immediately (no waiting)

Rule 1.3: High-Frequency Burnout

Trigger: Frequency > 5 for 3+ days AND daily spend > €40

Purpose: Pause audience saturation to preserve future campaigns

Why frequency 5: Above 5, impressions generate minimal new conversions

Why €40 spend: Prevents false positive on tiny test audiences

Action: Pause ad set for 5 days, then auto-restart to rebuild audience appetite

Rule 1.4: COGS-Adjusted Profitability

Trigger: Revenue < (COGS + Fees + Ad spend + €10 profit target) after €100 spend

Purpose: Only possible with tools like Calatrix that access Shopify COGS

Why this matters: High-COGS product at 1.9x ROAS is actually unprofitable; you need 2.5x+ ROAS. This rule accounts for it.

Action: Pause ad set

Tier 2: Scale-Up Rules (Optimization)

Once your defensive rules are working, add these to double down on winners.

Rule 2.1: Winning Campaign Scale-Up

Trigger: ROAS > 3.2x for 5 days AND daily spend < €300

Purpose: Automatically increase budget on proven winners

Action: Increase daily budget by 25%

Rule 2.2: Expansion to Cold Traffic

Trigger: ROAS > 3.0x for 7 days in a retargeting ad set

Purpose: Once retargeting works, expand to cold traffic with similar creative

Action: Create a new cold-traffic ad set with same creative, budget €100/day (manual, then let automation take over)

Rule 2.3: Winner Duplication

Trigger: CPA < €20 (your break-even CPA) AND frequency < 2 (audience is fresh) AND ROAS > 2.8x for 4+ days

Purpose: Clone high-performing ad sets before audience saturates

Action: Duplicate ad set with same targeting/creative, split budget 50/50

Rule 2.4: Budget Reallocation from Losers

Trigger: Campaign has 1+ ad set at ROAS > 3.0x AND 1+ ad set at ROAS < 1.5x

Purpose: Shift budget from losers to winners automatically

Action: Reduce losing ad set budget by 50%, increase winner budget by 50%

Tier 3: Advanced Rules (Problem-Specific)

Only add these if you see the specific pattern in your data.

Rule 3.1: Weekday/Weekend Split Management

Trigger: (Mon–Fri ROAS > 2.5x) AND (Sat–Sun ROAS < 1.2x) for 2 consecutive weekends

Purpose: Pause unprofitable weekends, preserve profitable weekdays

Action: Create two campaigns from original: one Mon–Fri (scale up), one Sat–Sun (pause or test new creative)

Rule 3.2: Device-Specific Pausing

Trigger: Mobile conversion rate < 0.4% but desktop > 2% for 4+ days

Purpose: Stop bleeding budget on broken mobile experience

Action: Pause mobile placements in Ads Manager, keep desktop running

Rule 3.3: Cross-Campaign Cannibalization Detector

Trigger: Two campaigns with >70% overlapping audience AND combined ROAS < 2.5x

Purpose: Prevent wasted impressions on the same people

Action: Merge overlapping audiences or pause the lower-ROAS campaign

Rule 3.4: Seasonal Pause/Resume

Trigger: (Today is January 2 AND campaign tagged “holiday”) OR (Today is April 1 AND campaign tagged “seasonal”)

Purpose: Auto-pause seasonal campaigns outside their season; auto-resume when season returns

Action: Pause campaign; re-enable on specific date next year

The Rule Sequence (Order Matters)

Deploy in this order to avoid conflicts:

Week 1: Tier 1 Rules

Rule 1.1 (Break-even)
Rule 1.2 (Zero conversions)

Week 2: Add Tier 1 remaining 3. Rule 1.3 (High frequency) 4. Rule 1.4 (COGS-adjusted, if using Calatrix)

Week 3: Monitor, then add Tier 2.1 5. Rule 2.1 (Scale winners)

Week 4: Add Tier 2 remaining 6. Rule 2.2 (Expansion to cold traffic) 7. Rule 2.3 (Winner duplication) 8. Rule 2.4 (Budget reallocation)

Weeks 5+: Add Tier 3 as needed 9–12. Tier 3 rules (only if you see the specific problem)

Conflict Matrix: Which Rules Can Run Together?

Not all rules play nice together. Here’s the compatibility:

Rule	Conflicts with	Solution
1.1 (Break-even)	None	Run always
1.2 (Zero conv)	None	Run always
1.3 (Frequency)	None	Run always
1.4 (COGS)	None	Run always
2.1 (Scale)	None	Safe to run
2.2 (Expansion)	None	Safe to run
2.3 (Clone)	2.4	If 2.4 reduces budget, clone may duplicate. Stagger them: run 2.3 only after 2.4 fires.
2.4 (Reallocate)	2.3	See above.
3.1 (Weekday/weekend)	2.4	If reallocating budget, avoid this. Choose one.
3.2 (Device)	None	Safe to run
3.3 (Cannibalization)	2.4	If reallocating, avoid this. Choose one.
3.4 (Seasonal)	1.1	If campaign is paused for season, 1.1 won’t trigger (already paused). This is OK.

Key principle: Pause rules never conflict. Scale rules can conflict with other scale rules if they touch the same budget. Avoid running multiple scale rules on the same campaign.

Real-World Example: €100k/mo Store

Campaign portfolio:

8 campaigns
32 ad sets total
Mix of cold traffic, warm retargeting, brand awareness

Rules deployed:

Tier 1 (all active):

Rule 1.1: Pause if ROAS < 2.0x after €150 spend for 3 days
Rule 1.2: Pause if €80 spent, zero conversions in 48h
Rule 1.3: Pause if frequency > 5 for 3 days
Rule 1.4: Pause if margin < 18% (Calatrix)

Tier 2 (selective):

Rule 2.1: Scale if ROAS > 3.2x for 5 days
Rule 2.4: Reallocate budget from ROAS < 1.5x to ROAS > 3.0x

Tier 3 (active):

Rule 3.2: Pause if mobile conv rate < 0.4% vs desktop > 2%

Total rules: 7 active

Impact over 30 days:

Rules paused: 6 underperforming ad sets (saved €1,200)
Rules scaled: 2 winners (increased spend by €400, earned €900 additional profit)
Rules reallocated: moved €200 from loser to winner (gained €150 incremental profit)
Rules prevented: 1 mobile-broken campaign continued (saved €400)

Net savings: ~€2,400 additional profit in one month

Cost of tool to run these rules: €100/month

ROI: 24x

Implementation Checklist

Before deploying any rule:

Write down the trigger condition in plain English
Calculate the thresholds based on your margins (don’t copy blindly)
Set up notifications so you’re alerted when rules trigger
Test the rule in “preview mode” for 3 days (see what would have fired, don’t fire yet)
Check for conflicts with other active rules
Document the rule (keep a log of what it does and why)
After 7 days live, review triggered campaigns (confirm they were actually bad)
Iterate: if rule is too aggressive, raise threshold. If too conservative, lower it.

Common Implementation Mistakes

Mistake 1: Deploying all 12 rules at once

Result: Conflicts, over-pausing, panic.

Fix: Deploy 4 at a time, wait a week between batches.

Mistake 2: Using generic thresholds (not adjusted for your store)

Result: Rules based on someone else’s margins, kill your winners.

Fix: Calculate break-even ROAS for your store first. Then build thresholds around it.

Mistake 3: No spend qualifiers

Result: Rules fire during learning phase, kill campaigns that would have improved.

Fix: Always add “after €[minimum] spend” to every rule.

Mistake 4: No time qualifiers

Result: Rules fire on bad days without pattern.

Fix: Always require “for 3+ days” or “for 2 consecutive days.”

Maintenance: Monthly Review

Every month, audit your rules:

How many times did each rule fire?
Of those, how many were correct (paused actual losers)?
Of those, how many were false positives (paused would-be winners)?
Did the rule save more budget than it cost in false positives?

If a rule has >10% false positive rate, adjust the threshold.

Ready to Deploy?

Start with Tier 1. You’ll save money immediately.

Set up rules in Calatrix or in Meta Ads Manager for simpler setup.

At €100k+/month spend, automation pays for itself in the first week.

Let’s go.