UTM governance policy

UTM governance policy template

Document the rules that stop tracked links drifting once multiple people start building, approving, and publishing them.

A usable policy defines scope, ownership, non-negotiable rules, exception handling, and the enforcement rhythm that keeps campaign data readable after launch.

Last updated 13 Apr 2026Policy layer in the UTM governance stack

Scope and accountability

The policy defines where governed tracking applies, who is responsible for it, and which steps cannot be skipped before a link goes live.

Scope

  • Applies to paid ads, email, affiliates, influencers, partner campaigns, QR codes, and any redirect layer used for campaign tracking.
  • Use UTMs only when you need campaign, placement, or partner reporting. Do not add them to internal navigation.
  • Any redirect or shortener in the path must preserve parameters end to end before publish.
  • If a platform also appends IDs or auto-tagging parameters, document that interaction before launch.

Accountability

  • The requester owns the campaign brief, destination, and intended tracking context.
  • The approver owns naming approval, controlled values, and exception decisions.
  • The publisher uses the exact approved URL, not a revised copy.
  • The analyst or ops owner runs the drift review and maintains the change log.

Non-negotiable policy rules

These are the rules the policy enforces every time a tracked link is created, approved, and published.

Approved values onlySource and medium come from controlled lists rather than free-text guesses.
One naming contractCampaign and content values follow one stable writing pattern across channels.
Mandatory campaign logEvery live tracked URL is recorded with owner, approver, and destination.
Publish-safe QANo tracked URL goes live before human signoff and redirect proof where relevant.
No silent editsAny live URL or parameter change is logged with reason, date, and approver.
One live versionThe published URL must match the approved log entry exactly.

Naming contract

Use one approved writing pattern for campaign values. Keep separators, casing, and field intent stable across channels.

Open naming conventions

Approved dictionary

Keep source and medium on a short controlled list so reporting stays readable and alias drift is easy to spot.

Open taxonomy design

Change control and enforcement

Good policy is less about writing rules once and more about controlling new requests, approved exceptions, and monthly drift checks after launch.

Start here if ownership is unclear: move to scope and accountability.
Start here if the rules keep drifting: move to non-negotiable policy rules.
Start here if changes keep slipping through: stay on change control and enforcement.

Valid change requests

  • A new platform or partner requires a genuinely new approved value.
  • A reporting gap reveals a missing value or rule that the current stack cannot express.
  • A redirect path or launch workflow changes and must be re-tested.
  • A planned campaign structure change is documented before launch.

Reject the request when

  • The new value is only a synonym for something already approved.
  • The change is being requested just to save time during launch.
  • The campaign is already live and someone wants a silent retroactive edit.
  • The requester cannot explain how the new value will be used in reporting.

Monthly enforcement rhythm

  • Export top source, medium, and campaign values.
  • Flag unknowns, case variants, punctuation variants, and unexplained new values.
  • Confirm live links still resolve correctly and preserve parameters where required.
  • Update the change log and policy version whenever a controlled update is approved.

Go deeper in policy implementation