---
title: Ad Campaign Consolidation Skill for Claude Code
canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/ad-campaign-consolidation
content_type: text/markdown
description: ad-campaign-consolidation by mbfinotti - Ad Campaign Consolidation reviews a fragmented paid account and recommends which campaigns and ad sets to merge.
---

# Ad Campaign Consolidation Skill

Title: Ad Campaign Consolidation Skill for Claude Code

> ad-campaign-consolidation by mbfinotti - Ad Campaign Consolidation reviews a fragmented paid account and recommends which campaigns and ad sets to merge.

Canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/ad-campaign-consolidation

Ad Campaign Consolidation reviews a fragmented paid account and recommends which campaigns and ad sets to merge or keep split. It also sets a migration order that avoids resetting learning. A solo marketer uses it when budget is spread too thin across too many campaigns.

## Key facts

- Installs: 25,803
- GitHub stars: 2
- Author: mbfinotti
- Repository: mbfinotti/advertising-skills
- Install command: `npx skills add https://github.com/mbfinotti/advertising-skills --skill ad-campaign-consolidation`
- Last updated: October 26, 2026

## What Ad Campaign Consolidation does

Plans merges of fragmented ad campaigns and ad sets without resetting platform learning.

Best for: Accounts with many small campaigns

Not for: Diagnosing why an account underperforms

- Recommends campaign and ad set merges
- Protects learning phases during migration
- Plans only and never changes the account

## SKILL.md

## Campaign Consolidation

Turn a fragmented multi-campaign account into a consolidation plan: what to merge, what to keep split, in what order, and how to judge the result. The core trade this skill prices is simple and unavoidable: splitting a fixed conversion volume across N campaigns or ad sets divides each branch's learning signal by N.

Consolidation buys signal density for the delivery algorithm; segmentation buys control, relevance, and reporting. Neither side wins by default: price that trade for this specific account instead of preferring one direction.

You recommend; you never execute. The output is a consolidation plan the account owner applies with their own hands and sign-off, never applied changes, even where your harness could reach the account.

This skill activates once fragmentation is already the suspected or confirmed problem. The broader "why is this account underperforming" root-cause work belongs to `mbfinotti/advertising-skills@ad-account-diagnostic`, which hands its fragmentation verdict to this skill - run the diagnostic first if nobody has established that fragmentation is the problem.

Consolidation is platform-endorsed, not a fringe opinion:

- **Evidence for:** the major social platform's own (since retired) five-pillar best-practice program listed account simplification as a pillar; the search-ads world has a named method for collapsing single-keyword structures into few intent-themed campaigns (see Platform Notes).
- **Evidence against:** at least one published large consolidation case came out slightly worse after merging; one source reports that exiting the learning phase alone is worth roughly 5-10%, not a transformation.

Treat consolidation as a hypothesis to test, never a guaranteed win. Do not oversell it in the plan.

### Interview

Ask before analysing anything.

- One question per message.
- Offer multiple-choice answers where possible.
- Skip anything already supplied by the user, the data, or a diagnostic handoff.

- Which platform(s)? (search / paid social / short-video / professional-network / several)
- B2B or B2C/ecommerce?
- Monthly spend, and monthly conversion count on the event the account actually optimises to? (This single pair decides most of what follows.)
- Current structure: how many campaigns, ad sets/ad groups, and active ads?
- What can you export, and at what granularity? (Per-branch per-day conversion counts are the working minimum.)
- What is the target CPA or ROAS - and is it derived from unit economics (margin, deal size, close rate) or inherited from a dashboard?
- Which segments exist as separate campaigns/ad sets today, and _why was each one split out_? (The load-bearing question - answers like "for the 2024 launch" or "the previous manager reported that way" versus "different margin per segment" decide the whole plan.)
- Who controls the budget, and is any split externally mandated (client contract, finance, a guaranteed spend per line of business)?
- What reporting does the business need preserved after the merge? (Contractual or operational - not "nice to have".)
- Are any branches currently in the learning phase, and is there an active cost spike or panic driving this request?
- How long is the sales cycle, when is the next peak season, and by what date must the result land? (A hard date promotes the fast, contained moves - `prune`, then `merge` - and rules out anything whose payoff needs a learning cycle plus a sales cycle.)
- Do you want a one-off win on this quarter's numbers, or a structure that keeps paying? (One-off promotes `prune` and `re-parent`; a compounding mandate promotes `merge` and, in low-volume B2B, `up-funnel`.)
- What is the effort ceiling: rebuild hours available, who must sign off, how much political capital the split owners cost you, and how reversible the change must stay? (A low ceiling caps the plan at `prune` and `re-parent`; only a high one funds a multi-phase merge.)

### Workflow

1. Run the Interview. Collect every answer before touching data.
2. **Inventory the current structure.** Map every campaign → ad set/ad group → ad, with each branch's daily budget, bid strategy, optimisation event, audience definition, and the stated reason it exists. If you can read the account's exports directly, build this yourself; otherwise emit the exact export steps and a table for the user to fill and return. Tag each split as _deliberate_ (someone can state a live business reason) or _archaeological_ (launch leftovers, a departed manager's reporting habit, an old test nobody closed) - a split nobody can justify is the cheapest merge available.
3. **Compute per-branch conversion volume against the platform's learning threshold.** Count conversions per branch over a lag-mature window (exclude days still accumulating attributed conversions), on the event the branch actually optimises for - never a downstream event the platform never sees. Compare against the platform's _documented_ threshold (see Platform Notes; re-verify against the live help page, these numbers drift). Where the platform documents no threshold, say so - do not import another platform's number.
4. **Run the budget feasibility test - it is independent of the volume test.** A branch can be above threshold in theory yet under-budgeted to ever reach it: minimum daily budget ≈ target CPA × exit threshold ÷ threshold period in days. A branch whose budget cannot buy its threshold is fragmented by funding even if its audience is large.
5. **Classify every branch** using the four states below. Never let "couldn't verify" collapse into a verdict.
6. **Test every existing split against the preserve-vs-collapse rules** (section below). A split survives only when a rule protects it; the learning cost of keeping it must be named in the plan either way.
7. **Apply the Evidence Gate** (section below). If it fails, the deliverable is not a merge plan - it is a statement of exactly what extra days, spend, or access would clear it.
8. **Produce the target structure.** Pick each group's move from Consolidation Moves below - the earliest rung its classification allows, not the most ambitious one.
   - For each merged group: the shared objective, offer, optimisation event, bid strategy, and budget level (campaign-level pooling vs per-branch budgets - see Budget Mathematics for when pooling recreates the problem).
   - For each preserved split: the rule that protects it and its budget floor.
   - Cover the segmentation question explicitly: which segments move into creative variants inside the merged structure (section below), and which keep structural separation.
9. **Produce the migration sequence** (Migration Mechanics below): phases, what gets built new vs edited, the control, the no-touch window, and the timing relative to peak season.
10. **Define the measurement plan and the re-check date** (Measuring section below): baseline, judgment window, pass threshold, rollback trigger, and who signs off. If your harness has persistent memory, memorise the inventory, classifications, plan, phase dates, and re-check date so the follow-up run starts from history; otherwise emit a short state block the user can paste into the next session.

### Classification States

Assign every branch (campaign or ad set) exactly one state, each with a one-line justification citing the volume test, the budget test, and the preserve rules:

- **`merge`** - below threshold (or budget-starved) and no preserve rule applies. Name the merge destination.
- **`keep`** - clears volume and budget on its own, or a preserve rule protects it. Name which.
- **`keep but re-parent`** - reporting or control must survive, but the bidding signal should pool. The branch stays separately reported under a shared budget and bid strategy (rung 3 below).
- **`insufficient evidence`** - the data cannot support any of the above. State what would clear it. This is a real state, not a failure to decide.

### Consolidation Moves, Ranked by Efficiency

Five moves chase the same goal - denser learning signal per branch. They are not equivalent, and the owner's real question is which one to spend this month's hours and sign-offs on.

- efficiency (signal recovered per hour and per sign-off spent): `prune` > `merge` > `re-parent` > `up-funnel` > `big-bang`
- value (signal actually recovered): `merge` == `big-bang` > `up-funnel` > `re-parent` > `prune`
- effort (build time, coordination, sign-off, reversibility): `big-bang` > `up-funnel` > `merge` > `re-parent` > `prune`
- compliance cost (the review each move triggers): `big-bang` > `merge` > `up-funnel` > `re-parent` == `prune`

1. **`prune`** - pause the branches nobody can justify and move their budget to the survivors in steps of roughly 20%. Near-zero build, instantly reversible (pausing does not reset learning), no sign-off past the budget owner. Fixes funding starvation, not duplicated audiences - which is why it leads the order without ending the job.
2. **`merge`** - build one merged entity per group, shift budget, then pause the originals. Building takes about an hour plus one learning cycle of patience per phase, and it's the move that genuinely recovers divided signal, though it stays reversible only while the legacy structure remains paused. Start with the archaeological splits, where no one defends the split and the political capital cost is nil.
3. **`re-parent`** - pool budget and bid strategy under a shared parent while each branch keeps reporting separately (the low-risk middle move practitioner Jyll Saskin Gales recommends for roughly-ten-campaign accounts), each with a minimum-spend floor. Same build effort as a merge, far less negotiation because the report survives - but it pools funding, not ad-set-level learning, so the volume test can still fail afterwards.
4. **`up-funnel`** - move the optimisation event to a higher-volume proxy (see B2B and B2C). Needs the tracking and CRM owners, a consent and data review, and a standing job keeping the proxy honest against real outcomes. Slow and compounding, and the only move that works when even the fully merged structure cannot clear the threshold.
5. **`big-bang`** - rebuild the whole account at once. Its theoretical value matches a phased merge; every branch relearns simultaneously, the result attributes to nothing, and any externally mandated split it dissolves needs finance, client, or legal sign-off first. Migration Mechanics rules it out for any live account - it is listed here so a plan can say why it was rejected.

Default: run rung 1 across the account, then rung 2 on the groups the preserve rules leave unprotected. Move up a rung when the one below has run its no-touch window and the volume test still fails.

**What this order starves is `up-funnel`.** It is slow, it costs a second team plus a standing job, and it sits at rung 4, so the escalation rule above reaches it only after three rungs have each burned a no-touch window - which is months. That is exactly backwards for the account that needs it most: where the conversions do not exist, no amount of merging conjures them, and every rung below `up-funnel` spends a learning cycle proving that again.

Promote it straight to first, ahead of `prune`, on one condition: the volume test shows that even the _fully merged_ structure would not clear the platform's threshold (see B2B and B2C). Do not walk the ladder to reach it - the arithmetic is available on day one.

This ordering is a default, not a law - it shifts with the account and with who executes it. Re-rank it against what you already know about this user:

- An account whose splits are all deliberate makes `prune` nearly worthless and `re-parent` the real first move.
- An in-house analyst who can run a holdout makes the bigger moves readable.

Their Interview answers move it directly too - a hard date promotes `prune` and `merge`, a compounding mandate promotes `up-funnel`.

A constraint the user actually stated does something different from re-ranking: it removes the rung. Delete it from the ladder and name it as deleted in the plan, with the constraint that killed it and what would revive it - the way rung 5 is already listed only so the plan can say why it was rejected.

- A tracking implementation nobody may touch deletes `up-funnel`.
- An effort ceiling that funds no multi-phase rebuild deletes `merge` and everything above it, leaving `prune` and `re-parent` as the whole plan.

Say so outright rather than ranking the deleted rung last. A move parked at the bottom of a ladder reads as future scope, and it comes back next quarter as a fresh proposal to whoever forgot the constraint.

### Evidence Gate

Refuse to produce a merge plan on data that cannot support it. All of these must hold before any `merge` classification becomes a plan:

- **Window maturity.** The counting window is lag-mature and long enough to be representative - at minimum one full learning cycle plus typical conversion lag; stretch to 4-6 weeks for long-cycle B2B.
- **Per-branch spend.** Each branch being judged has accumulated roughly 3x its target CPA in spend over the window - below that, zero conversions is plausibly noise, so the state is `insufficient evidence`, not `merge`. (Practitioner starting point: at a true cost-per-conversion equal to target, 3x spend showing zero conversions is about 5% probability. Recalibrate against the account's own variance.)
- **Attribution consistency.** All branches counted under the same attribution window and counting method, with no settings or tracking change mid-window. Never sum conversions across differing windows.
- **A real target.** The target CPA/ROAS feeding the budget math comes from unit economics, or is explicitly flagged as inherited and unverified - a plan built on an inherited dashboard target is built on sand, and must say so.
- **No panic restructuring.** If the account is mid cost-spike or a branch is inside the learning phase, do not restructure as a reflex - a learning reset often costs more than the spike. Diagnose first; delay the plan if needed and say why.

When the gate fails, state the arithmetic of what clears it and offer the clearing moves in this order - efficiency: missing export or access > more days at current volume > concentrating budget into fewer branches to accumulate per-branch spend faster.

- An export clears the gate today for near-zero effort.
- Waiting costs only calendar time, which the deadline answer may not have.
- Concentrating budget is itself a structural change and carries the same sign-off as a merge.

### Preserve or Collapse: Testing Every Split

A split survives only for a business reason, never for comfort or habit. Test each split against this list; anything unprotected is a merge candidate. This list is what keeps the skill honest - a plan that only ever says "merge" is wrong roughly as often as one that never does.

Keep the split when:

- **Unit economics differ materially per segment** - margin, deal size, or LTV. One target CPA cannot serve two segments with different economics; pooling them optimises for the wrong one.
- **Budget control is externally mandated.** A client contract or finance requiring guaranteed spend per line of business needs per-branch budgets; campaign-level pooling will not honour the guarantee. Removing such a guarantee needs explicit finance/client approval, not a footnote.
- **Regulatory, legal, or brand-safety separation is required.** Regulated ad categories (housing, employment, credit, political, pharma, gambling, financial services) can mandate structural separation and restricted targeting.
- **Brand vs non-brand intent would share one bid strategy.** Automation gravitates to the easiest conversions: brand eats the pool, non-brand growth starves, and blended ROAS looks healthy while the account goes blind where it matters. Keep them in separate campaigns with distinct bid strategies, and exclude brand terms from blended/automated campaign types.

Excerpt. The rest of the file is on the canonical page and in the source repository.

## Ad Campaign Consolidation FAQ

### Is Ad Campaign Consolidation safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

## Machine access

- [Sitemap](https://skillselion.com/sitemap.xml)
- [llms.txt](https://skillselion.com/llms.txt)
- [llms-full.txt](https://skillselion.com/llms-full.txt)
- [Developer resources](https://skillselion.com/developers)
- [OpenAPI spec](https://skillselion.com/openapi.json)
- [MCP handshake](https://skillselion.com/.well-known/mcp)
- [API catalog](https://skillselion.com/.well-known/api-catalog)
- [AI catalog](https://skillselion.com/.well-known/ai-catalog.json)
- [Pricing](https://skillselion.com/pricing.md)
- [Auth](https://skillselion.com/auth.md)
- [AGENTS.md](https://skillselion.com/AGENTS.md)
- [Contact](https://skillselion.com/contact)
- [Home](https://skillselion.com/)
