Consolidated Account Structure vs STAG
In short: These aren't really rivals - they operate at different levels of the same account and usually get built together. Consolidated structure is the account-wide decision to keep campaign and ad group counts low. STAG is the ad-group-level rule for which keywords belong together once you've decided how many ad groups to have. Most modern Search accounts consolidate campaigns and build STAGs inside them at the same time. Think of consolidation as the how-many-containers decision and STAG as the what-goes-in-each-one decision - you need both.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Consolidated Account Structure
Deliberately few campaigns and ad groups, so budget, conversion data, and bidding signal concentrate rather than splintering across dozens of thin containers.
Fewer, larger campaigns let automated bidding learn from a pooled conversion history and reduce the daily maintenance surface. It is the right default for small and mid-sized accounts, especially those on Smart Bidding or Performance Max. The cost is control: with everything in one bucket you cannot cap spend on a weak product line or region, so consolidate until you actually need a lever, then split only there.
Full definitionSTAG
Groups keywords that share one intent into a single ad group, so the ads and landing page can address that theme.
Single theme ad groups sit between SKAG fragmentation and full consolidation: a handful of semantically close keywords, one set of responsive search ads, one landing page. Most modern Search accounts land here because it preserves relevance while pooling enough conversions for automated bidding. The mistake is drawing themes too narrowly, which recreates SKAGs under a new name and starves each ad group of signal.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Consolidated Account Structure | STAG | |
|---|---|---|
| What it governs | How many campaigns and ad groups exist across the whole account. | Which keywords are allowed to share a single ad group. |
| Level it operates at | Account and campaign level. | Ad group level, inside whatever campaign structure already exists. |
| Can exist without the other | Yes - you can consolidate campaigns while still building SKAG-style single-keyword ad groups inside them, a common half-finished restructure. | Yes - you can build well-themed STAGs inside a highly granular, unconsolidated campaign structure. |
| What it fixes | Budget and data fragmented across too many campaigns or ad groups. | Message match and copy relevance lost when keywords are grouped too loosely, or data lost when they're split too finely. |
| Risk if pushed too far | Losing the ability to cap spend or bid differently where the business genuinely needs it. | Drawing themes so broadly that ad copy stops feeling relevant to some of the keywords inside it. |
| Where it shows up in the UI | Campaign list and ad group count at the account level. | The keyword list inside a single ad group's settings. |
| How they're usually adopted | As an account-level cleanup project, often alongside a bid strategy change. | As the default rule for building any new ad group, regardless of the broader restructure. |
What actually separates them.
Consolidation is a decision about container count; STAG is a decision about container contents - you can change one without touching the other.
A consolidated account can still contain SKAG-style single-keyword ad groups if nobody addressed the ad-group-level rule; STAG fixes exactly that gap.
STAG can be applied inside a highly granular, unconsolidated account just as easily as inside a consolidated one - it doesn't require fewer campaigns to work.
Pushing consolidation too far costs you campaign-level budget control; pushing STAG too far, with themes too broad, costs you ad copy relevance, which is a different failure with a different fix.
A full restructure typically changes both at once - fewer campaigns overall, and themed rather than single-keyword ad groups inside each - because doing only one leaves the other's problem in place.
Which one should you use?
Use Consolidated Account Structure when
- Your account has more campaigns than the business has real budget lines or targeting distinctions to justify.
- You're moving to Smart Bidding and want fewer, larger campaigns so it has enough data to learn from.
- You're spending more time managing campaign-level settings than reviewing performance.
- You want a starting point for an account-wide restructure, not just a fix to one ad group's keyword list.
Use STAG when
- You're deciding how to group keywords inside an ad group, regardless of how many campaigns exist above it.
- You're replacing SKAGs with a modern equivalent without necessarily changing campaign count.
- You want one coherent ad copy and landing page to serve a handful of closely related keywords.
- You're building a brand-new ad group and need a rule for what belongs in it.
Common questions.
Should I consolidate my campaigns or fix my ad groups first?
Either order works, but fixing ad groups by moving off SKAGs to STAGs is usually the faster win since it doesn't touch budgets or targeting settings other people may depend on. Campaign-level consolidation is the bigger project and worth planning separately once the ad-group layer is clean.
If I consolidate campaigns, do my ad groups automatically become STAGs?
No, those are separate changes. Merging campaigns just changes how many campaigns exist and how budget is shared; the keyword grouping inside each ad group stays whatever it was until you deliberately rework it.
Can a granular, unconsolidated account still use STAG ad groups?
Yes. STAG is about what goes inside one ad group, not how many campaigns or ad groups the account has overall. A tightly segmented account with many campaigns can have every one of those ad groups built as a proper theme rather than a single keyword.
Or stop choosing between them.
AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.
Related comparisons
- SKAG vs STAG
- Hagakure Structure vs SKAG
- Consolidated Account Structure vs SKAG
- Granular Account Structure vs SKAG
- Granular Account Structure vs STAG
- Consolidated Account Structure vs Hagakure Structure
- Granular Account Structure vs Hagakure Structure
- Consolidated Account Structure vs Granular Account Structure