How to Write a Google Ad Manager Campaign Naming Convention

Why naming conventions matter

If you've ever inherited a Google Ad Manager account with campaign names like test_final_v2_REAL or Nike - Homepage - April, you know the pain. Inconsistent naming makes reporting unreliable, handoffs slow, and automation impossible.

A good naming convention solves all three: it makes every campaign name self-documenting, machine-readable, and auditable.

The anatomy of a GAM campaign name

A well-structured GAM campaign name has between four and six segments separated by underscores. Each segment answers a specific question about the campaign.

A common structure looks like this:

Advertiser_Product_Placement_AdSize_StartDate

For example:

Nike_AirMax_Homepage_300x250_20260401

Breaking this down:

• Nike — the advertiser
• AirMax — the product or campaign line
• Homepage — the placement or page
• 300x250 — the ad size
• 20260401 — the flight start date in YYYYMMDD format

Rules to enforce

No spaces. Spaces break URLs, export files, and most ad server APIs. Use underscores only.

Date format is YYYYMMDD. Not April, not Apr26, not 04-01-2026. The YYYYMMDD format sorts chronologically and parses unambiguously.

TitleCase for text segments. Each word in a segment should be capitalised: SpringSale, not springsale or SPRINGSALE.

No special characters. Hyphens, slashes, and ampersands will cause issues in reporting exports and API integrations.

Adapting for your team

Not every team needs the same segments. A direct-response advertiser might include a Tactic or Audience segment. A publisher might include Region or Vertical.

The key is to define the convention once, document it clearly, and then audit every campaign name against it before it goes live. That's exactly what AdOps Auditor is built to do.

Using AdOps Auditor with GAM

AdOps Auditor includes a pre-built GAM template that enforces the convention above. Paste your campaign names, select the GAM template, and get an instant compliance score with plain-English explanations for every violation.

You can also customise the convention to match your exact taxonomy — just describe your rules in the convention field and the AI will apply them consistently.