Overview
An ad account structure planner helps a paid search manager redesign campaigns and ad groups before touching live spend. This playbook installs a structure map table and migration plan document so campaign, ad group, budget, naming, control, and cutover decisions stay in one reviewable place.
Use it when an account has outgrown its original setup: brand and nonbrand are blurred, ad groups carry mixed intent, budgets are hard to control, naming is inconsistent, or reporting no longer explains performance clearly. The output is a practical planning sheet replacement, not an automated platform editor.
Why you should plan the restructure before changing campaigns
Account restructuring can improve control, but it can also scramble reporting history and make performance shifts harder to diagnose. The risk is rarely one bad campaign name. It is losing track of why each budget, bid strategy, audience, geography, and conversion goal was separated in the first place.
Google frames account organization around account, campaign, and ad group levels in its performance guide. Campaign settings such as budget and bid strategy also shape delivery control, as covered in Google Ads campaign settings, which is why a restructure deserves a map before edits happen.
This playbook keeps the work boring in the right way. It makes current entities, proposed entities, protected areas, migration phases, validation checks, rollback triggers, and open decisions visible before anyone pauses, merges, renames, or rebuilds live campaigns.
Step-by-step
- 1Confirm the platform, account, campaign scope, restructure goal, reporting requirements, protected areas, and migration tolerance.
- 2Install the ad account structure workspace with a primary structure map table and a migration plan document.
- 3Map the current campaign and ad group structure from connected read-only account context, an export, an existing table, or user notes. Keep missing data visible instead of inventing details.
- 4Classify the role of each material entity, including reporting bucket, budget control, bid or conversion control, protected status, and the evidence behind the decision.
- 5Design the proposed structure with clear change types such as keep, rename, merge, split, move, create new, pause after cutover, or needs decision.
- 6Turn the map into a phased migration plan that preserves reporting continuity, keeps legacy entities available until validation passes, and gives the team clear rollback triggers.
- 7Summarize the ready moves, review-only rows, protected areas, naming decisions, and unresolved questions so the paid search manager can approve the restructure with less spreadsheet archaeology.
Frequently asked questions
Does this edit my ad account?
No. The playbook creates the planning workspace for a restructure. It can use account data or exports when available, but the default output is a map and migration plan for human review.
What does it replace?
It replaces the minimum useful account-structure planning sheet: the table where a paid search manager maps current campaigns to proposed campaigns, records budget and control decisions, and tracks migration safety.
Do I need a Google Ads connection?
No. A connection can make the current-structure read faster, but the playbook can also start from exports, pasted account notes, existing Juno tables, or a manual campaign list.
When should I run it?
Run it before a major account cleanup, campaign consolidation, naming overhaul, market expansion, product-line split, or migration from a legacy structure. It is most useful before platform edits begin.
