Definition
A naming convention is a documented pattern that every name of a given kind must follow. It is usually written as a short sequence of fields with a separator between them, plus a closed list of allowed values for each field. Applied consistently, it turns names into data: a filter on one field isolates every brand campaign, a pivot splits spend by market, and a new colleague can read an account without a briefing.
The term is sometimes used narrowly for campaign names alone, but in practice one convention, or a family of related ones, covers everything that a report or a person needs to group:
- Campaigns, ad groups and ads in each advertising platform.
- Tracking parameter values, above all the UTMURL tags identifying traffic source. source, medium and campaign values that carry a visit's origin into analytics. Google's documentation on URL builders describes these parameters; the convention decides what goes in them.
- Analytics events and parameters, and the variables that feed them from the site's Data LayerA structured object on a web page that passes values to a tag manager for tags to use..
- Tags, triggers and variables inside a tag manager container.
- Audiences, conversion actions and files, wherever several people create them.
In practice: elements, separators and allowed values
A working convention settles four things, and writes them down in one place.
The fields and their order. Each name is built from the same elements, ordered from the most general to the most specific, so that sorting the list alphabetically groups it the way people think about it. The naming conventions guide for Google Ads sets out the usual fields for an ad account, including market, campaign type, funnel stage, product and goal, and how to choose their order from the question reports most often ask.
The separator. One character that never appears inside a value splits the fields, so a spreadsheet formula can break any name apart without ambiguity. A different character may join words inside a field.
Closed lists of values. Each field has a fixed set of abbreviations, so the same market is never written three ways. New values are added by agreement, not by someone typing a fresh one into a new campaign.
Case and characters. Tracking parameters are read exactly as written, so lower case only, no spaces and no characters with a meaning in a web address. The UTM and naming conventions guide explains why a medium typed in two cases becomes two values in analytics, and why the medium is where consistency matters most. The UTM and naming conventions template is a ready-made starting point with fields and allowed values to adapt.
Governance: templates, checks and exceptions
A convention decays as soon as more people build campaigns than know the rules. What keeps it alive is small and unglamorous: one owner who approves new values, one document that holds the rules, a builder sheet or form with dropdowns so nobody types a name by hand, a check before launch, and a regular look at the names that broke the pattern. The guide to campaign structure across channels treats the convention as a record of intent: once a name states what a campaign is for, a report showing it doing something else is an anomaly someone will notice. The measurement plan guide fixes the convention before launch, as one of the decisions a plan records, because every analysis without it starts with a clean-up. Inside a tag manager, the same logic applies to tags and triggers, and the container governance guide calls naming the cheapest governance there is.
Renaming has a cost that adding does not. Saved reports, scripts, filters and rules may match old names, so a change to the convention is made in a batch, with dependencies listed and a mapping from old names to new kept for anyone reading older reports.
A distillery shop stops sorting its report by hand
Peatmoss Distillery Shop ran 26 campaigns across search, social and email, each named by whoever built it: "Xmas gift sets new", "FB lookalike Nov", "whisky club promo 2". The monthly report took a day of manual tagging before spend could be split by market or objective. The team agreed a four-field pattern of market, objective, audience and launch month, with closed lists of 3 markets, 4 objectives and 5 audiences, and a matching lower-case campaign value for every tracked link. A build sheet with dropdowns generated each name and link. Two months later 24 of the 26 live campaigns followed the pattern; the 2 exceptions were found by a filter on names that did not split into four fields, renamed in one batch, and the report now groups spend automatically.
Related terms
UTMURL tags identifying traffic source. parameters carry the convention's values from a link into analytics, and the campaign value should repeat the platform's campaign name or a fixed short form of it so the two reports join cleanly. Channel GroupingRules that assign each visit or conversion to a channel, such as organic search or email, from its source, medium and campaign values. rules read the source and medium values, so a value outside the agreed list can leave visits in an unassigned bucket. The Data LayerA structured object on a web page that passes values to a tag manager for tags to use. passes values to tags, and its keys follow the same naming discipline as events. Every KPIA metric tied directly to an objective. reported by channel, market or campaign inherits the convention's consistency, or its absence.
Common confusions
- A naming convention is not a tidiness exercise. Names are often the only description of a campaign a report can read, so a broken name is missing data.
- Auto-tagging does not replace it. Platform click identifiers help within one platform; consistent names and parameter values are what let reports across platforms agree.
- The best pattern is not the point. Any reasonable pattern applied every time beats a clever one applied most of the time.
- Writing it down is not enforcing it. Without a builder, an owner and a pre-launch check, a convention drifts within months.
