“A source naming system succeeds when a busy person can apply it correctly and a new colleague can read it without tribal knowledge. Constrain vocabulary, preserve raw values, and expose exceptions.
Diagnose the failure
Names drift when agencies, platforms, and sales use different spellings for market, project, audience, placement, or creative. Reports split one campaign into many rows or merge distinct work. A complex taxonomy fails if it needs memory. The system must make the correct name the easiest name to create and read.
Use a decision framework
Define a small schema: project, market, objective, channel, audience, creative version, and flight. Give each allowed values, examples, and an owner. Google’s URL-builder guidance explains that UTM values flow into acquisition reports; use that mechanism consistently, but never overload one parameter with several meanings or hide the human-readable offer.
A hypothetical real estate example
Implement and measure
Put the schema in briefs, builders, CRM picklists, and the QA checklist. Reject missing or invalid values before launch and keep a change log. Measure invalid rate, unknown share, split-row rate, and reporting time. If people bypass the rule, simplify it before adding controls; adoption is evidence about usability. A naming rule is successful when it survives handover between Gameel, platform operators, and the property sales desk. A rule people can explain aloud is more durable than a taxonomy only its author understands.
Put it to work
- Limit each field to an approved vocabulary.
- Put examples in tools people already use.
- Audit invalid and unknown values weekly.
Sources and visual credits
Illustrative photograph: Overhead desktop workspace (Unsplash). It does not depict the hypothetical example. Jeff Sheldon ugmonk · CC0 · Wikimedia Commons