How to Build a Campaign Naming Convention for Your Marketing Team

Open your Google Analytics traffic acquisition report and count how many variations of the same campaign you can find. Email, email, E-mail, newsletter, Newsletter, email_nl — all the same channel, all different names, none grouped automatically. This is the cost of no naming convention: fragmented data, unreliable comparisons, and hours wasted in cleanup spreadsheets before every reporting cycle.

A campaign naming convention is a set of rules that every person who creates a tracked link follows. It defines what goes in each UTM parameter, the exact format of values (lowercase, underscores not hyphens, no spaces), and the approved vocabulary for common values. The investment is one afternoon to build the convention and one training session to roll it out. The return is clean analytics data from day one and year-over-year comparisons that are actually meaningful.

utm_source identifies where the traffic comes from: the publisher, platform, or tool. Values should be specific and consistent: google, facebook, linkedin, newsletter, twitter, partner_hubspot. Never use generic values like social or paid — they tell you nothing you do not already know from utm_medium.

utm_medium identifies the channel type or marketing tactic: cpc, email, organic_social, affiliate, referral, retargeting, push, sms. This is the category above source. utm_campaign identifies the specific marketing initiative, product launch, or promotion: q3_summer_sale, product_launch_v2, brand_awareness_emea. utm_content distinguishes between multiple links in the same campaign (different ad creatives, different email CTAs, different banner positions): hero_image, text_link, sidebar_ad. utm_term is primarily for paid search keywords: project_management_software, buy_crm_tool.

Analytics tools are case-sensitive for UTM parameters. Facebook and facebook are different sources. Your naming convention must mandate a case format and enforce it. The industry standard is lowercase for all UTM values — no exceptions. Google Analytics 4 is case-sensitive and will split lowercase and uppercase values into separate rows.

Word separation is the next common inconsistency. Choose one separator and use it exclusively. Underscores (q2_summer_sale) are the most common choice because hyphens can be misread as minus signs in some contexts and spaces are URL-encoded as %20 which clutters URLs. Agree on a separator in your convention and document it with examples that show what NOT to use.

The most important part of a naming convention is a controlled vocabulary — a pre-approved list of values for each field. Without it, people make up new values every campaign and the fragmentation returns within months. Build a shared spreadsheet with one tab per UTM parameter and populate each with the approved values and their definitions.

For utm_source, list every traffic source your team uses with the exact lowercase name: google, facebook, instagram, linkedin, twitter, youtube, tiktok, newsletter, partner_[name], conference_[name]. For utm_medium, define the channel taxonomy: cpc, cpm, email, organic_social, paid_social, affiliate, referral, direct_mail, events. Mark any value not on the list as Not Approved and require a request process to add new values.

The utm_campaign field is where most inconsistency occurs because campaigns have creative names that people format differently. A structured naming formula solves this: YYYY_MM_INITIATIVE or YYYY_Q[quarter]_INITIATIVE. Examples: 2026_q2_brand_awareness, 2026_06_product_launch, 2026_q3_summer_sale.

The date prefix enables time-based filtering and year-over-year comparisons without any extra work. The initiative name uses the controlled vocabulary from your campaign taxonomy. This makes it possible to filter all Q2 2026 campaigns across every channel with one regex: ^2026_q2. Without this structure, a cross-channel Q2 analysis requires manually identifying and grouping campaign names.

A naming convention only works if everyone follows it. Document the convention in a shared wiki page that includes the approved values list, format rules, and example links for every common channel. Run a 30-minute training session when you launch the convention and include it in onboarding for new marketing team members.

Use a UTM builder tool (like the ShortIQ UTM builder) that validates against the naming convention. A builder with a drop-down for approved sources and mediums prevents typos and format violations at the point of link creation, before the link is ever shared. Some teams go further and create a bot that validates UTM parameters in campaign briefs or spreadsheets and flags any values not on the approved list. The more automated the enforcement, the less it depends on individual discipline.

If you already have months or years of inconsistent UTM data, audit it before rolling out the new convention. In Google Analytics 4, export the source/medium and campaign reports to a spreadsheet. Identify all the variations of each intended value and create a mapping table: E-mail, email, Email, newsletter all map to the canonical email.

In GA4, use channel groupings to remap historical values to the correct channel. You cannot retroactively change UTM values in historical data, but you can create a custom channel grouping that correctly classifies the existing traffic. Going forward, the new convention prevents new fragmentation. Quarterly audits for the first year catch any slippage before it becomes a large backlog.