Account-Level vs Campaign-Level Ad Assets: What Goes Where

The override mechanic decides which assets actually serve, and getting the level wrong means your best copy never shows.

· QueryCut

The short version

  • Google serves the most specific asset level it finds and does not merge levels, so campaign assets replace account assets of the same type.
  • Put stable, universal assets (main phone, generic callouts, core sitelinks) at the account level as a no-maintenance fallback.
  • Keep assets local when geography, language, offer, or funnel stage changes their ideal content.
  • Never add a single campaign-level asset expecting it to join the account set; build a complete replacement set instead.
  • Before relocating a non-serving asset, check asset-level impressions: it may be an ad rank issue, not a placement issue.

Set assets at the account level when the content is identical across every campaign and will not change: your main phone number, core sitelinks to pages like About or Contact, and a generic callout set. Keep assets at the campaign (or ad group) level whenever the message, offer, or landing path differs by product line, geography, or funnel stage. The reason this matters is mechanical: a campaign-level asset of the same type does not stack with the account-level one, it suppresses it. If you set campaign sitelinks, the account sitelinks stop serving for that campaign entirely.

The override rule that drives every decision

Google Ads resolves assets from the most specific level available. For any given asset type, the engine looks at the ad group level first, then the campaign level, then the account level, and it serves the most specific set it finds. It does not merge levels. This is the single fact that should govern where you place anything.

Say you have account-level sitelinks pointing to Home, Pricing, Reviews, and Support. You add two campaign-level sitelinks to a Black Friday campaign. That campaign now serves only your two Black Friday sitelinks. The four account sitelinks are gone for that campaign, not blended in. People get burned by this constantly: they add one campaign-specific sitelink expecting it to join the account set, and instead they amputate the account set down to one link.

The practical read: account level is your fallback layer. It fills gaps. The moment you specify the same asset type at a lower level, you are replacing, not supplementing. Plan the lower-level set as a complete set, never a single add-on.

What belongs at the account level

Put things here that are true everywhere and stable over time. The test is simple: if this asset should show on a campaign you have not built yet, and you would not want to remember to add it manually, it belongs at the account level.

Good candidates are your primary call asset (the main business line), a business-name and logo asset, a generic callout set describing universal selling points (Free Shipping, 24/7 Support, Family Owned), and structured snippets that describe your whole catalog. Account-level location assets tied to a Google Business Profile also make sense when every campaign serves the same physical locations.

The payoff is coverage without maintenance. New campaigns inherit these automatically, so you never launch a bare ad. For a small account with one product and one message, you could reasonably run almost everything at account level and keep campaign-level assets empty. That is not sloppy; it is correct when the message genuinely does not vary.

What belongs at the campaign or ad group level

Keep an asset local whenever its content is tied to the thing the campaign is about. Campaign-level sitelinks that point to specific product categories, promotion-specific callouts, a tracked phone number that routes by campaign, and price or promotion assets for a time-boxed offer all belong where they are relevant.

Geography is the most common forcing function. If you run separate campaigns by region, a location extension, a local phone number, or a city-specific callout has to live at the campaign level because the account-level version would be wrong half the time. The same goes for language: a Spanish-language campaign needs its own assets, because account-level English callouts would serve into it and read badly.

Funnel stage matters too. A top-of-funnel awareness campaign and a bottom-of-funnel branded campaign want different sitelinks (Learn More, How It Works versus Buy Now, Pricing). Because the lower level overrides, you can give each campaign a tailored complete set and trust that the account fallback never leaks in.

The failure modes nobody warns you about

The partial-override trap is the big one, described above: adding a single campaign-level asset silently kills the account set for that campaign. Before you add any campaign-level asset, decide whether you are building a full replacement set or whether you actually want the account version to keep serving. If the latter, do not touch the campaign level at all.

The second trap is auditing an inherited account. When you take over an account, the UI does not scream which level an asset lives at. Go to Campaigns, then Assets, and use the association view, filtering by level, to see what is set account-wide versus per campaign. Check a campaign that looks under-served and compare its associated assets against the account defaults. If a campaign shows only one sitelink, suspect an accidental override, not missing account assets.

The third trap is assuming assets always show. Even a correctly placed asset serves only when Google predicts it will improve performance and the ad rank clears the threshold for that format. You can have perfect account-level sitelinks that rarely appear on low-position mobile queries. Do not conclude an asset is misplaced just because it is not showing; check the asset-level impression data first under the Assets view before you move anything.

A decision procedure you can run this afternoon

For each asset type (sitelinks, callouts, structured snippets, calls, prices, promotions, images), ask one question: does the ideal content for this asset change across my campaigns? If no, set it at the account level and delete redundant campaign copies. If yes, set it at the campaign level for the campaigns that differ, and leave the account level as the fallback for everything else.

When you do push an asset down to the campaign level, build the full set in one sitting. For sitelinks that means at least four, because that is how many can show on desktop; shipping two means you cap your own display. For callouts, write at least four to six so Google has rotation room. Treat the campaign-level set as self-contained, because it is.

After any change, wait a few days and verify under Campaigns, then Assets, filtered to the specific campaign, that the intended set is associated and accruing impressions. If an account-level asset you expected to inherit is absent from a campaign, you have an override somewhere. If a campaign-level asset shows zero impressions after meaningful traffic, the issue is ad rank or relevance, not placement, and moving it will not help.

Questions people also ask

If I set sitelinks at both the account and campaign level, which ones show?

Only the campaign-level sitelinks show for that campaign. Google uses the most specific level available for each asset type and does not combine them. The account-level sitelinks will still serve on campaigns that have no campaign-level sitelinks of their own.

How do I tell what level an existing asset is set at in an account I inherited?

Go to Campaigns, then Assets, and use the association or level filter to separate account-level from campaign-level and ad-group-level assets. Compare a specific campaign's associated assets against the account defaults. A campaign showing far fewer assets than you expect usually means an accidental lower-level override, not a gap in account coverage.

Is it bad to run most assets at the account level?

No, if your message genuinely does not vary. For a single-product, single-region account, running sitelinks, callouts, and calls at the account level is correct and saves maintenance. It only becomes a problem when different campaigns need different content and the account-level version serves into places where it is wrong.

My account-level asset is not showing on a campaign. Does that mean it is placed wrong?

Not necessarily. First confirm no campaign-level asset of the same type is overriding it. If there is none, the asset is likely being withheld by Google because of ad rank, format eligibility, or a prediction that it will not help. Check the asset's impression data before concluding placement is the issue.

How many sitelinks should I add at the campaign level?

Add at least four, because desktop can display up to four sitelinks and shipping fewer caps your own display potential. Since the campaign-level set fully replaces the account set, treat it as complete rather than as an add-on to the account sitelinks.

More from the blog

Landing Page Experience: The Changes That Actually Move ItImpression Share Lost to Rank vs Budget: What Each One MeansHow Many Campaigns Is Too Many for the Budget You Have?Primary vs Secondary Conversion Actions: What Each One Actually Changes