Build a campaign URL with consistent labels
''A UTM link adds campaign labels to a destination URL. Those labels can help a properly configured analytics system distinguish visits from a newsletter, a social post, an advert or a printed QR code. This builder creates the URL locally in your browser. It does not connect an analytics account, create a campaign inside an advertising platform or guarantee that a visit will appear in a report.
Enter an absolute HTTP or HTTPS destination and provide source, medium and campaign. These three labels are required by this builder. Term and content are optional. The tool preserves unrelated query parameters and the URL fragment while setting the UTM values. Review the complete output before sharing it, especially if the original destination already contains query values that control content or access.
Creating a tagged link does not require an analytics account. Reporting on it requires the destination and analytics setup to collect and interpret the campaign parameters correctly. Consent settings, redirects, blocked scripts and application routing can also affect what is recorded. Treat the builder as a reliable way to assemble labels, then test the real destination and reporting workflow separately.
Choose source, medium, campaign, term and content
''Source identifies the origin
Use source for a stable origin label, such as a publication, partner or newsletter name. Decide your spelling before creating a series of links. “newsletter”, “email_newsletter” and “weekly-news” may all be understandable, but inconsistent values make later reporting harder to compare. Choose a naming convention that your team can apply consistently rather than inventing a new label for each link.
Medium identifies the channel type
Use medium to describe the general channel, such as email, a social channel category or a printed placement. The appropriate vocabulary depends on your analytics conventions. This builder does not enforce a platform's channel grouping rules. If your reports expect a particular value, use that exact convention and verify how it is interpreted in the reporting system.
Campaign identifies the initiative
Use campaign for the named initiative that should group related links. A clear launch name or seasonal promotion label is more useful than a vague value such as “test” in a production link. Keep the campaign value stable across sources when the intent is to compare channels for the same initiative. Separate initiatives should have deliberately distinct labels.
Term and content provide optional detail
Term can hold a useful targeting or keyword label when that fits your reporting design. Content can distinguish placements or creative variants, such as a top button versus a footer link. Do not fill an optional field merely because it exists. Each extra dimension should answer a real reporting question and use a documented convention.
Avoid personal or secret information in every field. UTM values are part of the visible URL and can be copied into browser history, logs, screenshots and shared messages. Use campaign labels rather than names, email addresses, account references or access tokens. Encoding makes a value URL-compatible; it does not make it confidential.
Worked examples and a naming plan
| Placement | Source | Medium | Campaign | Content |
|---|---|---|---|---|
| Weekly email button | weekly_news | spring_launch | top_button | |
| Partner article | partner_journal | referral | spring_launch | article_link |
| Printed event card | event_card | open_day | qr_front |
Suppose a newsletter contains two links to the same product page. Keep source, medium and campaign identical, and change content to identify the top button and the text link. That makes the difference explicit without creating two unrelated campaigns. The labels do not measure clicks by themselves; the destination analytics must receive and report the parameters.
Suppose a printed card uses a QR code. Build the tagged destination first, verify it, and then use the static QR generator to encode that complete URL. The QR image itself has no scan analytics here. A visit to a properly tracked destination may carry the campaign labels, but scan counts, successful navigation and recorded visits are different events and need different instrumentation.
Suppose the destination already has a query such as a product variation or a language choice. The builder preserves unrelated query values while adding the UTM fields. Check that the preserved parameter still selects the intended content. A syntactically valid URL can be wrong for the campaign if it points to the wrong product, locale or landing page.
Suppose you are preparing links for a team. Create a short naming sheet that defines allowed spellings and the meaning of each field. Include one complete example and a rule for new campaign names. Consistency is more valuable than elaborate labels that nobody can apply reliably. Keep the sheet with the campaign plan so later links can follow the same pattern.
Create, test and distribute the link
''Start with the final destination, including the path and any required content parameters. Use an absolute address beginning with HTTP or HTTPS. A relative path, an email scheme or a plain phrase is not accepted as the destination for this builder. Confirm the destination independently before tagging it: adding labels cannot repair a broken page or an incorrect access requirement.
Enter the required source, medium and campaign values as raw labels. Do not pre-encode them unless the interface explicitly asks for encoded text. A structured URL builder handles encoding as part of assembly, and pre-encoding can create a second layer. Use the optional term and content fields only for dimensions you intend to review later.
Read the generated URL from beginning to end. Check the scheme and host, the path, preserved query values, the three required UTM fields and any fragment. Long URLs are easy to skim incorrectly. Copy the final result into a plain text note beside its intended placement so the correct link is used when the campaign is assembled.
Test navigation deliberately in the environment where the link will appear. Confirm that redirects retain the parameters and that the landing page is usable. If you have access to the analytics setup, use its appropriate testing or debug process to verify campaign collection. The builder does not perform that test or promise when a report will update.
Before distribution, check the exact final asset. Email editors, document systems and QR workflows can introduce a wrong link or an old draft. Click the published preview or scan the printed proof and verify the destination. Keep a record of the final URL and placement so you can interpret later reports without guessing which version was used.
Reporting limitations and troubleshooting
''If visits do not appear as expected, separate link construction from analytics collection. First confirm that the complete URL contains the intended parameters. Next check that redirects and landing-page routing preserve them. Then inspect the analytics configuration and any consent or blocking conditions. A correctly assembled link cannot force a browser to run tracking or a report to classify a value as you intended.
If one campaign appears under several names, look for inconsistent capitalization, punctuation, spaces or abbreviations in the labels. The builder does not maintain a shared campaign dictionary. A naming convention and a final review can prevent many of these variations. Do not rename historical values casually without understanding how your reporting system groups them.
If the destination already has UTM parameters, the builder sets the selected UTM values for the new link rather than treating stale campaign labels as authoritative. Inspect the output to make sure the current campaign has the intended labels. Preserve unrelated parameters only when they remain appropriate to the destination and safe to share.
Use campaign tagging for the use case your analytics plan supports. Adding fresh campaign labels to internal navigation can affect attribution in ways you did not intend. This tool does not decide that reporting policy. Follow the conventions of your analytics setup and test a representative journey before applying tags broadly across a site.
A campaign URL can be long, especially with descriptive values and existing parameters. A static QR code containing it may become denser. Shorten labels for clarity only when their meaning remains documented, or use a stable redirect under your own control if that is part of your infrastructure. This toolkit does not provide a redirect service, a URL shortener or editable campaign destinations.
Practice: prepare a small campaign link register
Suppose a launch uses a newsletter, a partner article and an event handout. Create a small register before building the links. Give each row a placement name, destination, source, medium, campaign and optional content label. Use the same campaign spelling for the shared initiative. This gives you a concrete plan to review and makes it easier to spot a label that accidentally belongs to an earlier promotion.
Choose labels that a colleague can understand without opening every asset. A short content value such as a placement name is useful when it has a documented meaning. An unexplained random abbreviation may be compact but difficult to interpret months later. Keep labels concise enough for practical URLs while preserving the distinctions that your reporting question actually needs. Do not create a separate campaign merely to distinguish two buttons in one email.
Build one representative link and test its full journey. Check the landing page, redirects, preserved query values and final campaign parameters. If an email platform or publishing system rewrites links, test the version produced by that system as well. The builder's local result and the distributed link can differ. A correct source URL does not prove that every later editing or delivery step preserved it.
For the handout, build the complete tagged destination before creating the static QR image. Keep the URL and PNG associated with the same register row. Print a proof at the intended size, scan it and verify the destination. This avoids a common maintenance problem where a designer updates a visible caption but leaves an older QR payload embedded in the artwork.
Verify reporting using the analytics system's appropriate test process, with permission to inspect the relevant data. Confirm how the labels are collected and grouped rather than promising that a row will appear immediately in a report. Consent settings, blockers and redirects can affect collection. The register should describe the intended labels, while the analytics check establishes what the actual setup records.
After publication, retain the final distributed URLs and placement dates. If a campaign is repeated later, decide whether it is the same initiative or a new one before copying old labels. Do not put individual customer details into the values to make rows unique. A consistent public naming plan and a clear placement record provide useful context without exposing personal information or pretending that a tagged link itself is a measurement service.
Keep campaign templates separate from final generated links. A publishing system may substitute a placeholder with a real destination or label later in its workflow. This builder does not perform that system's personalization or verify its merge syntax. Review the final resolved link in the actual preview, using nonprivate test values where appropriate. A template that looks plausible before substitution can still produce a wrong path or label afterward, so the distributed version deserves its own destination and parameter check.
Local processing and a reliable review
This tool carries out its operation in your browser. It does not send the values you enter to a remote processing service, and it does not need an account to produce a result. The page still runs within your device and browser environment: anyone with access to your screen, an exported file, or a copied clipboard value may be able to read that material. Choose input that you are allowed to handle on the device you are using.
The practical input limit for this tool is 100,000 text characters. A limit is a boundary, not a promise that every device will handle the largest possible entry at the same speed. Other tabs, low available memory, browser extensions and an old browser can affect responsiveness. If the page appears busy, allow the operation to finish before repeating it. When a large text task can be divided safely, try a small representative sample first and then process clearly labelled parts.
Keep your source separately until you have checked the output. A browser result can be useful and still be unsuitable for the final place where you intend to use it. The receiving form may have different limits, a house style may need a manual edit, or a document may require facts that no mechanical conversion can infer. Compare one simple case by hand, then inspect a case near the boundary that matters to your work.
A useful campaign link combines a correct destination with labels that your team can interpret consistently. Build it locally, test its real journey, and verify analytics collection as a separate part of campaign preparation.
Frequently asked questions
Do I need an analytics account to create a UTM link?
No. The builder can assemble the URL without an account. To see useful reports, the destination needs an appropriate analytics setup that receives and interprets the parameters. Creating labels and collecting data are separate steps. Test the actual landing page and reporting workflow before relying on the campaign for measurement.
Which fields are required?
This builder requires source, medium and campaign along with an absolute HTTP or HTTPS destination. Term and content are optional. Use a naming convention before filling the fields so related links can be compared later. An optional field should answer a real reporting question rather than contain arbitrary extra text.
What should I put in source?
Use a stable label for the origin of the traffic, such as a newsletter or partner name. Keep the spelling consistent across the campaign. The best label depends on your reporting plan, not a universal value enforced by this tool. Avoid personal information because the value is visible in the URL.
What is the difference between medium and campaign?
Medium describes a broad channel category, while campaign names the initiative that links belong to. Several sources and media can share one campaign when you want to compare their contribution to the same initiative. Your analytics configuration may have conventions for medium values, so use and test those conventions explicitly.
When should I use content?
Use content when you need to distinguish placements or creative variants within the same broader campaign, such as a top button and a footer link. Keep the other labels stable if that is the comparison you intend. Do not assume a content value measures clicks by itself; the destination still needs proper tracking.
Does the builder preserve existing query parameters?
It preserves unrelated query parameters and the fragment while setting the UTM values. Review the output, because an existing parameter may control content, language or access. A syntactically valid link can still lead to the wrong page state. Keep only parameters that are appropriate for the final shared destination.
Can I use a relative URL or an email link?
The destination must be an absolute HTTP or HTTPS URL. Relative paths and other schemes are outside this builder. Use the actual landing-page address you intend to share. Confirm it independently before tagging it, since campaign parameters cannot repair a wrong path or a destination that requires unexpected access.
Should I encode the labels before entering them?
Normally enter raw labels and let the builder encode them while assembling the URL. Pre-encoding can create a second layer and make the destination receive literal escape text. Inspect a sample with spaces or punctuation if those are part of your convention. Consistent simple labels are easier to review and maintain.
Does a UTM link count clicks automatically?
The URL itself does not contain a click counter. A properly configured destination analytics system can use the labels on recorded visits. Clicks, QR scans, successful page loads and analytics events are different measurements. The builder does not provide a dashboard or guarantee that any particular reporting system will collect every visit.
Can I turn the link into a QR code?
Yes. Build and test the complete tagged URL, then use the static QR generator. Scan the final code from the actual printed or displayed asset. This toolkit does not add scan analytics or an editable destination to a static QR image. Destination tracking must be configured separately if you need visit reports.
Why are reports splitting one campaign into several rows?
Check for inconsistent case, spaces, punctuation or abbreviations in the values. The builder does not enforce a shared campaign dictionary. Use a documented convention and compare the exact generated URLs. Reporting tools may also apply their own grouping rules, so review their configuration rather than assuming the URL labels alone determine every report.
Why did my parameters disappear after opening the link?
A redirect, application router or landing-page script may remove or replace query parameters. The builder cannot control that destination behavior. Test the full navigation path and confirm where the parameters are available to analytics. A clean final address is not by itself evidence that tracking succeeded or failed.
Can I put customer names or email addresses in a label?
Avoid personal or secret information in UTM values. URLs can appear in history, logs, screenshots and shared messages. Use campaign and placement labels instead of identifying people. Percent encoding is not encryption. The local builder does not make a sensitive value safe to distribute in a public link.
Should I tag internal links on my own site?
Follow your analytics plan. Campaign tags on internal navigation can affect attribution in ways you may not want. This builder does not decide that policy or inspect your reporting configuration. Use a method designed for internal interaction measurement when appropriate and test the full journey before adding campaign tags broadly.
Can I edit a shared UTM destination later?
The shared URL contains a fixed destination and labels. You can create a new URL, but existing printed or copied links do not change automatically. A redirect under your own control can provide a separate management layer, but that infrastructure is not included here. Plan permanent printed assets with that limitation in mind.
What is the final campaign link checklist?
Verify the destination, naming convention, required labels, optional distinctions and preserved query values. Test redirects and the landing page, then verify analytics collection using the appropriate process. Finally check the exact link in the distributed asset. Keep the final URL beside its placement record so later reporting can be interpreted accurately.
Useful next steps
Choose a related tool when its operation matches the next part of your task. Check the result at each stage so a small source mistake does not carry into the final output.