#ga4 utm taxonomy

GA4 UTM Naming Convention SOP That Lands Every Campaign in the Right Default Channel Group

Write a UTM taxonomy for a marketing team that maps each source and medium value to the GA4 default channel group it will land in, flags values that fall into Unassigned, and ships a builder sheet layout and QA checklist.

Act as a marketing operations analyst who audits GA4 properties and writes UTM naming standards that survive handoffs between agencies, in-house teams, and email tools. You know GA4 assigns the default channel group from source, medium, and campaign rules, and that inconsistent casing or a stray medium value sends sessions to Unassigned. Inputs: - Channels and platforms the team actually runs (paid social, newsletters, partners, podcasts, SMS): [ChannelList] - Current messy UTM values exported from GA4 Traffic acquisition or a link sheet: [CurrentUtms] - Campaign naming parts the team needs to filter by (quarter, product line, region, offer): [CampaignParts] - Tools that add their own UTMs automatically (email platform, link shortener, ad auto-tagging such as gclid): [AutoTagging] - Who builds links (agency, interns, one ops person): [LinkBuilders] - Output format: [Format] - Language: [Lang] Generate: 1. Diagnosis of CurrentUtms. Group the pasted values, show the casing and spelling variants that split one channel, and say which default channel group each one currently lands in (for example Paid Social needs a social source plus a paid-pattern medium such as cpc or paid_social; Email matches email in source or medium; Referral needs medium referral; anything unmatched becomes Unassigned). 2. Controlled vocabulary. One table per parameter: utm_source, utm_medium, utm_campaign, utm_content, utm_term, and utm_id if the team needs campaign IDs. For each allowed value, give the intended GA4 default channel group, and list the forbidden variants it replaces. 3. utm_campaign pattern built from CampaignParts with a fixed order, lowercase, underscore or hyphen chosen once, and two worked examples. 4. AutoTagging conflicts. Explain where tools already tag (for example Google Ads auto-tagging with gclid should not get manual UTMs on the same link), and where the email platform appends its own values that must match the vocabulary. 5. Link builder sheet layout for LinkBuilders: column order, dropdown validation lists from the vocabulary, a concatenation formula idea, and a final URL column. 6. QA checklist and a monthly review step in GA4 (Traffic acquisition report by Session source / medium, filter for Unassigned) with an owner. Constraints: - Lowercase only for every value; say so explicitly because GA4 reports treat casing variants as separate rows. - Do not invent channels the team does not run or traffic numbers of any kind. - If a value could land in two channel groups, pick the one the team intends and explain the rule that decides it. - No em dashes.