Building a UTM URL is easy; keeping analytics clean is the hard part
facebook, Facebook, and fb can fragment reports into separate values. Before generating links, define a small naming dictionary everyone follows.
The point is not to repeat the tool interface. It is to understand the problem that leads you to the tool and what deserves a second look before the result reaches production.
Where the problem usually starts
These are the areas that most often change the outcome, and each one calls for a different decision.
utm_source
Where the visit came from, such as google, newsletter, or linkedin.
utm_medium
The channel type, such as cpc, email, or paid-social under your convention.
utm_campaign
The campaign name shared by related links.
utm_content
Optional distinction for creatives, buttons, or message variants.
lowercase
A consistent lowercase style reduces accidental fragmentation.
Avoid internal UTMs
UTMs on internal links can distort attribution.
A workflow that catches mistakes earlier
Test a small known case, understand the result, then scale the change.
Define allowed values
Create the source and medium vocabulary before launch.
Name the campaign once
Use a concise name that will still make sense months later.
Generate the links
Reuse the same values consistently across channels.
Audit the reports
Catch new spellings before they multiply.
Test the real case in the tool
Start with a sample you understand, compare the output with what you expected, and only then use it on a larger payload, URL set, or configuration.
How do you know the result is actually better?
A successful result is not simply one that produced output. Ask whether the structure, rule, URL, or report is easier to explain, whether conflicting signals were removed, and whether another developer can understand what changed without guessing.
Questions that come up during real use
Do UTMs improve rankings?
Should I use UTMs on internal links?
Does capitalization matter?
Which fields matter most?
Related tools for the next step
These links belong to the same developer workflow rather than acting as a generic list.