Meta Ads Operating System
End-to-end system for launching and scaling paid social.
The account structure is 20% of the work. The creative system is the other 80%. This playbook is about the 80%.
- Meta Ads in 2026 is a 3-loop system: offer, creative, and attribution.
- Clay + Common Room beat guesswork by feeding Meta 1:1 audiences and signal tiers.
- Framer + Relume replaces landing-page clutter; speed wins 2-day tests, not 2-week rebuilds.
- Northbeam + PostHog is the default stack; GA-style vanity reporting is dead.
- 11x + n8n replaces 1 SDR team for follow-up, lead routing, and creative feedback capture.
- 01Day 1: Audit 3 live Meta campaigns and map every ad set to 1 audience thesis.
- 02Day 2: Build 1 enrichment flow and export 3 audience tiers into Meta Ads Manager.
- 03Day 3: Draft 4 creative angles from 20 verbatim buyer phrases.
- 04Day 4: Ship 6 assets into 1 test campaign with clean UTMs and 1 naming rule.
- 05Day 5: Wire ad spend, site events, and CRM into 1 daily reconciliation query.
- 06Day 6: Set alerts for pricing visits, demo requests, and low-MER pauses.
- 07Day 7: Review winners, kill losers, and launch 2 new variants before Monday 09:00.
1. Build the account like an OS, not a media buy
Start with 3 layers: acquisition, retargeting, and signal recovery. Use Meta Advantage+ Sales for breadth, then isolate 1 value-based retargeting campaign for high-intent visitors from PostHog and Northbeam. Keep Attio as the source of truth, then sync qualified rows from Clay by firmographic tier and lead intent. Common Room and Keyplay decide who gets higher-frequency creative. 11x or Lindy handles post-click follow-up, so paid social is not carrying the entire conversion burden. If your account has 12 campaigns before 12 winning ads, you built a dashboard, not an OS.
- 01
Step 1: Collapse campaign sprawl
Run 3 campaign types only: 1 prospecting, 1 retargeting, 1 signal recovery. Use Meta Advantage+ Sales first, then split only when spend reaches 5x your target CPA. Keep naming strict: geo, offer, audience, creative angle, date.
Campaign: US | Demo | A+ Sales | Clay-intent | Founder-proof | 2026-07-08
- 02
Step 2: Push enriched audiences into Meta
Use Clay to enrich ICP rows, then send 3 tiers into Meta via audiences: hot, warm, and lookalike seed. Add Common Room to score product-qualified signals and exclude low-fit accounts. This gives Meta cleaner training than a generic pixel ever will.
Clay prompt: 'Score accounts 1-5 by ARR fit, hiring velocity, and recent site visits; export tier 4-5 to Meta.'
- 03
Step 3: Automate recovery and routing
Use n8n with Attio to route form fills, high-intent visits, and demo requests. Trigger 11x or Lindy when a lead hits score 80+, and write every touchback into Attio. That closes the loop between paid social and revenue without manual exports.
n8n trigger: when PostHog event = 'pricing_view_3x' and Attio stage = MQL, call 11x agent 'Jordan'.
2. Run creative like a 7-day release train
Creative is the primary lever in 2026, not targeting. Build 4 angle buckets: proof, pain, comparison, and objection. Use AdCreative.ai or Pencil for first-pass variants, then Arcads for UGC-style avatar ads and Runway or Google Veo 3 for motion cut-downs. Framer handles fast landing swaps, while Relume gives you a site structure that does not need a 3-week agency loop. Clay and Apollo AI feed real customer language into briefs, and Claude 4.5 Sonnet turns that language into 10 ad prompts. If a concept cannot produce 6 variants in 48 hours, it is not a concept.
- 01
Step 1: Mine language from actual buyers
Pull objections, triggers, and phrases from Common Room, Attio notes, and Clay enrichment fields. Use Apollo AI to cluster by role and intent. Feed the top 20 phrases into Claude 4.5 Sonnet for ad angles, hooks, and first-line copy.
Claude prompt: 'Turn these 20 customer phrases into 4 Meta hooks, each under 12 words, with 1 sharp proof point.'
- 02
Step 2: Ship 6 assets per angle
Use AdCreative.ai for static variants, Arcads for avatar-led explainers, and Runway for 15-second motion edits. Track each asset in Attio with an owner, a hypothesis, and a kill date. One angle should always have 6 assets so Meta can find the pocket faster.
Angle: 'No in-house ops hire needed' -> 2 statics, 2 UGC, 2 motion cuts.
- 03
Step 3: Automate creative QA
Use n8n or Trigger.dev to send each new ad into a review flow. Claude 4.5 Sonnet checks claim risk, brand voice, and CTA clarity. If the asset passes, push it to Meta; if not, open a task in Attio with a rewrite prompt.
Decision rule: reject any ad with 0 proof point, 0 CTA, or 0 audience specificity.
3. Instrument for decisions, not reporting theatre
Use Northbeam for paid-social attribution and PostHog for on-site events. June can track product-led movement if the funnel crosses into activation or trial. Attio stores the commercial truth; Meta stores delivery; Northbeam stores the blended read. Build one SQL layer in Cursor or Claude Code to reconcile revenue, spend, and cohort quality every morning. If your team is still debating 7-day click versus 1-day view in a slide deck, you are 2 quarters behind. The only useful question is whether the next 10% spend will keep MER above target.
- 01
Step 1: Define 1 event taxonomy
Track view_content, pricing_view, lead_submit, demo_booked, and activated. Map all events in PostHog, then mirror revenue stages in Attio. Use one UTM template and one naming convention for every Meta ad.
UTM rule: utm_source=meta&utm_medium=paid_social&utm_campaign={{campaign_name}}&utm_content={{ad_name}} - 02
Step 2: Reconcile spend to revenue daily
Use Northbeam for attributed revenue and Cursor SQL for blended analysis against Attio closed-won data. If Meta reported ROAS is 2.2x and Northbeam says 1.4x, trust Northbeam and inspect creative, not the dashboard.
Cursor query: join spend, pipeline, and closed-won by campaign_name for the last 14 days.
- 03
Step 3: Create agent alerts
Set a Clay or Common Room signal to trigger n8n when 3 high-fit accounts visit pricing in 24 hours. Fire an 11x agent to follow up, then log reply sentiment back into Attio and PostHog. This turns attribution into action.
n8n rule: if MER < 2.5x for 3 days, alert in Slack and pause bottom 20% of ads.
4. Scale only after the system proves it can self-correct
Scale is a governance problem, not a budget problem. Raise spend only when 3 conditions hold: creative win rate above 25%, MER above target for 7 days, and lead quality in Attio stable or improving. Use Keyplay and Common Room to keep exclusions tight as spend expands. Apollo AI and Clay should refresh ICP weekly, not quarterly. 11x can handle inbound qualification, but the RevOps layer still needs one operator using Claude Code or Cursor to audit spend, cohorts, and creative fatigue. If a team needs 6 people to launch 1 new ad set, the process is broken.
- 01
Step 1: Use scale gates
Increase budget by 20% every 72 hours only if MER and lead quality both hold. If performance drops, cut back 15% and rotate 2 new concepts from the backlog.
Scale gate: spend +20% only when 7-day MER >= 3.0x and Attio SQL rate stays above 18%.
- 02
Step 2: Refresh audiences weekly
Use Clay to re-score accounts, Apollo AI to detect new fit patterns, and Keyplay to adjust account tiers. Exclude low-fit engagement from Meta before frequency damages marginal returns.
Clay job: re-enrich top 5,000 accounts every Monday at 08:00.
- 03
Step 3: Run a weekly operator review
One operator reviews spend, creative fatigue, lead quality, and pipeline in Attio, Northbeam, and PostHog. Use Claude Code to generate a 1-page SQL summary and n8n to push actions into Slack. No meeting longer than 20 minutes.
Prompt: 'Summarise 7-day Meta efficiency, top 3 winning angles, and 2 scale blockers in plain English.'
What goes wrong
1 campaign per product feature
Collapse into 3 campaign layers and test features inside creative, not account structure.
Attribution arguments in slides
Use Northbeam, PostHog, and Attio with one daily SQL reconciliation.
Creative made from internal opinions
Mine 20 buyer phrases from Clay, Common Room, and Attio notes before writing 1 ad.
Manual lead routing
Use n8n plus 11x or Lindy to route, score, and follow up in under 5 minutes.
Scaling before landing-page fit
Fix Framer conversion flow first; no budget increase until CVR holds for 7 days.
Should we use broad targeting or tight audiences in 2026?▾
Use 1 broad prospecting campaign first, then feed it cleaner signals from Clay, Common Room, and Keyplay. Tight targeting only wins when your data quality is already strong. If spend is under 5x target CPA, broad usually beats over-segmentation because Meta needs 1 stable training loop, not 6 tiny ones.
Do we need a standalone attribution tool?▾
Yes, unless you enjoy guessing. Northbeam is the default for paid-social truth, with PostHog for on-site events and Attio for commercial stages. Meta reporting is useful for pacing, not for decisions. If attribution and CRM disagree by more than 20%, fix UTMs and event mapping before increasing spend.
What replaces a traditional SDR follow-up flow?▾
11x, Lindy, or Relevance AI replaces the first 80% of SDR work in 2026. One operator can manage routing, qualification, and follow-up through n8n, with replies written back into Attio. Cold SDRs are dead as a team function; one agent plus one operator is the new default.
How many creatives should we launch each week?▾
Launch 12 to 20 assets per week if you want a real learning loop. Use AdCreative.ai, Arcads, Runway, and Claude 4.5 Sonnet to keep production fast. If you are launching fewer than 6 assets weekly, the account will stagnate before Meta finds a durable winner.
When should we increase budget?▾
Increase budget only when 3 gates hold: MER above target for 7 days, creative win rate above 25%, and lead quality in Attio stable or rising. Use 20% increments every 72 hours. If frequency rises and CVR falls, spend is a vanity metric until creative refreshes land.
Get one system like this in your inbox each week
No fluff, no upsell. Unsubscribe anytime.