Do I need to UTM-tag my organic search results?

No. Organic clicks from google.com are auto-classified by our pixel as utm_source=google&utm_medium=organic. UTMs are only useful for paid-search landing pages that bypass Google Ads (e.g., a Performance Max ad redirect) or for content campaigns where you want a specific in-pipe campaign name.

What about Bing or DuckDuckGo organic search?

Same — bing.com and duckduckgo.com are in the 30-platform classifier (per GL#361). No tagging needed. They appear in the dashboard under utm_source=bing / utm_source=duckduckgo with utm_medium=organic.

When will the native GSC integration ship?

Active development. Star the integration on /integrations to get notified the moment it lands. The OAuth scope (webmasters.readonly) and the Search Analytics API surface are already documented; we're finalizing the per-query rollup pipe in Tinybird.

Can I forecast organic revenue today without native GSC?

Yes. Because organic Google clicks already attribute via auto-classification, organic search revenue is computable from visitor_payments rows where attributed_utm_source='google' AND attributed_utm_medium='organic'. The MMM channel-contribution model on /dashboard/analytics already includes organic search as a first-class channel.

Coming soon · Google Search Console integration

Google Search Console integration — coming soon

Native API integration for Google Search Console is in active development. Until then, you can attribute every Google Search Console dollar today with a two-step UTM-and-pixel bridge: tag your Google Search Console URLs with the UTM template below, paste the Admaxxer pixel on your storefront, and our 30-platform smart-referrer classifier (per GL#361) auto-attributes revenue with 365-day first-touch persistence.

Star the integration on /integrations FAQ

The bridge — use our pixel + UTM tagging today

Three steps. About five minutes total.

Step 1 — Install the Admaxxer pixel

If you haven't already, drop the Admaxxer pixel into your storefront's <head>. Works on Shopify, WooCommerce, BigCommerce, Squarespace, Wix, Webflow, and any custom storefront. See install instructions for 35+ platforms.

Step 2 — Tag every Google Search Console URL with UTMs

In the Google Search Console UI, append these query parameters to every destination URL:

utm_source=gsc — identifies Google Search Console as the source
utm_medium=organic — categorizes the channel type
utm_campaign=<your_campaign_name> — for per-campaign breakdown in MER, ROAS, and cohort LTV
utm_content=<creative_or_keyword> — optional, for per-creative reporting

Example tagged URL:

https://yourstore.com/best-running-shoes?utm_source=gsc&utm_medium=organic&utm_campaign=organic-2026-q2&utm_content=hero-creative

Step 3 — Revenue auto-attribution kicks in

The first time a visitor lands on your site from a tagged Google Search Console URL, the Admaxxer pixel writes the UTM tuple into localStorage for 365 days. Google Search Console doesn't expose a per-click ID parameter, so first-touch UTM persistence (365 days) is the canonical attribution path. When the visitor checks out — even months later, even from a different device that we stitch via email_hash — the order is attributed back to the original Google Search Console campaign on the visitor_payments row.

Tag once, our 30-platform classifier (including AI-chat referrers) does the rest.

What's already working today via UTMs

Revenue attribution per campaign — both last-touch and first-touch, on every order row.
Click-ID coverage — first-touch UTM persistence covers attribution; no click-ID needed for this platform.
Cohort LTV by acquisition campaign — 7 / 30 / 90-day windows, partial-refund-aware.
MMM contribution analysis — the channel shows up in the geometric-adstock model with full per-campaign granularity.
Cross-session stitch — first-touch UTMs persist 365 days, so a click in March that converts in August still attributes correctly.
One classifier, every channel — tag once and the 30-platform smart-referrer classifier (including AI-chat traffic) handles the rest with no per-source config.

What native integration will add when shipped

UTM tagging gets you accurate revenue-side attribution today. Native API integration adds spend-side reconciliation and platform-side reporting depth:

Per-query clicks, impressions, and average position from the GSC Search Analytics API.
16-month historical query backfill on first connect.
Keyword-cohort LTV: which organic queries drive customers with the highest 90-day repeat rate.
Paid-vs-organic cannibalization detection: which Google Ads keywords are cannibalizing organic clicks you'd get for free.
Organic search as a first-class MMM channel alongside paid Meta, paid Google, paid TikTok.

Google Search Console specifics

For organic Google traffic referred from google.com, the Admaxxer pixel auto-classifies the visit as utm_source=google, utm_medium=organic — no UTM tagging required for organic search clicks. UTM tagging is for paid-search landing pages NOT going through Google Ads itself (e.g., a Performance Max experiment outside GSC's organic surface) or for tracking specific GSC-driven content campaigns by name. When the native GSC integration ships, you'll additionally get per-query click + impression + position data merged onto the same row as ad-spend reconciliation.

Frequently asked

Do I need to UTM-tag my organic search results?: No. Organic clicks from google.com are auto-classified by our pixel as utm_source=google&utm_medium=organic. UTMs are only useful for paid-search landing pages that bypass Google Ads (e.g., a Performance Max ad redirect) or for content campaigns where you want a specific in-pipe campaign name.
What about Bing or DuckDuckGo organic search?: Same — bing.com and duckduckgo.com are in the 30-platform classifier (per GL#361). No tagging needed. They appear in the dashboard under utm_source=bing / utm_source=duckduckgo with utm_medium=organic.
When will the native GSC integration ship?: Active development. Star the integration on /integrations to get notified the moment it lands. The OAuth scope (webmasters.readonly) and the Search Analytics API surface are already documented; we're finalizing the per-query rollup pipe in Tinybird.
Can I forecast organic revenue today without native GSC?: Yes. Because organic Google clicks already attribute via auto-classification, organic search revenue is computable from visitor_payments rows where attributed_utm_source='google' AND attributed_utm_medium='organic'. The MMM channel-contribution model on /dashboard/analytics already includes organic search as a first-class channel.

Next steps

Install the Admaxxer pixel — 35+ platforms supported.
UTM best practices — canonical UTM templates for every channel.
Revenue tracking deep-dive — how the 30-platform classifier and 365-day first-touch model work end-to-end (GL#361).
Star the Google Search Console integration on /integrations — you'll be notified the moment native API support ships.