Toolkit Shelf
Find

Utility Tools

UTM Link Builder

Use this UTM link builder to create trackable campaign URLs for newsletters, ads, social posts, QR codes, partner links, and launch handoffs.

Catalog QA baseline June 6, 2026Free toolSource note included

Live generator

Generated URL

https://toolkitshelf.com/tools/qr-code-generator?utm_source=newsletter&utm_medium=email&utm_campaign=spring-launch&utm_content=hero-button

OpenQR
Campaign linkReady

Source, medium, and campaign are present.

Query string4 UTM parameters

New UTM values are encoded into the destination URL.

Link length138 characters

Shorter campaign links are easier to test, share, and scan.

Review notes
  • Core campaign fields are present and naming normalization is on.
Privacy note

This builder runs in the browser. The UTM values become part of the final URL, so analytics tools, link previews, redirects, and anyone receiving the link may be able to read them.

Quick answer

UTM Link Builder: what it generates

UTM Link Builder generates campaign tracking URL from destination URL, campaign source, campaign medium, campaign name, campaign ID, source platform, and 4 additional inputs. The visible generation method is UTM URL = destination URL + encoded utm_source + utm_medium + utm_campaign + optional UTM fields.

Draft outputCampaign tracking URL
InputsDestination URL, Campaign source, Campaign medium, Campaign name, Campaign ID, Source platform, Term, Content, Creative format, Marketing tactic
Generation methodUTM link method

Generation method

UTM link method

UTM URL = destination URL + encoded utm_source + utm_medium + utm_campaign + optional UTM fields

The output uses URL query parameters. Analytics reporting quality depends on consistent naming, valid destination URLs, and the analytics setup on the destination site.

How to use

Steps

  1. Enter the destination URL where the campaign link should send visitors.
  2. Add source, medium, and campaign name so analytics reports can group the traffic.
  3. Add optional ID, content, term, platform, creative format, or tactic fields when they distinguish variants.
  4. Copy the generated URL, open it for a quick destination check, or send it to the QR code generator.

Example

Sample output

Emailutm_source=newsletter, utm_medium=email
Paid socialutm_source=instagram, utm_medium=paid_social
QR campaignutm_content=poster-a before creating the QR code

Generator use

Best for

  • Use this UTM link builder to create trackable campaign URLs for newsletters, ads, social posts, QR codes, partner links, and launch handoffs.
  • Reviewing the visible generation method and assumptions before relying on the campaign tracking URL.
  • Comparing the output with the sample output and benchmark table before using it elsewhere.
  • Browser-side link, file, format, and web utility tasks that need an output now.

Before relying on it

Check first

  • Using the campaign tracking URL before confirming the visible inputs match the same task and context: destination URL, campaign source, campaign medium, and 7 additional inputs.
  • Ignoring that the output uses URL query parameters. Analytics reporting quality depends on consistent naming, valid destination URLs, and the analytics setup on the destination site.
  • Skipping the source notes when the formula, benchmark, or warning depends on outside context.
  • Publishing a generated file or code without testing it in the real destination.

Details

What to know before using the output

Core fieldsSource, medium, campaign

These three fields keep the campaign link recognizable in most reporting workflows.

Existing queryPreserve or clear

The builder can keep existing non-UTM query parameters while replacing stale UTM parameters.

QR handoffOne click to QR

The generated URL can be sent to the QR code generator for flyers, signs, menus, or print tests.

Source notes

References used for this generator

Google Analytics HelpDocuments UTM parameters, URL builder guidance, and the recommendation to use source, medium, and campaign fields.MDN Web DocsDocuments URLSearchParams behavior for encoding and serializing query parameters in the browser.

Benchmarks

How to read the output

Core trio: source, medium, campaign.

Use these fields together for cleaner traffic attribution and fewer not-set report values.

Variant fields: content, term, ID.

Use optional fields when you need to separate creative, keyword, audience, or campaign-upload variants.

QR and print: Keep short.

Long URLs can still work, but shorter campaign links are easier to test, share, and encode as QR codes.

Method and limitations

Methodology and assumptions

Generation method

UTM URL = destination URL + encoded utm_source + utm_medium + utm_campaign + optional UTM fields

Inputs used

Destination URL, Campaign source, Campaign medium, Campaign name, Campaign ID, Source platform, Term, Content, Creative format, Marketing tactic

Limitations

Utility outputs depend on the encoded payload, file format, target app, scanner, printer, browser, and real-world testing before sharing.

Catalog QA baseline

June 6, 2026. This date marks the catalog-wide automated and editorial QA baseline, not a tool-specific expert review.

Cite this page

Toolkit Shelf. UTM Link Builder. Page version June 6, 2026. https://toolkitshelf.com/tools/utm-link-builder

FAQ

Common questions

Which UTM fields should I always include?

Use source, medium, and campaign for most campaign links. Add ID, platform, term, content, creative format, or tactic only when those fields help distinguish reporting rows.

Does this builder upload my campaign URL?

No. The link is assembled in the browser. The final URL still contains readable campaign values, so do not put private notes or secrets in UTM fields.

Can I turn the UTM link into a QR code?

Yes. Use the QR button in the result panel to send the generated campaign URL to the QR Code Generator, then test the scan before printing.

Do utility tools upload my payload?

Use the page notes for each tool. Browser-side utilities can generate outputs locally, but the final file or code may still reveal whatever you encode or share.

Why should I test the generated output?

Scanners, printers, file viewers, apps, and platform previews can behave differently, so test the exact downloaded output before using it publicly.