Campaign Tag Guard · field guide
如何统一 UTM 命名，而不重写历史数据How to standardize UTM naming without rewriting history
先冻结一份允许值和别名表，再审计新链接；历史报表与未来命名要分开处理。Freeze allowed values and aliases first, then audit new links. Treat historical reporting and future naming as separate jobs.
- 列出 source 与 medium 的规范值，不要从现有脏数据反推唯一真相。List canonical source and medium values; do not infer a single truth from dirty history.
- 把 fb→facebook、paid-social→paid_social 这类映射写成显式别名。Write aliases such as fb→facebook and paid-social→paid_social explicitly.
- 逐行保留原值、问题、修正值和负责人，形成可回滚收据。Keep original value, finding, correction, and owner per row as a reversible receipt.
- 先在一个 campaign 试用；确认 GA4 新数据归类后再扩散。Pilot one campaign and confirm new GA4 classification before expanding.
证据边界Evidence boundary
工具只检查你提供的 URL 与命名规则，不连接 GA4，也不证明历史数据已经修复。The tool checks only supplied URLs and naming rules. It does not connect to GA4 or prove historical data was repaired.