Granular Account Structure vs SKAG
In short: Both increase the number of containers in an account, but for different reasons operating at different levels. Granular structure splits campaigns and ad groups along business lines - budget, geography, product margin - so you can control spend precisely. SKAG splits ad groups along a single keyword, purely to control message match. An account can be granular without using SKAGs, and a small account can accidentally combine both and end up unmanageable. Keep the granularity that maps to a real budget or targeting need, and drop the granularity that only maps to a keyword list.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Granular Account Structure
Many narrow campaigns and ad groups split by keyword, product, geography, or match type to maximize manual control over budget and messaging.
Splitting the account buys you precise budget caps, separate bid strategies, and reporting you can read at a glance. It genuinely helps large accounts with distinct margins, regions, or inventory that must not share spend. The failure mode is applying it to a small account: each container gets a fraction of the conversions, automated bidding never gathers enough data, and you spend your week managing structure instead of performance.
Full definitionSKAG
A legacy Google Ads structure putting one keyword in its own ad group so every query maps to tightly matched copy.
Single keyword ad groups gave advertisers manual control over message match back when exact match meant exact. Close variants ended that: the same query can now enter several ad groups anyway, and splitting keywords fragments conversion data that Smart Bidding needs. Treat SKAGs as history rather than a plan. Accounts still built this way usually show hundreds of low-volume ad groups, none with enough data to bid intelligently.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Granular Account Structure | SKAG | |
|---|---|---|
| What decides where the split happens | Business boundaries - a product line, a region, a margin difference, a budget owner. | A single keyword and nothing else. |
| Scope of the split | Campaign level and ad group level - budgets, locations, and bid strategies can all differ across splits. | Ad group level only - the campaign, budget, and bid strategy are usually shared. |
| Purpose | Precise control: cap spend on a weak line, target a specific geography, protect a high-margin product's budget from a low-margin one. | Message match: guarantee one keyword maps to one specific ad. |
| Can it coexist with STAG ad groups | Yes - you can be granular at the campaign level while using themed, multi-keyword ad groups underneath. | No - SKAG defines the ad group's contents directly, so there's nothing left to theme. |
| Right-sized for | Larger accounts with genuinely distinct products, regions, or margins that must not share a budget. | No modern account size - the original use case, locking exact match, no longer holds since close variants expanded. |
| Reporting benefit | Campaign-level, P&L-style reporting you can read without a saved report or script. | Keyword-level reporting, which granular structure can also deliver without going to one keyword per ad group. |
| Failure mode | Applied to a small account, it fragments the same limited conversion volume across too many budget-siloed containers. | Applied at any scale, it fragments conversion data at the ad group level and adds ongoing negative-keyword upkeep. |
What actually separates them.
Granular structure splits along business reasons - what needs its own budget or targeting - while SKAG splits along keyword count alone, with no business logic behind the split.
Granular structure operates campaigns and ad groups; SKAG only ever operates at the ad group level, one keyword at a time.
You can build a granular account structure using STAG-style ad groups throughout, keeping the business-level splits without the keyword-level fragmentation SKAG adds.
Granular structure preserves or increases conversion data per split when the split maps to a real difference in performance; SKAG reduces conversion data per container regardless of whether any real difference exists.
Undoing SKAG inside a granular account only means merging keywords into themed ad groups within each existing campaign - it does not require flattening the campaign-level splits that granularity was built for.
Which one should you use?
Use Granular Account Structure when
- Different product lines or services carry different margins and cannot share one budget without the worse one starving the better one.
- You need to target different regions with different budgets, bids, or even different offers.
- A stakeholder or client wants to see spend and performance broken out by a specific line item, not blended together.
- One part of the account needs a different bid strategy than the rest - for example a brand campaign on manual CPC next to a Smart Bidding prospecting campaign.
Use SKAG when
- You are maintaining a legacy account exactly as built, without a mandate to restructure it.
- You need one keyword, like a trademark term, walled off from everything else for legal reasons.
- You are auditing an old account and SKAGs are part of what you're documenting before a rebuild.
- You are explaining why a granular-looking account is actually just SKAGs wearing campaign-level labels.
Common questions.
Is a granular account structure the same thing as building SKAGs?
No, they operate on different axes. Granular structure is about splitting campaigns and ad groups along business lines like budget, region, or margin; SKAG is specifically about giving one keyword its own ad group. An account can be granular at the campaign level while using multi-keyword themed ad groups, with no SKAGs anywhere in it.
My account is granular and still underperforms. Could SKAGs be the hidden cause?
Check whether the ad groups inside each granular campaign are themed or are actually one keyword each. It's common for an old account to look granular from the campaign list while every ad group underneath is a SKAG, which fragments conversion data at a level the campaign-level split doesn't show you.
Should a small account ever be granular?
Rarely, and if it is, keep the splits to the one or two dimensions that actually need separate budget control - don't also split by keyword the way SKAG does. Two genuine business lines each with a themed ad group beats ten thin containers every time.
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
- Consolidated Account Structure vs STAG
- Granular Account Structure vs STAG
- Consolidated Account Structure vs Hagakure Structure
- Granular Account Structure vs Hagakure Structure
- Consolidated Account Structure vs Granular Account Structure