A UTM naming convention your whole team can follow

Consistency matters more than cleverness

A naming convention is a team agreement, not a new tracking technology. Its job is to keep the same marketing idea under the same label. When one person writes LinkedIn, another linkedin, and a third li, your reporting gets harder to compare.

Google treats UTM parameter values as case-sensitive. Choose one case and a consistent separator. Lowercase values with hyphens are a practical convention, not a Google requirement; properly encoded alternatives can work too.

Give each field one responsibility

Keep platform names in source, marketing types in medium, and shared initiatives in campaign. Content is the place for a creative or placement variant. Do not make every field repeat the whole campaign name.

For example, use linkedin / social / autumn-demo / carousel-a for an organic social placement and newsletter / email / autumn-demo / header-cta for an email link promoting the same initiative. Keeping the campaign name identical lets you compare placements together.

source: linkedin
medium: social
campaign: autumn-demo
content: carousel-a

Maintain a small campaign register

A shared document or spreadsheet is enough to begin. Record the campaign name, destination, source, medium, content value, and final URL. Assign someone to settle new naming choices before links go live.

Keep medium values aligned with the reporting categories you want. GA4’s default channel groups follow specific rules; an arbitrary value does not guarantee the channel label you expect. Paid campaigns using auto-tagging deserve a separate check rather than blindly copying organic-link conventions.

• Define approved source and medium values.
• Agree on one campaign name before launch.
• Reserve content for variants you genuinely need to compare.
• Keep personal information out of every URL.
• Test one link per placement before distributing the batch.

Fix the process, not only the spreadsheet

Do not rename a campaign halfway through without documenting the change. New values do not relabel previously collected visits. If a historical report has inconsistent names, explain the grouping in your analysis instead of assuming it has been fixed at collection.

In Traceflow, explore the sources and content below a campaign to spot fragmented labels. That helps you catch naming mistakes for the next launch, but it does not edit the data stored in Google Analytics.