UTM 打参指南UTM tagging guide

utm_source 等参数的定义、来源、GEO Tag 的统计口径,以及给运营的打参规范——看完这页,你就知道报表里的「utm_source」维度从哪来、为什么大量流量是 (not set)、以及自己的推广链接该怎么拼。 What the utm_* parameters are, where they come from, how GEO Tag counts them, and the tagging conventions for your team — after this page you'll know where the "utm_source" dimension comes from, why much of your traffic shows (not set), and how to build your own campaign URLs.

UTM 是什么,标准在哪里What UTM is, and where it's defined

UTM(Urchin Tracking Module)是链接上的一组查询参数约定,由发链接的人主动拼在 URL 后面,用来声明「这个访客是从哪个渠道、哪次活动点进来的」。它不是正式标准——没有 RFC、没有 W3C 规范,而是 Google(源自其 2005 年收购的 Urchin 分析软件)确立的事实惯例,全行业分析工具跟随。 UTM (Urchin Tracking Module) is a convention of URL query parameters, appended by whoever publishes a link, declaring "which channel and campaign this visitor came from". It is not a formal standard — no RFC, no W3C spec; it's a de-facto convention established by Google (from Urchin, acquired in 2005) that the whole analytics industry follows.

参数定义(权威出处)Parameter definitions

GA4 官方文档《Collect campaign data with custom URLs》:GA4 official doc "Collect campaign data with custom URLs": support.google.com/analytics/answer/10917952

官方拼参工具Official URL builder

Google Campaign URL Builder,每个参数旁有定义与示例:Google Campaign URL Builder, with per-field definitions and examples: ga-dev-tools.google/campaign-url-builder

取值惯例Value conventions

GA4 默认渠道分组规则(什么 source/medium 组合算 organic/social/email…):GA4 default channel group rules (which source/medium combos count as organic/social/email…): support.google.com/analytics/answer/9756891

底层载体Underlying carrier

URL 查询串本身的语法才是正式标准:Only the URL query-string syntax itself is a formal standard: RFC 3986

参数定义与 GEO Tag 采集范围Parameters & what GEO Tag collects

Google 惯例共五件套(GA4 又扩展了 utm_id 等);GEO Tag 当前采集前三个——对绝大多数打参场景已足够。 Google's convention has five classic parameters (GA4 added utm_id and more); GEO Tag currently collects the first three — sufficient for most tagging scenarios.

参数Parameter	含义Meaning	示例Example	GEO Tag
`utm_source`	流量来源:平台/站点/发布者。必填,报表「utm_source」维度直接用它Traffic source: platform / site / publisher. Required; the report dimension uses it directly	`wechat`, `weibo`, `newsletter`	✅
`utm_medium`	媒介类型:什么形式带来的Medium: what form of link	`social`, `email`, `cpc`	✅
`utm_campaign`	活动名:哪一波推广Campaign: which push	`launch_2026q3`	✅
`utm_term`	付费关键词(搜索广告用)Paid keyword (search ads)	`ai+analytics`	已采集collected
`utm_content`	素材/位置区分(同渠道 A/B)Creative / placement variant (A/B within a channel)	`banner_top`	已采集collected

GEO Tag 的统计口径How GEO Tag counts UTM

会话入口捕获——utm 参数在每段会话的第一个动作(session_start 事件)上记录,整段会话都归属这个来源,与 GA4 的「会话来源」口径一致。 Captured at session entry — utm parameters are recorded on the session's first action (the session_start event); the whole session is attributed to that source, matching GA4's "session source" scope.
utm_source 变化即切新会话——同一访客从另一个打参链接再进来,会开新会话并归到新来源(GA4 惯例:入口来源变化 = 新一段访问)。 A changed utm_source starts a new session — the same visitor arriving via a different tagged link opens a new session attributed to the new source (GA4 convention).
没打参 = (not set),属正常——自然搜索、直接访问、AI 引擎引用的裸链接都不带 utm,这部分本来就该是 (not set),不是采集故障。 No parameters = (not set), and that's normal — organic search, direct visits and bare links cited by AI engines carry no utm; that traffic is supposed to show (not set). It's not a collection bug.
报表位置——控制台「流量获取」页,维度切到「utm_source」;AI 引擎归因(referrer/参数指纹)是并行维度,互不覆盖。 Where to see it — Console → Acquisition, switch the dimension to "utm_source"; AI-engine attribution (referrer / parameter fingerprint) is a parallel dimension, neither overrides the other.

怎么打参:模板与纪律How to tag: template & discipline

utm 只对你自己能控制的链接生效:公众号菜单、邮件签名、给合作方的专属链接。别人转述、AI 引擎引用你管不了,也不用管。 UTM only works on links you control: official-account menus, email signatures, dedicated partner links. Links quoted by others or cited by AI engines are out of your hands — and that's fine.

拼参模板Template

https://your-site.com/landing?utm_source=wechat&utm_medium=social&utm_campaign=launch_2026q3

// 常见渠道示例 / common examples
// 公众号菜单:  ?utm_source=wechat&utm_medium=social&utm_campaign=menu
// 邮件通讯:    ?utm_source=newsletter&utm_medium=email&utm_campaign=2026w31
// 合作方引流:  ?utm_source=partner_acme&utm_medium=referral&utm_campaign=co_marketing

打参纪律(数据干净与否全靠它)Discipline (clean data depends on it)

全小写——utm 值区分大小写,WeChat / wechat 会在报表里裂成两行。 Lowercase everything — values are case-sensitive; WeChat and wechat split into two report rows.
维护一张固定值表——团队共用同一份 source/medium 取值清单,新渠道先登记再打参,不要即兴发挥。 Keep one shared value list — the team uses a single source/medium vocabulary; register new channels before tagging, don't improvise.
不用中文、空格和特殊字符——用 a-z0-9_-,避免编码差异产生重复行。 No spaces or special characters — stick to a-z0-9_- to avoid encoding-induced duplicates.
预期参数会丢——微信等 App 内打开可能剥参,短链展开可能丢参;打了参也可能落到 (not set),属平台行为。 Expect parameter loss — in-app browsers (e.g. WeChat) may strip query params and short links may drop them; tagged links can still end up (not set). That's platform behavior.

拼好链接后,自己先点一次,再到控制台「实时」页确认事件带上了 utm——秒级可见。 After building a link, click it once yourself and check the Console Realtime page to confirm the utm arrived — visible within seconds.