You know the problem. Someone asks "how did our Q1 campaigns perform across Meta and Google?" and the answer takes three days, two spreadsheets, and a lot of squinting at campaign names trying to figure out which ones belong to the same initiative. Or worse — nobody asks the question at all, because everyone knows the data isn't reliable enough to answer it.

If your team doesn't have a naming convention yet, you're not alone. Most marketing teams start without one and only realise they need one after the pain becomes impossible to ignore. The good news is that building a convention from scratch is a finite project with a clear end state — and this guide walks through exactly how to do it, step by step.

Before You Start: The Audit

Before designing anything, take stock of what exists today. Open your ad platforms and look at the last 50–100 campaign names across all platforms your team uses. You're looking for patterns — even informal ones.

Most teams that think they have no convention actually have fragments of one. Maybe one person consistently puts the brand first. Maybe there's an unspoken habit of including the quarter in campaign names. Maybe the agency uses hyphens and the in-house team uses underscores. These fragments are useful — they tell you what your team already instinctively wants to encode.

Write down what you find. List the platforms you're active on (Meta, Google Ads, TikTok, DV360, LinkedIn — whatever applies), note the naming patterns you see in each, and identify the biggest inconsistencies. This audit typically takes an hour and gives you the raw material for every decision that follows.

While you're at it, talk to two groups of people: the campaign managers who create the names and the analysts who consume the data downstream. Campaign managers will tell you what information they need to see in a name at a glance. Analysts will tell you what dimensions they need to slice performance data by in reports. The overlap between those two lists is your starting point.

Step 1: Choose Your Dimensions

Dimensions are the categories of information you encode in a campaign name. This is the most important decision in the entire process, because your dimensions determine what questions your data can answer.

Start with the analytical question: "What do we need to be able to group, filter, or compare campaigns by?" Every answer to that question is a candidate dimension.

Here are the dimensions most teams end up needing, roughly in order of how universal they are:

Almost always included:

Brand — Which brand or product is this campaign for? Even single-brand organisations often find this useful when they expand. Short codes work best: ACME, BRX, NIKE.

Market or Region — Geographic targeting. Use consistent codes: UK, US, DE, APAC, GLOBAL. If you operate at both region and country level, decide whether to encode one or both. Encoding both (e.g., EMEA-UK) gives you more analytical flexibility but adds length.

Campaign Objective — What is this campaign trying to achieve? Common values: AWR (Awareness), CON (Consideration), CONV (Conversion), RTN (Retention). Align these with your funnel stages, not with platform-specific objective names — Meta calls it "Awareness," Google calls it "Brand Awareness and Reach," but your dimension should use a single term.

Platform — Where the campaign runs. META, GADS, TIKTOK, DV360, LI. Some teams omit this because the platform is implicit (you're looking at Meta, so it's Meta). But if you ever do cross-platform reporting — and you will — having the platform in the name makes parsing and filtering trivial.

Frequently included:

Audience — Who the campaign targets. PROS (Prospecting), RTG (Retargeting), LAL (Lookalike), BROAD. This is typically encoded at the ad set or ad group level rather than campaign level, but some teams include it at campaign level when audience defines the campaign structure.

Campaign Type or Format — What kind of campaign this is. SEARCH, DISPLAY, VIDEO, SHOPPING, PMAX (Performance Max). Especially important on Google Ads where campaign type fundamentally changes the reporting context.

Time Period — When the campaign runs. Q1-2025, 2025-03, JAN25. Choose one format and stick to it. Quarter-based is the most common for campaign-level naming; month-based works for shorter flights.

Sometimes included (depending on complexity):

Creative Type — VIDEO, STATIC, CAROUSEL, HTML5. Usually at the ad level, not campaign level.

Funnel Stage — If you distinguish between awareness, consideration, and conversion at a more granular level than the objective dimension.

Product Line or Category — For multi-product brands. SHOES, APPAREL, ACCESSORIES.

Language — For multi-language markets. EN, FR, DE, TR.

Agency or Team — If multiple agencies or internal teams create campaigns and you need to distinguish ownership in reporting.

The critical constraint: fewer is better at the start. Every dimension you add makes names longer and the convention harder to adopt. Start with 5–7 dimensions at campaign level. You can always add more later, but removing a dimension from an established convention is painful.

A typical starting convention for a mid-size team might look like: Brand, Market, Objective, Platform, Period — five dimensions that answer the five most common reporting questions.

Step 2: Define Your Value Codes

Each dimension needs a controlled list of allowed values. This is where most conventions quietly fail — not because the structure is wrong, but because the values are inconsistent.

Keep codes short and unambiguous. If NA could mean North America or Not Applicable in your organisation, use NAM for North America. If CON could be Conversion or Consideration, use CONV and CNSD. Every code must be unique across all dimensions — no collisions.

Use consistent casing. Pick uppercase, lowercase, or title case and apply it everywhere. Mixed casing (Awareness in one dimension, RTG in another, uk in a third) makes names look sloppy and complicates parsing. Uppercase is the most common choice for codes.

Avoid spaces and special characters in values. A value like Brand Awareness will cause problems when it's embedded in a name that uses underscores as separators. Use BRAND-AWR or BRANDAWR or simply AWR.

Document every value. Create a reference table — a simple spreadsheet is fine at this stage — that lists every dimension, every allowed value, and its code. This becomes the single source of truth that the whole team references.

Here's what a minimal value reference looks like:

Dimension	Value	Code
Brand	Acme	ACME
Brand	BrandX	BRX
Market	United Kingdom	UK
Market	United States	US
Market	Germany	DE
Objective	Awareness	AWR
Objective	Conversion	CONV
Objective	Retargeting	RTG
Platform	Meta	META
Platform	Google Ads	GADS
Platform	TikTok	TIKTOK
Period	Q1 2025	Q1-2025

Step 3: Choose Your Separator and Ordering

Separator. Use the underscore (_). It's supported across all major advertising platforms, it's visually distinct from hyphens (which you may want to use within dimension values like Q1-2025), and it's the most commonly used separator in the industry. Unless you have a specific reason to use something else, underscore is the safe default.

Ordering. Place dimensions in order from broadest to most specific: brand first, then market, then objective, then platform, then period. This makes names scannable — when you're looking at a list of 200 campaigns in Ads Manager, the first few characters tell you the most important context.

Your campaign-level naming pattern now looks like this:

{Brand}_{Market}_{Objective}_{Platform}_{Period}

Producing names like:

ACME_UK_AWR_META_Q1-2025
ACME_US_CONV_GADS_Q1-2025
BRX_DE_RTG_TIKTOK_Q2-2025

Test your pattern by generating 10–15 example names and checking two things: can you read the name and immediately understand what campaign it describes? And can you split the name back into its individual dimensions unambiguously? If both answers are yes, the pattern works.

Step 4: Extend to Entity Levels

So far, we've designed naming for the campaign level. But most platforms have deeper hierarchies — ad sets/ad groups and ads/creatives — and each level benefits from naming governance.

The principle is: inherit shared dimensions from the parent, add level-specific dimensions at each child.

Campaign level: Brand, Market, Objective, Platform, Period — the strategic context.

Ad Set / Ad Group level: Inherits Brand and Market from the campaign. Adds Audience, Placement, or Targeting — the tactical context.

ACME_UK_PROS_FEED
ACME_UK_RTG_STORIES

Ad / Creative level: Inherits Brand and Market from the campaign and Audience from the ad set. Adds Creative Type, Version — the creative context.

ACME_UK_PROS_VIDEO_V1
ACME_UK_RTG_STATIC_V2

Not every team needs naming rules at every level from day one. If you're starting from scratch, begin with campaign-level naming. It delivers the most analytical value with the least adoption effort. Add ad set and ad-level naming once campaign-level is stable and adopted.

Step 5: Handle the Edge Cases

Every convention encounters situations that don't fit the standard pattern. Deciding how to handle them now, rather than ad hoc later, prevents the convention from degrading over time.

Optional dimensions. Some campaigns might not have a meaningful value for every dimension. A brand awareness campaign might not have a specific audience segment. You have two options: use a default value like ALL or GENERAL, or make the dimension optional and accept a shorter name. The first approach keeps segment counts consistent, which makes parsing easier. The second keeps names shorter but requires the parser to handle variable lengths. For most teams, default values are the simpler path.

New values. What happens when someone needs a value that doesn't exist in the controlled list? Define a process: they request it from the convention owner (usually the marketing ops lead), the value is added to the reference table with an agreed code, and only then does it get used. This is the single most important governance mechanism in the entire system. If anyone can add values unilaterally, the controlled vocabulary degrades within weeks.

Versioning. When a campaign is duplicated or refreshed — same strategy, new creative — how do you distinguish the new version? A version suffix (V1, V2) at the campaign or ad level is the simplest approach. Some teams use date-based versioning instead (Q1-2025 vs Q2-2025), which works when the refresh aligns with time periods.

Legacy campaigns. You don't need to rename every existing campaign. Retroactive renaming is risky (it can break tracking and historical reporting) and time-consuming. Instead, draw a clear line: all campaigns created after a specific date follow the new convention. Existing campaigns stay as they are. Over time, legacy campaigns age out of active reporting, and the proportion of compliant names increases naturally.

Step 6: Document and Distribute

Your convention now exists as a set of decisions. It needs to exist as a document that the entire team can reference.

The documentation should include four things: the dimension list with all allowed values and codes, the naming pattern for each entity level, example names showing the pattern in action, and the process for requesting new values. Keep it to one or two pages — brevity increases the chance people actually read it.

Where you store this document matters. It needs to be somewhere that the campaign team accesses regularly — a pinned Slack message, a bookmarked Notion page, a shared Google Doc. If it's buried in a wiki that nobody visits, it won't get used.

For teams managing more than a few campaigns per week, this is also the point where a generation tool becomes worthwhile. A shared spreadsheet with dropdown menus for each dimension eliminates manual typing and catches errors before they enter the ad platform. This is the transition from Level 2 (Documented) to Level 3 (Templated) in the taxonomy maturity model — and it's the step where naming compliance jumps from "mostly followed" to "consistently enforced."

Tuxonomy is designed specifically for this step and beyond. You can replicate your dimension list and naming patterns in a free workspace in under an hour, and the platform handles generation, validation, and team access from there — replacing the spreadsheet with a governed system that scales as your team and convention grow.

Step 7: Roll Out and Get Adoption

The best naming convention in the world is worthless if the team doesn't use it. Adoption is a change management problem, not a documentation problem.

Start small. Don't launch the convention across every team, every platform, and every market simultaneously. Pick one team or one platform — ideally the one with the highest campaign volume or the worst naming inconsistency — and roll out there first. Work out the friction before scaling.

Make it easier than the old way. If the new convention requires more effort than whatever people were doing before, adoption will be slow. Generation tools (spreadsheets or platforms) flip this equation: selecting from dropdowns is faster than typing freehand, and the output is guaranteed to be correct. When the governed workflow is genuinely easier than the ungoverned one, adoption follows naturally.

Assign ownership. Someone needs to own the convention — to approve new values, resolve ambiguities, answer questions, and monitor compliance. In most teams, this is the marketing ops lead or the most senior campaign manager. Without clear ownership, the convention drifts within the first quarter.

Show the value early. Within the first month, pull a cross-platform report that was previously impossible (or painfully slow) to produce. Show the team that consistent naming directly enabled a piece of analysis or a decision. This converts sceptics faster than any training session.

What Comes Next

Once your convention is documented, adopted, and producing consistent names across your primary platforms, you've reached Level 2–3 on the taxonomy maturity model. From here, the path forward follows a natural progression.

Expand to more entity levels. Add ad set/ad group and ad/creative naming conventions once campaign-level is stable.

Expand to more platforms. Apply the convention to platforms you initially excluded, adapting dimension sets to each platform's entity hierarchy.

Move from generation to governance. Replace the spreadsheet with a dedicated platform that centralises dimensions, enforces rules, and validates compliance. This is the Level 3 to Level 4 transition — and where the operational ROI is largest.

Connect to your data pipeline. Once names are consistent, the parsing step becomes reliable. Campaign names can be automatically decomposed into structured dimensions in your data warehouse, unlocking the cross-platform analytics that motivated the whole effort.

You don't need to do all of this at once. The most important step is the first one — going from no convention to a documented, adopted convention. Everything else builds on that foundation.