Examples
Campaign Naming Convention Examples
Concrete naming patterns for Google Ads and Meta Ads, and the structure that makes them parse cleanly in every report.
Published June 23, 2026 · Updated September 22, 2026
Key takeaways
- A reusable structure looks like COUNTRY_OBJECTIVE_CHANNEL_PRODUCT_AUDIENCE_PLACEMENT_YYYYMM_VARIANT — the same field order applied to every campaign, on every platform.
- Each segment of a well-formed name maps to a controlled dictionary value, not free text — that is what makes it parseable back into structured data.
- The same structure works across Google Ads and Meta Ads; only the platform-specific values (like utm_medium) change.
- A convention only delivers value when it is enforced at launch — an unenforced convention becomes five spellings of the same idea within a quarter.
- Standardizing the date segment as YYYYMM (not MM/YYYY, not "June26") avoids the single most common source of sort and parse errors in campaign reporting.
A reusable structure
A strong campaign naming convention uses an ordered set of fields with controlled values. For example: COUNTRY_OBJECTIVE_CHANNEL_PRODUCT_AUDIENCE_PLACEMENT_YYYYMM_VARIANT, which produces names like MX_CONV_SEM_PROD_BROAD_SEARCH_202506_A.
Examples
Acquisition search: MX_ACQ_SEM_LEADS_EX_SEARCH_202506_A. Brand display remarketing: MX_BRAND_DISP_GEN_REM_YT_202505_B. Each segment maps to an official dictionary value, so the name parses cleanly into country, objective, channel, product, audience, placement, date, and variant.
| Example name | Country | Objective | Channel | Date |
|---|---|---|---|---|
| MX_ACQ_SEM_LEADS_EX_SEARCH_202506_A | MX | Acquisition | Search (SEM) | 2026-06 |
| MX_BRAND_DISP_GEN_REM_YT_202505_B | MX | Brand | Display / YouTube | 2026-05 |
| CR_CONV_SOC_PROMO_RET_FB_202509_A | CR | Conversion | Social (Meta) | 2026-09 |
Rules that keep it consistent
Fix the field order, use a single separator, control the allowed values, standardize the date format (YYYYMM), and validate every name before launch. A convention only delivers value when it is enforced — otherwise it becomes five spellings of the same idea.
Frequently asked questions
What is a good campaign naming convention example?
A good example follows a fixed field order with controlled values, such as COUNTRY_OBJECTIVE_CHANNEL_PRODUCT_AUDIENCE_PLACEMENT_YYYYMM_VARIANT — producing a name like MX_CONV_SEM_PROD_BROAD_SEARCH_202506_A, where every segment is a reportable dimension, not decoration.
Does the same naming convention work for both Google Ads and Meta Ads?
Yes — the field structure (country, objective, channel, product, audience, date) stays the same across platforms; only platform-specific values change, like the channel segment reading SEM for Google Ads versus SOC for Meta Ads.
Why use YYYYMM instead of MM/YYYY for the date segment?
YYYYMM sorts correctly as plain text (202506 sorts before 202509) and avoids locale ambiguity between US and international date formats. MM/YYYY or written-out months break both sorting and parsing.
What separator should I use between segments?
Any single, consistent separator works — underscore and hyphen are the most common. The separator itself matters less than using exactly one, consistently, everywhere, so names can be split back into fields programmatically.
How many fields should a campaign naming convention have?
Enough to cover what you actually report on — most teams land on 6-8 fields (country, objective, channel, product, audience, placement, date, variant). More fields add precision but also add length and friction; fewer fields limit what you can segment in reporting later.
How do I make sure a naming convention is actually followed, not just documented?
Validate names against the convention at the point of creation — checking field count, allowed values, and format before the campaign launches — rather than relying on a reference document that nothing enforces.
Put this into practice
Standardize and validate campaign names, UTMs, and metadata with UseTaxonomy.
Request accessCampaign taxonomy software →