UTM Builder and Campaign Link Tagger
A campaign link is only useful if the values inside it are consistent.
This builder assembles a UTM-tagged URL from a destination and up to five UTM fields, offers channel templates for common ad platforms, and previews how those values would appear as channel data on a lead record. Use it to produce the link, then read the field guide and checklist below so the tags you ship are ones your analytics and CRM can actually report on.
Build the link
Start with the page you want people to land on, then fill in the UTM fields. Templates for Google Ads, Microsoft Ads, Facebook Ads, Instagram Ads, LinkedIn Ads, YouTube Ads, TikTok Ads, Reddit Ads, X Ads, email marketing and affiliates prefill the medium and source values and leave the other fields as you set them. You can also type every value yourself.
The builder requires only a non-empty destination URL before it will generate. Once generated, the tagged link and the CRM preview refresh as you edit any field. The copy control places the finished link on your clipboard, and the field order in the output follows medium, source, campaign, term, content.
What each field is for
The five UTM fields answer different questions, so decide the convention before you send traffic.
- UTM_Medium describes the route the visitor took, such as a paid click, an email or an affiliate referral.
- UTM_Source names the platform or property that sent them, such as a search engine or a social network.
- UTM_Campaign ties the click to a named initiative so results can be grouped later.
- UTM_Term is available for keyword-level detail, typically on search campaigns.
- UTM_Content distinguishes creative variants or placements inside the same campaign.
Empty UTM values are left out of the generated link rather than appended as blanks. Values are trimmed and internal whitespace runs become hyphens, with letter case preserved. The builder does not percent-encode values, so avoid characters that would break a query string or plan to encode them yourself.
Worked example
Suppose you choose the Google Ads template and keep its prefilled medium and source. If you set the campaign to a brand launch, the term to your brand name and the content to a free-trial ad, the generated link carries those five values in the builder's fixed order. The preview then shows how a lead from that click would be labelled: the source becomes the first drilldown, the campaign the second, the term the third and the content the fourth, with any blank field shown as a placeholder such as no campaign or no content.
That preview is illustrative only. It reflects the UTM values you typed and nothing else — no referrer data, no connected CRM record and no platform-side attribution. Treat it as a check that your naming is consistent, not as proof of what your CRM will store.
From tagged link to CRM record
A tagged link on its own does not put campaign data into your CRM. The path usually looks like this:
- Add hidden fields to your lead forms so a tracking layer has somewhere to write the UTM values and other attribution details.
- That layer records where visitors came from and fills the hidden fields with the attribution information, including the UTM parameters.
- When the visitor submits the form, the form tool captures those values and can pass them to your CRM and other tools.
- Reports inside the CRM can then show how many leads and customers came from each campaign.
If you are evaluating a tracking layer for step 2, check that it writes into the specific form and CRM fields you use, and confirm the integration exists for your stack before relying on it.
Pre-launch checklist
Run through these before you paste the link into an ad, an email or a partner kit.
- Destination includes a scheme. The builder only checks that the URL is non-empty, so confirm it starts with https:// or http:// yourself.
- Separator is correct. If the destination already contains a question mark, the builder appends an ampersand; otherwise it appends a question mark. Check the result if your URL already has query parameters.
- Existing tags are intentional. The builder does not strip UTM parameters already present on the destination, so remove stale ones first or you will ship duplicates.
- Fragments are handled. The builder does not parse a hash fragment, so a destination with an anchor may produce a link where the UTM values land in the wrong place.
- Special characters are safe. Values are not percent-encoded; avoid ampersands, question marks and spaces that would break parsing, or encode them before use.
- Copy actually worked. The copy control can show its success label even if the clipboard write was rejected, so paste once to confirm the link arrived.
- Naming is consistent. Agree on lowercase conventions for medium and source across the team so reports group correctly.
How the preview classifies a lead
The CRM preview applies a simple set of rules to the UTM values you entered, in a fixed order. If all five fields are blank, the lead is shown as Direct. If the medium is social and the source matches a recognized social alias, it is shown as Organic Social. A medium of email maps to Email Marketing. A paid or cost-per-click medium combined with a recognized social source maps to Paid Social. Paid or cost-per-click signals, or an adwords, ppc or cpc match across source, medium and campaign, map to Paid Search. A medium of display maps to Display, an affiliate medium maps to Affiliates, and anything else with at least one UTM value falls into Other Campaigns.
Medium, source and campaign are lowercased and trimmed for classification only; the generated link keeps the case you typed. These rules are a demonstration of how entered UTMs might be grouped. They are not a connected CRM sync, they do not read referrer data, and they are not guaranteed to match any analytics platform's default channel grouping.
Where the tagged values can go
The point of tagging is to carry campaign context into the systems where you work. Common destinations include CRM platforms, form builders, email marketing tools and analytics products. Before committing to a tracking layer, confirm the specific integration you need is listed and supported for your plan.
Frequently asked questions
Does the builder check that my URL is valid?
Only that it is not empty. There is no scheme check, so a destination without https:// or http:// will still generate a link. Confirm the scheme yourself before publishing.
Are my UTM values encoded?
No. Values are trimmed and whitespace runs become hyphens, but they are not percent-encoded. Characters such as ampersands or question marks inside a value can break the query string, so avoid them or encode them before use.
What happens if my destination already has UTM parameters?
They stay in place. The builder does not remove existing UTM parameters, so a destination that already carries tags will end up with duplicates. Strip old tags first.
Does the copy button guarantee the link was copied?
Not on its own. The success label can appear even when the clipboard write is rejected, so paste once to confirm the link arrived before sending it on.
Is the CRM preview a real integration?
No. It is an illustration of how the UTM values you entered would be grouped into channel and drilldown fields. It does not read referrer data, does not connect to a CRM and does not reproduce any analytics platform's default channel grouping.
Which fields are required?
Only the destination URL. Every UTM field is optional, and empty UTM values are omitted from the generated link rather than appended as blanks.
| Field | Type | Required | Description |
|---|---|---|---|