GA4

GA4 Unassigned Traffic From Meta, TikTok and Snapchat: The UTM Fix

Why paid social lands in Unassigned or Paid Other in GA4, a copyable UTM table for Meta, TikTok and Snapchat, and a custom channel group that fixes past reports.

Cover: Paid social, not Unassigned. Three ad links from Meta, TikTok and Snapchat whose UTM tags sort into a GA4 channel table, with one stray link dropping into an "Unassigned" bin.

Say you inherit a property on Sunday and the client’s first question on Monday is why Meta drove almost no sessions last month while "Paid Other" and "Unassigned" grew. Usually nobody broke GA4. Somebody typed a UTM value that GA4’s rules don’t recognise.

What GA4 does with a paid social click

GA4 reads utm_source and utm_medium from the landing URL and runs them through its default channel group. You can’t edit those rules. Four of them decide where your Meta, TikTok and Snapchat clicks end up:

  • Paid Social: the source is on Google’s list of social sites AND the medium matches ^(.*cp.*|ppc|retargeting|paid.*)$. In plain words, the medium contains "cp", is ppc or retargeting, or starts with "paid".
  • Paid Other: the medium matches that paid pattern, but the source isn’t a social, search, shopping or video site GA4 knows.
  • Organic Social: the source is a known social site, or the medium is social, sm, social-media or similar, and nothing paid matched first.
  • Unassigned: no channel rule matched at all.

Google publishes its source list as a download from the channel group help page. It includes facebook, fb, instagram, ig, messenger, tiktok and snapchat. It does not include meta, an (Audience Network) or msg (Messenger). That one gap explains a lot of the Paid Other rows in inherited properties.

Checked 19 Nov 2026

Where common paid social tags land

 GA4 channelWhy
facebook / paid_socialPaid SocialKnown social source, medium starts with "paid"
tiktok / cpcPaid SocialKnown social source, medium contains "cp"
meta / paid_socialPaid Other"meta" is not on Google’s social source list
an / paid_socialPaid OtherAudience Network’s code is not on the list either
tiktok / tiktokOrganic SocialSource is social, but the medium doesn’t look paid
facebook / social_paidOrganic SocialStarts with "social", not "paid", so the paid pattern misses
summer_sale_v2 / (not set)UnassignedAd name in the source and no medium at all

One more cause has nothing to do with UTMs. If the Google tag fires late, or consent mode is set up so that some hits arrive without a session start, GA4 can show perfectly tagged sessions as Unassigned. Google lists both in its "(not set)" article. If a whole platform is Unassigned while the URLs look right, check the tag setup (GA4 setup in Google Tag Manager, consent mode v2) before you touch the ads.

The UTM values that work, per platform

Use one source and one medium per platform, in lowercase, and let each platform’s macros fill in the names. The medium is the same everywhere so every platform lands in Paid Social and your cost imports can match it later.

Checked 19 Nov 2026

Copyable UTM pattern for paid social

 utm_sourceutm_mediumutm_campaignutm_termutm_contentutm_id
Metafacebookpaid_social{{campaign.name}}{{adset.name}}{{ad.name}}{{campaign.id}}
TikToktiktokpaid_social__CAMPAIGN_NAME____AID_NAME____CID_NAME____CAMPAIGN_ID__
Snapchatsnapchatpaid_social{{campaign.name}}{{adSet.name}}{{creative.name}}{{campaign.id}}
paid-social-utm-templates.txt
# Meta: Ads Manager > ad > Tracking > URL parameters
utm_source=facebook&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_term={{adset.name}}&utm_content={{ad.name}}&utm_id={{campaign.id}}

# TikTok: ad > URL parameters
utm_source=tiktok&utm_medium=paid_social&utm_campaign=__CAMPAIGN_NAME__&utm_term=__AID_NAME__&utm_content=__CID_NAME__&utm_id=__CAMPAIGN_ID__

# Snapchat: append to the website URL of the ad
utm_source=snapchat&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_term={{adSet.name}}&utm_content={{creative.name}}&utm_id={{campaign.id}}
  • utm_term is meant for keywords. On social, most teams use it for the ad set, as above. Pick one rule and keep it.
  • Meta placements: a single utm_source=facebook keeps Instagram traffic in the same row. If you need Facebook and Instagram split, Meta’s {{site_source_name}} macro writes short codes such as fb and ig, but its codes for Audience Network and Messenger fall into Paid Other unless your custom channel group catches them.
  • Snapchat: Snap’s documented URL macros cover campaign, ad set and creative names and IDs, with no ad-name macro. Name creatives the way you name ads, or type the ad name in as plain text.
  • TikTok: if you use TikTok’s built-in URL parameter option, check the values it fills in against your standard before launch.

The platform-side detail, including every macro, is in our Meta UTM guide and Snapchat UTM guide. Write the final pattern into your naming convention so the next buyer doesn’t invent a third medium.

Fix future data in four steps

Fix the tags

From the damage report to a tested click

  1. Pull the damage report
    In GA4, open Reports > Acquisition > Traffic acquisition, switch the dimension to Session source / medium and filter Session default channel group to Unassigned, Paid Other and Organic Social. Sort by sessions. Every row that belongs to a paid platform is a tagging fix.
  2. Trace each row to ads
    Export each platform’s ads with their destination URLs and URL parameters, and find which ads carry the bad values. Usually it’s a handful of templates copied across many ads.
  3. Fix the template, then the ads
    Update the standard string in your naming doc first, then the live ads. Editing a live ad’s URL can send it back to review on some platforms, so batch the edits and avoid doing them on a launch day.
  4. Test one real click per platform
    Open the final URL from each platform’s preview, check that every parameter survives redirects (language redirects and lowercase rewrites are common culprits), then watch the Realtime report for the new source and medium.

Fix past reports with a custom channel group

New tags only fix new sessions. For the months you’ve already reported, build a custom channel group. Google applies custom channel groups to past data in reports and explorations, which no tagging change can do.

  1. Go to Admin > Data display > Channel groups and create a new group (Editor role needed). Standard properties get two custom groups, 360 properties five, each with up to 50 channels.
  2. Start from a copy of the default group so organic channels keep their usual rules.
  3. Add a channel called "Paid Social (fixed)" built only from the bad pairs in your damage report. Conditions can use Source, Medium, Campaign name, Campaign id, Manual ad content, Source platform and Default channel group.
  4. Move it to the top. Traffic goes into the first channel it matches, so a fixed channel below Organic Social never fires.
  5. Save, then pick the group from the channel dimension menu in Traffic acquisition and re-run last month.
custom-channel-rule.txt
Channel: Paid Social (fixed)
Source  matches regex  ^(facebook|fb|ig|instagram|meta|an|msg|tiktok|snapchat)$
AND
Medium  matches regex  ^(paid.*|cpc|cpm|social_paid|tiktok|snapchat)$

Replace the values with the exact pairs you found; broad patterns can sweep real organic posts into paid. Two limits to know: edits to a custom group only apply going forward when the group is used in audiences or set as the primary channel group, and the Key events paths report and BigQuery export don’t use custom groups. GA4 also added a Source Group dimension in June 2026 that merges variants such as Facebook and Instagram, which helps for a quick look but isn’t a channel fix.

Where this goes wrong

  • A medium per buyer. One buyer writes paid_social, another cpc, a third paidsocial. All three reach Paid Social, but your reports show three rows and GA4’s cost connectors accept only one medium per platform.
  • The platform name as the medium. utm_medium=tiktok or utm_medium=snapchat files paid spend under Organic Social, and the client asks why organic grew while paid stayed flat.
  • The ad name in utm_source. Every ad becomes its own unknown source. Put names in campaign, term and content, never in source.
  • Macros from the wrong platform. A Meta macro pasted into a Snapchat URL, or a TikTok macro in Meta, arrives as literal text. Read a real landing URL, not the template.
  • Case drift. Channel rules ignore case, but reports and cost imports don’t: Facebook and facebook split rows and break cost matching.
  • Encoded characters and redirects. A plus sign, a %2B or a redirect that rewrites the query string can change or drop values. Test the final URL.

Do it faster with Whathead

Whathead connects Claude or ChatGPT to GA4 and to your ad accounts through one MCP server, so the damage report and the ad lookup happen in one conversation. Reads change nothing, and any write is shown as a preview until you confirm it.

  • “In GA4 property [name], show sessions and key events by session source / medium for the last 28 days where the session default channel group is Unassigned, Paid Other or Organic Social. Mark the rows that look like Meta, TikTok or Snapchat.”
  • “List my active Meta, TikTok and Snapchat ads whose destination URL has no utm_medium or a medium other than paid_social, with the corrected URL for each. Don’t change anything yet.”

For a standing check, the Whathead Google Sheets add-on can report Meta URL tags with the UTM source, medium, campaign, content and term already parsed, next to spend. Whathead is our product.

GA4 unassigned traffic: common questions

What does Unassigned mean in GA4?

It is the channel GA4 uses when none of its default channel rules match the session’s source and medium. For paid social it usually means a missing or unrecognised utm_medium, or a source GA4 doesn’t know.

Why is my Facebook traffic showing as Paid Other?

The medium matched GA4’s paid pattern but the source didn’t match its social list. utm_source=meta is the usual culprit; use facebook, fb, instagram or ig.

Can I fix Unassigned traffic retroactively?

Not in the raw data, but a custom channel group re-labels past sessions in reports and explorations. Fix the tags for future data and use the custom group for history.

What utm_medium should I use for paid social?

Anything that matches GA4’s paid pattern works. paid_social is the common choice because it reads clearly and starts with "paid". Use the same value on every platform.

Why does my TikTok ad traffic show as Organic Social?

The source is tiktok, which GA4 knows is social, but the medium doesn’t look paid, for example utm_medium=tiktok. Change the medium to paid_social.

Sources

Written by Ahmed Shahin, founder of Whathead. Last reviewed 19 November 2026.