GA4 Auto-Tagging Conflicts: Google Ads vs Microsoft Ads vs Meta (2026)

What is auto-tagging and why do conflicts occur?

Auto-tagging is a platform feature that automatically appends a click identifier to landing URLs — gclid for Google Ads, msclkid for Microsoft Ads. GA4 reads these identifiers to attribute sessions to the correct campaigns.

The conflict occurs when both auto-tagging AND manual UTM parameters are present on the same URL. GA4 reads UTM parameters first; if UTMs are present, they override the click identifier attribution. The result: Google Ads sessions appear attributed to your UTM values (which may be different from what Google Ads would assign), Google Ads conversion import breaks, and the session is often misattributed to (Other) if the UTM values don't match GA4's channel group rules.

Platform-by-platform configuration guide

Google Ads

The rule: Use auto-tagging only. Never manually UTM-tag Google Ads URLs.

Correct setup:

• Google Ads → Settings → Account settings → Auto-tagging → ON
• No UTM parameters on final URLs or tracking templates

Why no manual UTMs: Auto-tagging sets google / cpc as source/medium in GA4 automatically. Manual UTMs override this. If you add ?utm_source=google&utm_medium=cpc, GA4 uses your UTM values — which looks the same but breaks Google Ads conversion import because the gclid-to-session matching is disrupted.

If you need UTM data alongside gclid (for cross-platform reporting in a BI tool), use a tracking template that preserves the gclid:

The gclid={gclid} addition ensures GA4 reads the gclid for conversion attribution even when UTMs are also present.

Verify: GA4 → Reports → Acquisition → Traffic Acquisition → Session default channel group = Paid Search and Session source = google both appear when campaigns are active.

Microsoft Ads (Bing Ads)

The rule: Use auto-tagging (msclkid) for Microsoft Ads conversion tracking, plus optional UTM parameters for GA4 channel attribution.

Microsoft Ads auto-tagging appends msclkid to landing URLs. GA4 does not natively read `msclkid` for attribution — GA4 needs UTM parameters to correctly attribute Microsoft Ads sessions.

Correct setup:

• Microsoft Ads → Settings → Auto-tagging → ON (for conversion tracking)
• Also add UTM parameters to every Microsoft Ads URL for GA4 attribution:

In Microsoft Ads tracking template:

The msclkid={msclkid} at the end passes the click ID to Microsoft Ads conversion tracking; the UTMs ensure GA4 attributes the session to Bing / cpc correctly.

Common mistake: Running Microsoft Ads with auto-tagging but no UTMs. Result: GA4 shows these sessions as Direct (no UTMs, no recognised referrer) or Referral (bing.com). Sessions appear to come from organic Bing search, not paid.

Verify: GA4 → Traffic Acquisition → filter Session source = bing AND Session medium = cpc. Confirm these sessions appear and their count correlates with Microsoft Ads click volume.

Meta (Facebook/Instagram)

The rule: Always use manual UTM parameters. Meta has no auto-tagging that GA4 reads natively.

Meta does have its own click identifier fbclid — but GA4 does not use fbclid for attribution. GA4 only uses UTM parameters for Meta session attribution.

Correct UTM setup for Meta:

Use Meta's dynamic parameters (wrapped in {{}}) in the Ad set URL parameters field for automated population.

The `paidsocial` medium: Must be paidsocial (no underscore, no space) or paid social (with space) for GA4 to assign the session to the "Paid Social" default channel group. The underscore variant paid_social falls into (Other).

Instagram: Use utm_source=instagram (not facebook) for Instagram-placed ads if you want to distinguish Instagram from Facebook in GA4 reports. Some advertisers use utm_source=meta for all Meta placements — this falls into (Other) as "meta" isn't a recognised social source. Stick with facebook or instagram.

Verify: GA4 → Traffic Acquisition → Session default channel group = Paid Social. Filter Session source = facebook. Confirm sessions correlate with Meta Ads click volume.

TikTok

TikTok uses __PARAM__ format (two underscores each side) for dynamic values.

LinkedIn

LinkedIn uses {PARAM} format for dynamic values in its URL parameters field.

Pinterest

The conflict matrix

The (Other) diagnosis checklist

When traffic is falling into (Other) in GA4 channel groups, check these UTM issues in order:

1. `utm_medium` value mismatch — paid_social instead of paidsocial; Paid Search instead of cpc
2. Microsoft Ads missing UTMs — auto-tagging enabled but no UTM parameters → sessions appear as Direct
3. Google Ads UTM override — manual UTMs on Google Ads URLs without gclid preservation → sessions may appear as (Other) if medium doesn't match expected patterns
4. Unrecognised utm_source — utm_source=meta instead of facebook/instagram; utm_source=fb instead of facebook