Step 1: Audit what you already have
Before designing anything new, pull the last two or three months of live campaign names across every platform you run. Don't clean them up yet. Just look at what's actually there. You're hunting for the fields people already try to encode — region, channel, objective, date — and the inconsistent ways they encode them. This audit becomes your raw material, and it usually surfaces which fields matter enough that everyone was already tracking them informally anyway.
Step 2: Choose your fields and their order
Pick the smallest set of fields that covers how your team actually needs to filter and roll up performance later. Usually four to six. A common structure is REGION_CHANNEL_OBJECTIVE_CAMPAIGN-NAME_DATE. Fewer fields keeps names readable. Go past six or seven and people start abbreviating inconsistently just to make it fit, which defeats the whole point.
Step 3: Close every field to a fixed list of values
This is the step most naming conventions skip, and it's the one that actually matters. A free-text REGION field will eventually contain "NA," "N.A.," "North America," and "NAM" for the exact same thing. A closed list — REGION is NA, EMEA, APAC, LATAM, or GLOBAL, nothing else — is what makes the taxonomy machine-readable later. Every field needs this same discipline. Not just the obviously error-prone ones.
Step 4: Build a generator, don't rely on memory
A doc describing the schema gets followed for about a week. A generator — a form with dropdowns that assembles the final string — gets followed indefinitely, because it's easier to use correctly than to type from memory. This is the single highest-leverage step in the whole process. Worth building even if it's just a spreadsheet with data validation to start.
You don't have to build it from scratch to try this. KPI Compass has a free Taxonomy Builder that does exactly this — define your segments and their closed value lists once, then generate consistent strings you can copy straight into your campaigns. Three campaigns free, no signup.
Step 5: Check for drift on a schedule, not by accident
Taxonomy compliance decays the moment you stop looking. A freelancer launches a campaign the old way, or a field gets typo'd once and copied forward across a whole flight. Run every newly uploaded dataset through a compliance check that flags exactly which field on which string doesn't match a valid value — instead of waiting to notice drift the next time a rollup doesn't add up.
There's a free Taxonomy Checker for exactly this: upload a CSV and it auto-detects the pattern and flags which field on which string breaks it, right in your browser — files never leave your machine. Three checks free.
Rolling this out across a whole team or agency
Building this for the first time and don't want to design a schema from a blank page? An industry-specific starting point is usually faster than starting from scratch — a base set of fields and closed values common to your vertical, adjusted for your team instead of invented from nothing. Once the schema exists, the rollout matters as much as the design. Everyone who launches a campaign — including freelancers and agency partners who aren't full-time on your team — needs access to the generator. Not just a copy of the doc.
About the author
Zach Edelstein
Founder, KPI Compass
Zach has spent the last decade in data analytics, working both inside large media agencies and in-house at enterprise companies. He built KPI Compass because he kept hitting the same walls every BI team eventually hits — messy definitions, benchmarks nobody can verify, dashboards that quietly drift from reality. He's especially into where AI actually helps with this work, and he's still actively evolving KPI Compass to keep up with how fast the data landscape moves.
KPI Compass on LinkedIn