HomeBrowseBlogShare
Home/Blog/How to Use the GA4 UTM Naming Convention SOP Prompt to Fix Default Channel Groups
Blog

How to Use the GA4 UTM Naming Convention SOP Prompt to Fix Default Channel Groups

P
promptstudio
Oct 5, 2026·4 min read

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.

How to Use the GA4 UTM Naming Convention SOP Prompt to Fix Default Channel Groups

Open the Traffic acquisition report in almost any GA4 property and you will see the same mess: Facebook / Paid, facebook / cpc, and fb / paidsocial sitting on three separate rows, plus a growing Unassigned bucket nobody can explain. The cause is rarely the analytics setup. It is the links. Different people build UTMs in different ways, and GA4 sorts traffic into its default channel groups using rules on source, medium, and campaign. A value that matches no rule lands in Unassigned. The GA4 UTM Naming Convention SOP That Lands Every Campaign in the Right Default Channel Group prompt writes a standard that is designed around those rules.

Why channel groups matter

Most marketing reporting starts with the Session default channel group dimension. It is how leadership sees Paid Social, Email, Referral, and Organic Search side by side. If your Meta ads land partly in Paid Social and partly in Unassigned, every channel comparison is wrong before anyone looks at a number.

GA4's default rules are specific. Paid Social expects a recognized social source plus a paid-style medium such as cpc or a value that starts with paid. Email matches when source or medium is email. Referral needs medium referral. Audio expects medium audio. A creative medium like webinar or audio_ad does not match any default rule. Casing also matters in reports, because Email and email show up as different values.

What the prompt delivers

  1. A diagnosis of your current values. You paste your real source and medium combinations, and the prompt groups the variants that split one channel and says where each currently lands.
  2. A controlled vocabulary for utm_source, utm_medium, utm_campaign, utm_content, utm_term, and utm_id if you need it, with the intended channel group for every allowed value and the forbidden variants it replaces.
  3. A utm_campaign pattern built from the parts your team filters by, such as quarter, product line, and offer, with one separator chosen and worked examples.
  4. Auto-tagging conflict notes. For example, Google Ads auto-tagging with gclid should not be combined with manual UTMs on the same final URL, and email platforms often append their own default UTMs that must match your vocabulary.
  5. A link builder sheet layout with dropdown validation and a concatenation formula idea.
  6. A QA checklist and monthly review inside GA4, with an owner.

How to fill the inputs

ChannelList should list only channels you actually run. The prompt will not invent new ones. CurrentUtms is the most valuable input: export the Session source / medium combinations from GA4, or paste your link sheet, warts and all. CampaignParts describes how people want to slice campaigns later. AutoTagging names tools that already add parameters, and LinkBuilders describes who creates links, because an agency and an intern need different guardrails.

Walking through the example

The sample team runs Meta and LinkedIn ads, organic LinkedIn, a weekly newsletter, partner webinars, and podcast sponsorships. The diagnosis finds that Meta traffic is split by casing and abbreviations, that LinkedIn paid and organic are mixed, that partner webinars use a medium that falls into Unassigned, and that the podcast medium does not match the Audio rule.

The fix is a small vocabulary. facebook / paid_social replaces three variants. LinkedIn is split by medium into paid_social and social. Partner webinars move to medium referral with the partner's name as source, unless the team decides to build a custom channel group for partners. Podcast reads use medium audio. Everything is lowercase, and the campaign pattern is a fixed order with underscores.

The monthly review is simple but easy to skip: in the Traffic acquisition report, switch to Session source / medium, filter for Unassigned, and fix or retire every new value. Logging fixes in the shared sheet teaches whoever created the stray value.

Mistakes to avoid

  • Writing a naming doc without a dropdown-based builder. People will not memorize a vocabulary.
  • Adding manual UTMs on top of ad platform auto-tagging. You can overwrite better data.
  • Inventing new mediums for each campaign type. Medium is what GA4 uses to decide the channel, so it should be boring and stable.
  • Changing the convention mid-quarter without a mapping note. Old and new values will sit side by side in reports.

Who it is for

This prompt fits marketing ops leads, analysts inheriting a messy property, and agencies onboarding a new client. It works from what you paste and does not invent traffic numbers, so the output can go straight into a team wiki.

Related PromptDig links