Direct answer
The short version.
A durable naming convention uses a small controlled vocabulary for the dimensions needed across platforms and reporting, while storing richer context in dedicated fields or an asset registry.
Key takeaways
Keep these three decisions.
- Use a controlled vocabulary.
- Keep concept IDs consistent across systems.
- Measure unmapped and manually cleaned data.
The operating problem
Naming systems fail when they depend on memory, mix several meanings in one token or change by operator. Long names become truncated, the same audience receives several labels and reports fragment what should be one category.
A practical system
Choose stable dimensions such as market, objective, offer, audience family, concept ID and launch period. Publish allowed values, separators and examples. Generate names from a shared sheet or tool, preserve platform IDs and map UTM parameters to the same taxonomy without overwriting automatic identifiers.
What to measure next
Track unmapped spend, duplicate labels, manual cleaning time and the share of assets that can join cleanly from production through media and analytics. A good convention makes reporting faster while remaining understandable to a new operator.
Primary and authoritative references
Sources used for context.
Frequently asked questions
Two useful follow-ups.
What fields belong in a campaign name?
Include only dimensions required for operations and joining, such as market, objective, offer, audience family, concept ID and date or flight.
Should UTMs repeat the campaign name?
They should align with the taxonomy, but each UTM parameter should hold one clear dimension rather than a duplicate unreadable string.