Every ad set already lives somewhere in the funnel. The architecture just makes that explicit.

Cold prospects, warm considerers, and people who already converted need different treatment. We assign each stage an objective and creative brief, then use exclusions to keep one budget from serving conflicting jobs. For teams running paid social past a single "Conversions" campaign who need prospecting, consideration, and retargeting to operate as connected stages.

A campaign architecture where you can point to any ad set, name its funnel stage, and explain the job it does.

A paid-social strategist mapping campaign stages from cold prospecting through to retention on a shared funnel board

Some of the 500+ brands we've worked with

See all references
  • Tazedirekt
  • Hepsikredi
  • Gusto
  • Yatsan
  • Akşam
  • Vispera

Stage definitions come first, then budget. AI may draft the map and flag gaps. It must not change stage exclusions or move spend. Those calls stay with the named human owners.

How we hold ourselves to it

  • Each stage gets its own objective and signal
  • Exclusions keep stages from competing for the same person
  • Handoffs are part of every stage review
  • AI drafts the map. Named humans approve the architecture.
  1. Define what each stage actually means here

    Translate awareness, consideration, and conversion into this business's real moments: first exposure, a specific engagement, and a qualifying action.

    Stage definitions translating awareness, consideration and conversion into this business's real moments.

    AI assist
    Drafts a stage-definition brief from historical campaign data and flags stages with no current owner.
    Human gate
    Strategy lead and client owner agree the stage definitions before anything is built.
    Owners
    Strategy lead + client owner
  2. Assign one optimization signal per stage

    Pick the objective and optimization event for each stage. A prospecting stage is then judged against its own signal and handoff.

    One objective and optimization event per stage, with its handoff named.

    AI assist
    Checks the proposed signal list against platform objective options and flags mismatches.
    Human gate
    Channel lead approves the signal-to-stage mapping.
    Owners
    Channel lead + media specialist
  3. Design the exclusion and sequencing logic

    Decide who moves from one stage to the next, who gets suppressed from prospecting once they convert, and how long someone stays in a retargeting pool before falling out.

    Exclusion and sequencing rules naming who moves on, who is suppressed and how long a retargeting pool holds someone.

    AI assist
    Drafts the exclusion rule set from the stage map and flags any stage with no suppression logic.
    Human gate
    A human approves every suppression rule before it goes live, especially anything touching sensitive audience data.
    Owners
    Strategist + privacy owner
  4. Build it paused, then check the map

    Construct the campaign and ad-set structure, naming, and exclusions in a paused state. Verify every stage against the agreed map before spend starts.

    Paused-build QA record verifying structure, naming and exclusions against the agreed map.

    AI assist
    Compares the paused build against the approved stage map and flags missing exclusions or mismatched objectives.
    Human gate
    A second reviewer signs off on the paused build before launch.
    Owners
    Media specialist + second reviewer
  5. Launch stage by stage and watch the handoffs

    Bring stages live in sequence, confirm each one is delivering against its own signal, and check whether a stage is actually feeding the next one at a reasonable volume.

    Staged launch log confirming each stage delivers against its own signal and feeds the next at real volume.

    AI assist
    Flags handoff volume that's dropped sharply or an exclusion that isn't suppressing anyone.
    Human gate
    An authorized media owner makes every live change to budget or targeting.
    Owners
    Media lead + channel lead
  6. Review how the stages work together

    Check whether the map still matches reality, promote or hold a stage's budget, and retire any stage whose role no longer matches its delivery and handoff evidence.

    Stage review recording each promote, hold or retire call and the handoff evidence behind it.

    AI assist
    Drafts an observation-first review brief comparing current delivery to the original stage map.
    Human gate
    Channel leads and the portfolio owner approve any stage promotion, hold, or retirement.
    Owners
    Channel leads + portfolio owner

The map explains the account's stages and rules to a new hire or client stakeholder before they need to open Ads Manager.

  • Funnel architecture map

    Every stage's objective, audience, creative mode, and exclusion rule in one view, so a new campaign's job is obvious before it's built.

    Accepted when

    Every stage's objective, audience, creative mode and exclusion rule are visible in one view before a new campaign is built.

    Cadence: Built at setup

  • Exclusion and sequencing register

    Who's suppressed from which stage, why, and for how long, so a converter showing up in prospecting is a bug someone can actually trace.

    Accepted when

    Each suppression names who, why and for how long, so a converter appearing in prospecting is traceable rather than arguable.

    Cadence: At every stage change

  • Paused-build QA record

    Evidence that the live account matches the approved map before spend started, including who checked it.

    Accepted when

    The live account was checked against the approved map before spend started, and the checker is named.

    Cadence: Per launch or rebuild

  • Handoff and stage decision log

    What each stage handed to the next, what changed, and which stage got promoted, held, or retired.

    Accepted when

    Each stage records what it handed to the next and which promote, hold or retire decision followed.

    Cadence: Weekly, deeper monthly review

One objective, three audiences, and a budget fight nobody scheduled. Cold prospects, people who've already engaged, and people who converted last month often end up in the same "Conversions" campaign under one cost target. The algorithm drifts spend toward whoever converts cheapest right now, usually the audience that was already close to converting.

A good fit when

  • Your paid-social account runs several objective types, but prospecting, consideration, and retargeting still compete inside one campaign shape.
  • A mid-funnel action is tracked, yet nobody can say whether it predicts the qualifying action the next stage is supposed to receive.
  • Prospecting has enough budget for its own test window, so it can be judged on stage delivery and handoff volume before CPA.
  • Prospecting and retargeting share a budget and bid goal.
  • A mid-funnel action (view, engagement, form start) is tracked, but nobody has checked what it predicts downstream.
  • Last month's top performer becomes the template for a campaign meant to fill a different stage.
  • No clear owner for the exclusion list, so converters keep returning to prospecting.

Better handled as other work when

  • One small campaign is still searching for a workable shape, so a three-stage architecture would arrive before the account has evidence for it.
  • Every campaign optimizes toward the same conversion event, so audience temperature and stage handoffs never affect the build.
  • There isn't enough volume for a top-of-funnel stage to gather evidence before the next decision.

Paid Search, Paid Social, CRO, and Programmatic each run under a named owner at Zeo. The consultants below are matched to the channel this page is about, so you can see who you'd actually work with.

  • Optmyzr

    moves budget between funnel stages as a portfolio decision, in a few clicks instead of campaign by campaign

  • Skai

    runs a distinct optimization algorithm per stage, with the exclusion logic between them

We walk your live campaigns against real funnel stages, mark where an exclusion is missing, and show where two stages are quietly spending against each other.
Map your funnel architecture

Naming is cosmetic. This method gives each stage a real optimization signal, an exclusion rule, and a success definition, then checks that the paused build matches all three before anything spends.