UTM & campaign tracking reference: structure links that attribute

UTM parameters are query-string tags you add to a link so analytics can attribute the visit to a campaign even when the referrer is missing. This page explains the five tags, a consistent naming convention, and the hard rule that UTM values are public — so they must never contain personal data or secrets.

Because so much Reddit traffic loses its referrer, UTM tagging is the reliable way to measure Reddit. This page gives a recommended utm_source/utm_medium/utm_campaign structure for Reddit links, worked examples, and the common mistakes that send Reddit visits into 'direct'.

LinkedIn is a high-intent B2B channel, but its mobile app and shortened links can drop the web referrer. UTM tagging keeps LinkedIn visits measurable. This page gives a recommended utm_source/utm_medium structure for organic posts and LinkedIn Ads, with the rule that no personal data belongs in a UTM.

X wraps outbound links in its t.co shortener, which commonly strips the web referrer — so without UTM tags, X clicks often land in direct. This page gives a recommended structure, explains why t.co makes tagging essential, and advises picking one utm_source convention (x or twitter) and never mixing them.

Email clients usually send no web referrer, so newsletter clicks need UTM tags to be attributed at all. This page gives a recommended utm_medium=email structure with per-send utm_campaign naming, and the hard privacy rule that subscriber identifiers must never appear in a UTM.

Clicks from YouTube description links and cards often arrive without a clean referrer, so UTM tags make video-driven traffic measurable. This page gives a recommended utm_source=youtube structure, a worked description-link example, and the privacy rule for campaign URLs.

Google Ads can attach a gclid automatically (auto-tagging) or you can add manual UTM parameters. This page explains how the two interact, why double-tagging a URL with both conflicting schemes causes confusion, and how to keep your utm_* values clean and consistent.

Microsoft Advertising (formerly Bing Ads) can attach an msclkid click identifier or you can add manual UTM parameters. This page explains how the two interact and how to keep utm_medium=cpc consistent so Microsoft paid search groups alongside your other paid channels.

Quora drives traffic from both paid ads and links inside answers, and those clicks can lose their referrer. UTM tagging keeps Quora measurable. This page gives a recommended utm_source=quora structure for ads and answer links, with worked examples.

Influencer campaigns are easy to measure if each partner gets a distinct UTM label. This page shows how to use utm_content per influencer, the privacy rule that keeps personal data out of URLs, and the honesty rule against inventing benchmark numbers.

Co-marketing only measures cleanly when both partners tag links the same way. This page shows how to agree a shared utm_source naming and campaign convention up front, so a joint campaign aggregates instead of fragmenting across two different schemes.

Referral programs need their own UTM medium so referred traffic is not confused with organic referrers. This page shows how to label the referral channel and explains why you must not encode individual user IDs in UTM — it leaks personal data and invites abuse.

A product launch spans many channels at once. This page shows how to use a single utm_campaign across all of them while varying utm_source per channel, so you get a clean total for the launch and a per-channel breakdown without fragmenting the campaign.

Podcasts are read aloud, so listeners type a URL rather than click — which makes attribution inherently approximate. This page shows how vanity URLs that redirect to a UTM-tagged destination capture what you can, while being honest about the limits.

A QR code is just an encoded URL, so encoding a UTM-tagged link turns print, packaging, and signage into measurable offline-to-online traffic. This page shows the structure, a worked example, and the rule that no personal data goes in the encoded URL.

Most UTM data problems are naming problems. Because tools treat utm_source=Reddit and reddit as different values, inconsistent casing and spelling fragment one campaign across many rows. This page gives a convention — lowercase, hyphenated, documented allow-list — that keeps reports clean.

Facebook commonly opens links inside its in-app browser, which frequently strips the web referrer, so untagged Facebook clicks land in direct. This page gives a recommended utm_source=facebook structure for organic posts and Facebook Ads, and the rule that no audience data belongs in a public URL.

Instagram allows few clickable links, so most traffic flows through a link-in-bio or a Stories link. Tagging those destinations with UTM is the only reliable way to measure Instagram. This page gives a recommended utm_source=instagram structure and the rule that no personal data belongs in a URL.

TikTok routes most clickable traffic through a profile bio link or paid ads, both of which can lose the referrer. UTM tagging keeps TikTok measurable. This page gives a recommended utm_source=tiktok structure for bio and ad links, with a worked example and the privacy rule.

Pins keep driving clicks long after they are posted, so Pinterest traffic is long-tail and arrives over months. UTM tagging keeps those delayed clicks attributable to the right Pin and campaign. This page gives a recommended utm_source=pinterest structure with a worked example.

Reddit drives both organic community traffic and paid ads, and lumping them under one medium hides what your spend actually did. This page shows how to keep Reddit Ads on utm_medium=cpc, distinct from organic utm_medium=social, so paid and community traffic stay comparable.

Snapchat is an app-first channel where links open in-app and rarely deliver a web referrer, so paid Snapchat clicks need UTM to be measurable at all. This page gives a recommended utm_source=snapchat structure for Snapchat Ads and the privacy rule for public URLs.

Display and programmatic ads need their own medium so banner clicks are not confused with paid search or social. This page shows how to use utm_medium=display consistently and explains how platform click IDs differ from the utm_* parameters generic analytics tools read.

Affiliate programs measure cleanly when each affiliate has a distinct, stable label. This page shows how to use a per-affiliate utm_source or utm_content for attribution, and why an affiliate's identity must be an opaque code rather than personal data in a public URL.

A webinar has several link touchpoints — the registration page, reminder emails, and the join link — and tagging them separately reveals which one drives results. This page shows a UTM structure that keeps registration distinct from reminders so attendance attribution is honest.

Conferences scatter your links across booth QR codes, talk slides, and printed handouts. Tagging each touchpoint distinctly turns an offline event into measurable traffic. This page shows a UTM structure that keeps booth, slide, and handout links separable under one event campaign.

SMS messages are tiny and links open in whatever browser the phone uses, so SMS needs short, UTM-tagged links to be measurable. This page shows how utm_medium=sms keeps text traffic distinct, and the privacy rule that a recipient's number or identity must never appear in the URL.

Push notifications drive re-engagement, but their clicks blur into direct or app traffic unless tagged. This page shows how utm_medium=push keeps notification-driven visits as a distinct channel, with a worked example and the rule against personal data in the link.

UTM parameters are manual labels you write; click IDs like gclid, fbclid, and msclkid are opaque identifiers a platform auto-appends. This page explains how they differ, which tools read which, and why setting conflicting manual and auto-tagged values on one URL causes double-counting.

Every UTM parameter is visible in the address bar, browser history, referrer headers, and server logs. This page sets the hard rule: a campaign URL must never carry personal data or a secret, and explains exactly where these values leak so the rule is concrete, not abstract.

When a visitor moves from one domain you own to another mid-journey, the original campaign source can be lost unless the UTM values carry across. This page explains how to preserve them and the session caveat that, without care, splits one campaign visit into two attribution records.

The two optional UTM tags get muddled constantly. utm_content distinguishes creatives or links for A/B comparison; utm_term carries the paid-search keyword. This page draws a clean line between them so each does its job and your reports stay legible.

UTM data degrades when everyone builds links by hand. This page covers the governance that prevents it: a shared builder or spreadsheet, documented allow-lists for source and medium, and a review step so new values are deliberate rather than ad-hoc.

UTM tags are excellent at labelling a click, but a customer journey has many touches and UTM only stamps the ones that pass through tagged links. This page is an honest account of the last-non-direct caveat and the limits of building multi-touch attribution on UTM alone.

Tagging links between pages of your own site is one of the most damaging UTM mistakes: a UTM on an internal click can start a new session and overwrite the original campaign source. This page explains the mechanism and what to do instead.

When a campaign link opens a native app instead of a web page, the UTM values have to survive a web-to-app handoff that does not always preserve query strings. This page covers passing campaign data into deep links and the caveats that can drop it along the way.

Not every email is a campaign. Marketing sends belong in your UTM-tagged campaign reporting; transactional emails like receipts, password resets, and notifications do not. This page draws the line so functional clicks never inflate your marketing numbers.

Casing is the single most common UTM data bug. Because tools match values as exact strings, utm_source=Reddit and reddit are two separate rows, so one campaign quietly fragments. This page makes the lowercase rule concrete and shows how to deepen it into real consistency.

Meta Ads (Facebook and Instagram paid placements) lets you attach UTM parameters at the ad level through the URL Parameters field or the destination URL. This page gives a recommended utm_source/utm_medium/utm_campaign structure, shows Meta's dynamic URL parameters such as {{campaign.name}}, and flags the cross-network pitfalls that blur Facebook and Instagram in your reports.

TikTok Ads Manager lets you append UTM parameters to the destination URL and supports dynamic tracking macros such as __CAMPAIGN_NAME__ that TikTok fills in at delivery. This page gives a recommended UTM structure for TikTok paid traffic, shows the macros, and explains why paid TikTok must be separated from organic profile links.

Outbrain and Taboola serve native content-recommendation ads across publisher sites. Both support UTM parameters on the destination URL plus dynamic tokens (for campaign, ad, and publisher) that they expand at click time. This page gives a recommended UTM structure and explains how to keep the two native networks distinct in reports.

Most UTM data problems are preventable with a validation step before links go live. This page describes what to check on every tagged URL — presence of the core parameters, lowercase consistency, proper URL encoding, no double question marks — and a lightweight QA workflow so broken or inconsistent tags never reach production.

UTM parameters do their job at the moment of capture; leaving them in the visible URL invites messy shares, duplicate-looking URLs, and accidental re-tagging. This page explains stripping UTMs with history.replaceState after your analytics has read them, and how to keep canonical URLs clean without losing attribution.

Analytics filters (internal traffic, developer traffic, bot exclusion, source overrides) can quietly change how UTM-tagged visits are reported. This page explains the safe ways to filter without dropping legitimate campaign data, and the filter mistakes that make UTM numbers look wrong.

X Ads (formerly Twitter Ads) sends paid clicks through the t.co wrapper, which obscures the originating campaign. Tagging destination URLs with UTM parameters is the reliable way to attribute paid X traffic. This page gives a recommended structure and explains how to keep paid X distinct from organic posts.

LinkedIn Campaign Manager lets you append UTM parameters to the destination URL of sponsored content and message/conversation ads. Because LinkedIn is a high-value B2B channel, clean paid-vs-organic separation matters. This page gives a recommended structure and the B2B-specific tagging notes.

Pinterest Ads Manager lets you add UTM parameters to the destination URL of promoted Pins. Because Pins keep driving traffic long after launch, clean tagging matters for measuring paid versus organic. This page gives a recommended structure and the Pinterest-specific notes.

Amazon Ads that send traffic to your own website — such as Amazon DSP placements or brand campaigns pointing off-platform — can be tagged with UTM parameters on the destination URL. Ads that land on an Amazon product or Store page cannot, because you do not control Amazon's URLs. This page draws that line clearly and gives a structure for the off-Amazon case.

Criteo runs retargeting and commerce display ads across the open web. Its destination URLs can carry UTM parameters so retargeting clicks are attributed to the campaign rather than to generic display referrals. This page gives a recommended structure and the retargeting-specific caution about crediting visitors who would have returned anyway.

Programmatic display bought through a demand-side platform (DSP) serves across countless publishers via real-time bidding. UTM parameters plus the DSP's dynamic macros on the landing URL are how those scattered clicks get attributed. This page gives a recommended structure and explains the macro approach common to DSPs.

Audio ads on Spotify and podcasts have no clickable link in the audio itself, so attribution leans on companion display banners (which can carry UTMs) and on spoken vanity URLs or promo codes. This page explains where UTMs do and do not apply to audio, and how to make spoken URLs measurable.

Redirects are where UTM attribution quietly dies. A 301/302 or a link shortener that does not forward the query string strips your tags before the visitor reaches the landing page. This page explains how to preserve UTM parameters through redirects, shorteners, and vanity URLs.

Tagged URLs get fetched by more than humans: crawlers, link-preview unfurlers, security scanners, and uptime monitors all follow UTM links. Counting them as campaign clicks inflates results. This page explains why bots hit tagged URLs and how to separate automated traffic from human campaign visits.

Consent banners and consent-mode setups change when and how campaign data is recorded. UTM parameters live in the URL regardless of consent, but whether they are written into a cookie-based analytics tool depends on the visitor's choice. This page explains keeping UTM attribution privacy-safe and consent-aware.

Over time, UTM values drift — Facebook and facebook, email and Email, newsletter and news — and split one channel into several report lines. A periodic UTM audit finds and consolidates that drift. This page describes a repeatable audit method you can run from your analytics export.

Offline media — TV, radio, print, out-of-home — has no clickable link, so UTMs cannot ride a click. Instead you give each offline placement a vanity URL, QR code, or promo code that redirects to a UTM-tagged landing page. This page explains designing that offline-to-online bridge.

Analytics tools sort traffic into channel groups (Paid Search, Organic Social, Email, Referral, Other) using rules built mostly on utm_medium. Choose the wrong medium and good traffic falls into 'Other' or the wrong channel. This page explains how the mapping works and the medium values that keep channels correct.

utm_id is a campaign-identifier parameter that analytics tools use to join UTM-tagged sessions with imported cost or campaign metadata. It is not a replacement for utm_campaign's human-readable name. This page explains what utm_id does, when to use it, and how it relates to the other parameters.

A space, an ampersand, or an emoji inside a UTM value can corrupt the whole query string if it is not percent-encoded. This page explains URL encoding for UTM values — which characters need escaping, why + and %20 differ, and how encoding mistakes truncate or split your campaign data.

Single-page apps (React, Vue, and similar) load once and then route in the browser, which can drop UTM parameters before analytics reads them. This page explains capturing UTMs on the first request, persisting them across in-app navigation, and the SPA pitfalls that silently lose campaign attribution.

Some ad platforms auto-tag clicks with their own identifier (for example a click ID), while you also add manual UTMs. Used together carelessly, the same click gets attributed two ways. This page explains how auto-tagging and manual UTMs relate, which to trust per channel, and how to avoid conflicts.

WhatsApp is a major sharing channel where links are pasted into chats and statuses. Because messages travel inside an end-to-end encrypted app, the destination site rarely sees a meaningful referrer, so untagged WhatsApp clicks usually land in direct or unassigned. Adding UTM parameters to links you put in WhatsApp click-to-chat buttons, broadcasts, and shared posts lets analytics attribute that traffic without inspecting any message content.

Telegram channels, groups, and bots are high-volume distribution surfaces where outbound links are common. Like other messaging apps, Telegram usually does not pass a useful referrer, so untagged clicks become direct. Tagging the URLs you post in Telegram channels, pin in groups, or send from a bot lets analytics attribute that traffic by source and campaign without reading any message data.

Discord communities share links constantly in announcement channels, topic channels, and via bots. Discord's client opens external links in a way that typically passes little or no referrer, so untagged clicks land in direct. Tagging the URLs you post in your server lets analytics attribute Discord-driven traffic by source and campaign, while link-preview fetches stay classified as bots.

Slack is a common internal and community distribution channel where links are pasted into channels, DMs, and posted by apps. Slack's link unfurling fetches URLs server-side, and human clicks often arrive with little referrer, so untagged Slack traffic tends to land in direct. Tagging the links you share in Slack lets analytics attribute that traffic by source and campaign while unfurl fetches stay classified as bots.

Community channels — owned forums, member Discords and Slacks, subreddits, and discussion boards — drive engaged traffic that is easy to lose to direct or referral noise. A consistent UTM convention across community surfaces lets you measure which communities and which posts actually send visitors, without scraping any member data. This page covers a naming approach that keeps many community sources comparable.

When you publish a guest article or contributed piece on another site, the byline and in-body links send referral traffic. Those clicks usually arrive with the host's referrer, but a UTM lets you separate intentional campaign links from incidental ones and compare which guest placements actually convert. This page covers tagging guest-post links so each host and article is measurable.

Press coverage and wire-distributed releases can send meaningful traffic, but it is hard to separate the link in your own release from links journalists add in their own coverage. UTM parameters on the URLs you place in press releases, media kits, and pitches let you attribute the traffic you directly drove, distinct from earned coverage you do not control. This page covers tagging PR links without overclaiming attribution.

A link-in-bio page is the single URL in a social profile that fans out to several destinations. Without tagging, every outbound click looks the same and you cannot tell which social platform or which button drove it. Adding UTM parameters to the destination links inside your bio hub, plus the bio link itself, makes each path measurable. This page covers a two-layer tagging approach for bio links.

App-store listings do not consume standard utm_ parameters the way a web page does — Apple and Google each have their own campaign-tracking mechanisms (App Store campaign links / Apple Ads attribution and Google Play referrer / the Install Referrer). When you drive traffic from web links to a store, you tag the web hop with UTMs, then hand off to the store's native parameter. This page covers that handoff so install attribution is not lost.

Direct-buy banners and sponsorships — a logo in a newsletter, a placement on a partner site, a sponsored section — sit outside the ad networks that auto-tag with click IDs. That means you must tag them manually with UTMs or the traffic falls into referral or direct. This page covers a convention for sponsorship buys so each publisher, placement, and creative is measurable.

Google Analytics 4 reads the standard utm_ query parameters and maps them to its session and traffic-source dimensions. The mapping is specific: utm_source, utm_medium, and utm_campaign feed the core dimensions, utm_id powers the manual campaign ID, and utm_source/medium combinations drive GA4's default channel grouping. Knowing the exact mapping prevents tags that look fine but land in the wrong channel.

Plausible is a privacy-first, cookieless analytics tool that reads the standard utm_ parameters and exposes them as Source, UTM Medium, UTM Campaign, UTM Content, and UTM Term properties. Because Plausible avoids cookies and cross-site identifiers, UTMs are the primary way to attribute campaigns. This page covers how Plausible consumes the parameters and groups acquisition sources.

Matomo supports campaign tracking through its own mtm_ parameters and can also be configured to read the standard utm_ parameters. The mtm_campaign and mtm_keyword tags map to Matomo's Campaigns reports, while utm_ values can be mapped via Matomo's campaign parameter settings. This page covers how Matomo consumes both schemes and where the data surfaces.

Server-side tracking reads the UTM parameters from the incoming HTTP request on your server, rather than relying on a browser tag to capture them. This makes campaign attribution resilient to ad blockers, script failures, and consent-gated client tags. The trade-off is that the server sees the landing request but must be designed to persist the campaign context across the visit. This page covers the mechanics and limits.

When GA4 is linked to BigQuery, campaign data arrives in the event export as nested event_params and traffic-source fields. The UTM-derived values — source, medium, campaign, content, term — are queryable with SQL via UNNEST, letting you build custom attribution beyond the GA4 UI. This page covers where UTM-derived fields live in the BigQuery schema and the basic query shape.

Looker Studio (formerly Data Studio) connects to GA4 and other sources to visualise UTM-driven campaign data. The GA4 connector exposes Session source, Session medium, Session campaign, and the manual content/term dimensions, which you place on tables and charts to build a campaign report. This page covers the connector dimensions and how to avoid common breakdown mistakes.

A UTM builder is a tool that assembles a tagged URL from your source, medium, campaign, and optional content/term values, so people do not hand-edit query strings and introduce typos. Builders range from Google's free Campaign URL Builder to spreadsheet templates and governed internal tools that lock taxonomy. This page covers the builder spectrum and how a builder enforces consistency at the point of creation.

A long UTM-tagged URL is ugly to share in print, social, or chat. A shortlink hides that behind a clean short URL that redirects to the full tagged destination, so attribution is preserved while the visible link stays tidy. The key requirement is that the redirect lands on a URL that still carries the utm_ parameters. This page covers how shortlinks preserve UTMs and the redirect pitfalls to avoid.

Campaigns that run in multiple languages or regions need a UTM structure that lets you compare both the campaign overall and each locale within it. The choice is where locale lives — folded into utm_campaign, split into utm_content, or carried in a dedicated convention. This page covers structuring localized UTMs so cross-locale comparison stays clean and rollups still work.

UTMs and first-party attribution solve overlapping but distinct problems. UTMs label the inbound link — which source, medium, and campaign brought someone in. First-party attribution uses your own data (logins, server sessions, consented identifiers) to connect touches into a journey. As third-party signals fade, the two are increasingly used together. This page covers how they complement each other and where each is strongest.

UTM parameter values are case-sensitive in most analytics tools, so Email, email, and EMAIL count as three separate sources. Enforcing lowercase at the point links are created is the simplest way to stop a report from fragmenting into near-duplicate rows. This page covers why casing matters, where to enforce it, and how to clean up an existing mess.

Over time a UTM taxonomy accumulates abandoned sources, one-off mediums, and inconsistent campaign names. Cleaning it up improves reporting, but you cannot edit links already in the wild — they will keep arriving with old values. Deprecation is therefore about steering new links to the clean taxonomy while mapping legacy values forward in reporting. This page covers a safe cleanup process.

Mixpanel's JavaScript SDK automatically captures the five standard UTM parameters from the page URL and stores them as properties on tracked events, and can persist the first values as user profile properties. This makes UTM the basis for acquisition-channel breakdowns in Mixpanel without extra instrumentation, provided you understand when the values are read and how they persist.

Segment's analytics.js library automatically parses UTM parameters from the page URL into the standardised context.campaign object on every event, and forwards that context to connected destinations. Understanding this mapping lets you tag links once and have campaign data flow consistently into every tool wired to Segment.

Google Tag Manager does not capture UTM parameters by itself, but it can read them from the page URL using built-in URL variables or custom JavaScript, expose them in the dataLayer, and pass them to any tag. This makes GTM a flexible place to route campaign data to multiple tools without editing site code for each one.

Adobe Analytics does not use the UTM convention natively the way GA does. Campaign attribution typically runs through the campaign tracking-code dimension, and UTM parameters from inbound links are captured into that dimension or into eVars using Processing Rules or the Web SDK. Knowing this mapping lets you reuse UTM-tagged links inside Adobe.

Amplitude's browser SDK can automatically capture the five standard UTM parameters and store them as event properties and as initial and latest user properties. This supports acquisition-channel breakdowns and first-touch attribution in Amplitude charts without custom tagging beyond the link itself.

PostHog's web SDK automatically captures the five standard UTM parameters and stores them on events, and records initial UTM values as person properties so you can attribute later events to the acquisition channel. This supports channel breakdowns in PostHog insights without custom tagging beyond the link.

Consent Mode adjusts how Google tags behave based on a visitor's consent state. When analytics_storage is denied, GA4 receives cookieless pings rather than full cookie-based measurement, which changes how a UTM-tagged arrival is counted and may invoke behavioural modeling. Understanding this prevents misreading campaign numbers when consent is denied.

Federated microblogging is decentralised: links are posted across thousands of independent instances, so referrer hostnames vary and link previews are fetched by instance servers. UTM parameters on the link itself are the reliable way to attribute this traffic, since they travel with the URL regardless of which instance a click came from.

Twitch traffic reaches sites from stream panels, chat messages, the About section, and verbal call-outs that send viewers to a typed or shortened URL. Referrer data is often missing or shows a shortener, so UTM parameters on the destination link are the dependable way to attribute Twitch campaigns.

Bluesky, built on the AT Protocol, can be accessed through the main app and third-party clients, so referrer hostnames vary and link cards are fetched server-side. UTM parameters on the shared link are the reliable way to attribute Bluesky traffic across the app and alternative clients.

Threads is a mobile-first app where most clicks open in an in-app browser, so referrer data is often missing or shows a generic value. UTM parameters on the shared link are the dependable way to attribute Threads traffic, since they travel with the URL through the in-app webview.

Medium articles can drive traffic through in-text links, author bios, and publication pages, and Medium routes outbound links through its own redirector. UTM parameters on the destination URL are the reliable way to attribute Medium traffic, provided the UTM survives the redirect to your landing page.

Substack drives traffic from emailed newsletters, the web reader, and Notes. Email clicks pass through tracking and the reader app, so referrers are unreliable. UTM parameters on the destination link are the dependable way to attribute Substack traffic across email and web.

GitHub drives off-platform traffic from Sponsors profiles, repository READMEs, profile READMEs, and FUNDING links. Many of these are server-rendered and may show github.com as the referrer or none at all, so UTM parameters on the destination link are the reliable way to attribute GitHub-sourced traffic.

Nextdoor offers advertising to neighbourhood audiences. Because Nextdoor is not part of GA's default channel grouping, you should tag ad destination URLs with explicit UTM parameters so clicks are attributed to a paid Nextdoor channel rather than falling into referral or unassigned.

A UTM taxonomy spreadsheet is the operational backbone of consistent campaign tracking: it lists the approved values for each parameter, defines naming rules, and logs every link the team builds. It turns governance from a wiki page into something teams actually consult, reducing casing drift and duplicate channels.

Shortlink services redirect a short URL to a longer destination. They can carry UTM parameters to the final page, or strip and re-add them, depending on configuration. Knowing how your shortener handles the query string is essential so a memorable short URL does not silently lose its campaign attribution.

QR codes and NFC tags both bridge a physical touchpoint to a tagged URL, but they differ in how the URL is delivered and scanned. Both can carry UTM parameters so an offline interaction is attributed online; the practical differences are in scanning behaviour, capacity, and which one suits a given placement.

An attribution window is the time span within which a tagged touch can be credited for a conversion. Because UTM captures the touch but the window is set in the analytics tool, the same UTM-tagged click can receive credit in one report and not another. Understanding windows explains why campaign attribution varies across tools.

Yandex Direct is Yandex's advertising platform for search and display across the Russian-language web. To attribute its clicks in third-party analytics, add UTM parameters to your landing-page URLs and let Yandex Direct substitute its dynamic macros (such as the campaign and keyword placeholders) at click time. Yandex documents the available macros for building tracking URLs.

Naver is South Korea's leading search portal, and Naver Search Ad (and GFA display) drives a large share of Korean-market paid traffic. Because Naver's own analytics ecosystem is separate from Google's, you tag landing-page URLs with UTM parameters to attribute Naver ad clicks correctly in tools like GA4 or a privacy-first analytics platform.

Kakao Moment is Kakao's advertising platform, placing ads across KakaoTalk, the Daum portal, and partner inventory in South Korea. As with Naver, Kakao's measurement ecosystem is its own, so UTM parameters on the landing URL are how you attribute Kakao clicks inside GA4 or a privacy-first analytics tool.

Baidu is the dominant search engine in mainland China, and Baidu's advertising platform drives paid search at scale there. To attribute Baidu clicks in third-party analytics you add UTM parameters to the landing URL and use Baidu's dynamic URL parameters to fill in campaign and keyword values at click time.

VK (VKontakte) is a major Russian-language social network, and VK Ads serves promoted posts and performance campaigns across it. VK documents dynamic URL parameters you can combine with UTM tags so the campaign and ad that produced a click are carried into third-party analytics.

LINE is the leading messaging app in Japan, Taiwan, and Thailand, and LINE Ads places promotions across LINE's timeline, chat list, and partner inventory. Because LINE's measurement is its own ecosystem, you append UTM parameters to landing URLs so LINE ad clicks are attributed in GA4 or a privacy-first analytics tool.

Western analytics defaults recognize Google, Bing, and Meta, but treat regional giants such as Yandex, Naver, Kakao, Baidu, VK, and LINE as unknown referrals or direct. This page is a cross-cutting guide to applying consistent UTM tagging across regional ad platforms so each appears as its own channel, with macros where the platform supports them.

Fathom Analytics and Simple Analytics are cookieless, privacy-first analytics tools. Both read standard UTM parameters from the landing-page URL to attribute campaigns, so you get source/medium/campaign reporting without tracking individuals. This page covers what each reads and how UTM behaves in a no-cookie model.

Snowplow is an open-source behavioral data platform that collects rich, first-party event data into a warehouse. Its tracker and enrichment process map standard UTM parameters into dedicated campaign fields (mkt_source, mkt_medium, mkt_campaign, mkt_term, mkt_content) on the atomic event, giving you warehouse-native campaign attribution.

RudderStack is an open-source, warehouse-first customer data platform. Its JavaScript SDK automatically parses UTM parameters from the page URL and populates the context.campaign object (source, medium, name, term, content) on events, so campaign attribution flows to every downstream destination and your warehouse.

Heap is an autocapture product-analytics tool. It automatically records UTM parameters from the landing URL as marketing/acquisition properties on the session and user, so you can segment retroactively by source, medium, and campaign without instrumenting events by hand.

Piwik PRO is a privacy-oriented analytics suite (the commercial relative of Matomo) with built-in consent management. Its Analytics module reads standard UTM parameters to attribute campaigns and also supports configuring custom campaign parameter names, so you can report acquisition channels in a consent-aware, EU-hostable stack.

Most email service providers wrap links in a click-tracking redirect so they can count opens and clicks. That redirect must preserve the UTM parameters on the final destination URL, or your web analytics will lose the campaign attribution even though the ESP recorded the click. This page covers how the two layers coexist.

Cookie consent banners often block analytics scripts from running until a visitor consents. Because UTM attribution happens when the analytics script reads the landing URL, a consent gate can cause the campaign to be missed if the visitor navigates away or the UTM is gone before consent is granted. This page explains the interaction and mitigations.

Paid social ads and organic social posts can drive clicks from the same platform, but they are different channels with different costs and goals. The reliable way to separate them is a deliberate utm_medium convention, since the platform domain alone cannot distinguish a boosted ad from an organic share. This page sets out a clean split.

A self-hosted link shortener (for example an open-source tool like YOURLS or Shlink on your own domain) lets you create short campaign links that redirect to long UTM-tagged destinations. Running it yourself keeps the click logs first-party, the redirect domain on-brand, and the UTM mapping fully under your control.

Redirect services and link-management platforms sit between a click and your landing page. Depending on configuration they may preserve the UTM parameters, append their own, or drop the query string entirely. Knowing which behavior applies is essential, because a redirect that loses UTM silently breaks campaign attribution.

Yandex Metrica is Yandex's free web analytics platform, widely used for Russian-language and regional sites. It reads standard UTM parameters from the landing URL to attribute traffic in its source reports, and ties natively into Yandex Direct, so UTM tagging is how non-Yandex sources stay attributed alongside Direct.