Google Ads naming conventions: a quick guide to structuring your account

Open a Google Ads account that has been running for a few years and you'll usually find the same thing. A campaign called "Search 2," another called "Leads - New," a third called "Test - DO NOT PAUSE." Nobody remembers what the test was. The person who built it left two agencies ago.

A good name tells you what something is without making you open it. We covered this for Meta in our guide to Meta Ads naming conventions, and the payoff is the same here: faster decisions, cleaner reporting, and an account anyone on your team can read. But Google Ads is a different machine, so the convention needs to be built differently.

Why Google needs its own convention

Three differences drive everything below.

• Campaign type is the most important fact about a Google campaign. A Search campaign, a Performance Max campaign, and a YouTube campaign behave in completely different ways. In Meta, the objective is the headline field. In Google, the type is.
• The middle level is ad groups, not ad sets. In Search campaigns, ad groups are organized around keyword themes rather than audiences. Your naming logic has to follow the keywords.
• Clean campaign names pay off automatically in GA4. Google's auto-tagging carries your campaign names straight into your analytics. Name things well once and your reports inherit the structure for free. In Meta you have to do this work manually with URL parameters.

The structure, level by level

Pick one separator and keep the field order fixed. We use a vertical bar with a space either side, the same as our Meta convention, so reports from both platforms read the same way. Here's the full stack for a plumbing company running lead generation.

Campaign level: type and strategy

The campaign name answers two questions: what kind of campaign is this, and what is it for?

• Brand or client name. Essential if you manage more than one brand in the same account.
• Campaign type. Search, PMax, Shopping, Display, DemandGen, or YouTube. This field does the most work in the whole convention.
• Product or theme. What the campaign promotes. If you manage brand and non-brand search separately, and you should, make that distinction here too: Acme | Search | Brand next to Acme | Search | NonBrand-Services.
• Geo or date, optional. Useful when the same campaign runs in multiple regions, or for seasonal pushes like Acme | PMax | Full-Catalog | Q4.

Ad group level: keyword theme and match type

In Search, the ad group name should describe the keyword theme it contains.

• Keyword theme. The cluster the ad group covers, like Water Heater Install.
• Match type, if segmented. Water Heater Install | Exact next to Water Heater Install | Phrase. If you don't split match types into separate ad groups, drop this field. A field that's always empty is clutter.

For Display, Demand Gen, and YouTube campaigns, the ad group carries the audience instead, which looks more like a Meta ad set name: Remarketing-30d | In-Feed.

Ad level: format, message, variation

The ad name answers "which version is this?"

• Format. A short list in Google: RSA for responsive search ads, and the asset or video identifier for other campaign types.
• Hook or message. The offer, benefit, or angle. This field is what makes creative reporting readable six months from now: RSA | Same-Day Service | V1 next to RSA | Licensed and Insured | V2.
• Variation. V1, V2, and so on, so test versions stay distinct in reporting.

The Performance Max exception

PMax doesn't follow the three-level model. There are no ad groups and no individual ads, just asset groups, and Google gives you far less reporting visibility inside them. You can't name your way around that.

What you can do: name each asset group for its audience signal and product focus, so the structure is at least legible. Returning Customers | Best Sellers next to New-Prospecting | Seasonal tells you what Google is working with, even when the reporting won't.

That's the honest limit. A naming convention makes PMax easier to manage, not transparent.

When a label beats a longer name

Google Ads has a tool Meta doesn't: labels. Anything temporary or cross-cutting belongs in a label, not the name. Promo windows, test flags, budget review markers. Names describe what a thing is. Labels describe what's happening to it. A campaign named Acme | Search | Brand | BFCM-TEST-PAUSE-JAN is a name doing a label's job, and it will still say that in March.

Rules that keep it working

These carry over from our Meta convention, and they matter just as much here.

• One separator, used everywhere, by everyone. Mixing separators is what breaks filtering.
• Keep the fields in the same order every time. The second field always means the same thing. Consistent order is what lets you sort and filter by any part of the name.
• Short beats complete. Include what someone needs to tell things apart, and leave the rest in the settings.
• Write it down. A one-page reference for your team, with the fields, their order, and a few examples, is what keeps the convention alive after the person who set it up moves on.
• Rename legacy campaigns during a quiet week rather than living with two systems. Renaming doesn't reset learning, so there's no performance excuse to skip it.

A template you can copy

Start from these and adjust the fields to fit your business.

Setting this up takes an afternoon. Reading a well-named account takes seconds.

The bottom line: that trade pays for itself the first time you have to find out why spend jumped on a Tuesday. If your account has already reached the "Search 2" stage and you'd rather someone else untangle it, that's work we do all the time.