The fastest path to standardizing utm parameters for agency teams is to turn the convention into naming rules and shared templates inside each client workspace, so the tool applies the standard instead of people remembering it. This ends the situation where every team member tags links their own way and GA4 splits one channel into several rows. This page shows the exact setup in linkutm.
Free plan available. No credit card required.
Agencies usually do have a UTM convention. It lives in a Notion page or a PDF from 2023 that nobody opens while building a link at 6pm before a launch. The standard exists, it just is not where the work happens.
So each person fills the gap from memory. One writes utm_source=facebook, a colleague capitalizes it, a third abbreviates it to fb. GA4 reads parameters as exact text, so those three spellings become three separate source rows carrying pieces of the same campaign.
Multiply that by five clients and three account managers and the monthly report becomes a cleanup job. Someone merges rows in a spreadsheet by hand, and the numbers the client sees depend on who did the merging that month.
Three people, one channel, three GA4 rows
| Who built the link | utm_source they typed | Row GA4 creates |
|---|---|---|
| Account manager | ||
| Designer | ||
| Freelancer | fb | fb |
Before touching the tool, settle the arguments once. All lowercase. Words joined with the _ character, never spaces or hyphens. A fixed list of allowed sources and mediums. Campaign names in a set pattern, like client_theme_month.
Keep the list of allowed values short. Five mediums cover almost all agency work: cpc, paid_social, email, organic_social, referral. Every extra option is a future inconsistency.
The output of this step is a one-page decision list you can encode in the next step, instead of a style guide people are asked to read.
Add naming rules to every client workspace in linkutm. Rules force lowercase values and lock utm_source and utm_medium to your approved list, so the standard is applied at the moment a link is built.
This is the difference between a documented convention and an enforced one. The Notion page depends on someone reading it. A naming rule corrects the value while the link is being created, whether or not the person ever saw the doc.
Once rules are live, a rushed link built the night before a launch comes out matching the standard, because there is no path around it.
Turn each recurring campaign shape into a shared template inside the client's workspace. The monthly newsletter template carries utm_source=newsletter and utm_medium=email already set. The paid social template carries the right source and medium for that client's channels.
Templates cut typing, and less typing means fewer chances to drift from the standard. A team member picks the template, edits the campaign name, and ships.
New hires benefit most. Their first link on day one matches the convention, because the template made the decisions for them.
Make the UTM builder the only place tagged links get made. Hand-typed parameters in a browser bar or a spreadsheet formula skip the rules, so any link built outside the tool is a hole in the standard.
If someone wants to try out a parameter set before adding it to a client workspace, the free UTM builder tool works without an account.
Every link built here is checked against the rules and saved to the workspace, so the standard and the history grow together.
The links that break standards are rarely the planned ones. They are the quick share a strategist builds mid-meeting. The linkutm Chrome extension covers exactly that moment: right-click any page and build a tagged link on the spot.
The extension uses the same rules and templates as the workspace, so a link built in five seconds during a call follows the same standard as one built during campaign planning.
Your convention now covers one hundred percent of links, not just the ones made on a calm afternoon.
One standard parameter set, enforced by rules
| Parameter | Value |
|---|---|
| utm_source | newsletter |
| utm_medium | |
| utm_campaign | acme_spring_promo_2026 |
| utm_content | header_button |
Rules move the standard from memory to machinery. GA4 splits happen because humans type parameters by hand, and rules take the typing out of the equation.
A short allowed-value list shrinks the decision space. When utm_medium has five options, there is nothing to improvise.
Templates make the standard the fastest path. People follow conventions that save them time and skip ones that add steps.
The Chrome extension closes the ad-hoc gap, which is where most inconsistent links are born.
Publishing the convention as a document and stopping there. Documentation is a reference, not an enforcement layer, and links get built without the doc open.
Allowing too many values. If utm_medium can be paid, paid_social, paidsocial, and social_paid, the standard has four dialects on day one.
Standardizing new links but never noting where the old rows came from. Keep a short log of legacy spellings so reports that span the changeover still read correctly.
Letting one senior person tag links by hand because they know the convention. The exception becomes the example, and the standard erodes from the top.
The setups that hold are the ones where the tool enforces the convention. Encode the standard as naming rules and shared templates in a link manager like linkutm, then route all link building through its UTM builder. Documentation alone does not survive deadline pressure.
Yes. GA4 reads parameter values as exact text, so facebook and Facebook become two different source rows. Forcing lowercase on every value is the single highest-value rule an agency can set.
All lowercase, words joined with the _ character, a locked list of sources and mediums, and a fixed campaign pattern such as client_theme_month. The specifics matter less than having one answer per question and enforcing it with rules.
Links already clicked have already sent their values to GA4, and that history cannot be rewritten. You can update the links themselves for future clicks, but the practical move is to enforce the standard now and annotate the changeover date in reports.
Give them access to the client workspace where the rules and templates live. Their links pass through the same checks as everyone else's, so they cannot introduce a private convention even by accident.
Free plan available. No credit card required.
