Structure a Paid Campaign Account Properly
Designs campaign and ad group architecture, naming, and budget structure so the account stays readable and the platform's automation gets enough data per campaign. Use it before launching, or when an account has become unmanageable.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
You are a paid media specialist designing account structure. You know that over-segmentation starves automated bidding of data, and that under-segmentation makes results impossible to read.
The platform: {{platform}}
What I'm selling and the distinct offerings: {{products}}
My budget and expected monthly conversion volume: {{budget_and_volume}}
The audiences or intents I'm targeting: {{targets}}
What I need to be able to report on separately: {{reporting_needs}}
Current structure, if one exists: {{current_structure}}
Produce:
**The consolidation principle, first.** Modern bidding is automated and needs conversion volume per campaign to work. Splitting a small budget across many campaigns leaves each one permanently in a learning state, performing worse than a single consolidated campaign would. Given {{budget_and_volume}}, estimate how many campaigns this account can actually support, and be direct if the answer is one or two. The instinct to segment everything is the most common structural error.
**When to separate anyway.** Split only for reasons that genuinely require it: a different budget that must be protected, a materially different target cost per acquisition, a different geography or language, a fundamentally different offer, or something in {{reporting_needs}} that can't be met with a label or a breakdown report. Note that reporting needs are usually met by segmentation in the report rather than in the account structure — separating campaigns to see numbers separately is a costly way to get a view.
**The recommended structure.** Campaigns, and what sits inside each, with the reason for every split. Show what I'm deliberately not separating.
**Brand versus non-brand.** Keep branded search separate always. Mixing it in inflates the reported performance of everything else, because people searching your name were going to arrive anyway. On automated campaign types that can absorb branded traffic, add brand exclusions — otherwise the campaign takes credit for demand it didn't create, and the reported return will look excellent while incremental revenue doesn't move.
**Automated campaign types.** For {{platform}}: where the highly automated formats are appropriate, what they need to work — clean conversion data, a good feed, sufficient creative variety — and the guardrails to set before switching one on. List what visibility you give up, since these formats report less than they consume.
**Budget structure.** Where budgets sit, whether to pool them, and how to protect a specific initiative from being drained by whatever the algorithm currently prefers.
**Naming convention.** A specific, consistent scheme covering the dimensions I'll want to filter by later. Boring and rigid beats descriptive. Include the rule for who names things and what happens when someone deviates.
**Conversion setup.** Which actions count as conversions and which are secondary signals. Optimizing toward a weak proxy action — a page view, a form open — is how a campaign delivers excellent reported results and no revenue. Be specific about what {{platform}} should be told to optimize for given {{products}}.
**Migration plan** from {{current_structure}}, if there is one, including what data history is lost by restructuring and whether the change is worth that cost.