Campaign names your reporting can actually read.
Generate compliant names from your own master data, and catch the ones that slip through.
What it does
Teams generate campaign, ad set and ad names from controlled lists — brands, markets, campaign types, funnel stages — so names are structured by construction. Compliance is monitored, and non-compliant names are flagged automatically.
Names are still created in the ad platforms themselves, so nothing can stop someone with platform access typing whatever they like. Taxonomy Manager doesn't police the platforms — it makes the compliant name the easy one to create, and catches it fast when a name slips through anyway.
Why compliance needs a system, not a spreadsheet
Nobody names a campaign badly on purpose.
The convention lives in a spreadsheet somebody made in 2023, and at five o'clock on a Friday, guessing is faster than finding it. Generation fixes that by making the compliant path the fastest path.
Catching it late is the expensive part.
Flagged in week one, someone renames the campaign. Found at quarter-end, you're reconstructing three months of spend by hand.
Conventions are a stack, not a single scheme.
The 2019 version, the one after the rebrand, the one the new agency brought in. Rules can apply from a point in time or from a specific entity ID onwards, so history keeps working — the ID-based cutoff matters most when nobody remembers exactly when a convention changed, but everyone knows it was around campaign X.
Continuity is the real payoff.
Change agency, rebrand, restructure your markets — your reporting history doesn't break. The alternative most people live with is "we can only compare back to when we changed the naming," which quietly amputates year-on-year comparison.
What's inside
Name generation from master data
Controlled lists, validation, compliant names in seconds.
Structured by construction
Because the name was built from your dimensions, the semantic layer isn't reverse-engineering anything from it.
See Semantic Layer →Automatic detection
Names created outside the process land as unmapped and get flagged, in a report, rather than being quietly wrong.
Alerting
Routed to whoever can fix it, while the campaign is live and the name is still changeable.
Compliance reporting
By agency, market and team, over time — something a client-side lead can take into an agency review, not just an internal QA log.
Historic and legacy conventions
Time and ID-based rule scoping, so old and new naming schemes coexist without breaking your reporting history.
A new marketing analytics framework.
Your analysts in control, every team and tool connected to trusted data.