先定义未来链接的规则，再处理旧数据。下面这套四步方法适合多人、代理商或多个渠道共同建链的团队。Define rules for future links before touching old data. This four-step method works for teams where several people, agencies, or channels create URLs.
source 使用平台或来源名称，例如 facebook、google、newsletter；medium 使用渠道类型，例如 paid_social、cpc、email。Use platform or origin names for source, such as facebook, google, and newsletter. Use channel types for medium, such as paid_social, cpc, and email.
把 fb=facebook、paid-social=paid_social 写进别名表。不要指望每个人都记住同一套拼写。Put fb=facebook and paid-social=paid_social in an alias map. Do not rely on everyone remembering the same spelling.
每行保留原始值、发现的问题和规范值，让活动负责人可以复核或撤回。Keep the original value, finding, and canonical value per row so a campaign owner can review or reverse the change.
只在新链接上试运行，确认新数据按预期进入 GA4 后，再推广到其他团队。Pilot on new links only. Confirm new data lands in GA4 as expected before rolling the rule out to other teams.
| 字段Field | 输入示例Incoming | 规范值Canonical | 处理方式Action |
|---|---|---|---|
| utm_source | FB / facebook.com | 写入别名表Add to alias map | |
| utm_medium | Paid Social / paid-social | paid_social | 统一大小写与分隔符Normalize case and separator |
| utm_campaign | Summer Launch | summer_launch | 约定小写与下划线Agree on lowercase + underscores |
...?utm_source=FB&utm_medium=Paid%20Social&utm_campaign=Summer%20Launch规范链接After...?utm_source=facebook&utm_medium=paid_social&utm_campaign=summer_launch无需注册。原始 URL 不会离开浏览器。No sign-up. Raw URLs never leave your browser.