Campaign link inputs
Enter the destination URL and campaign parameters. Existing query parameters and hash fragments are preserved.
Custom parameters
Add non-UTM query parameters such as audience, placement, or internal routing values.
Create clean campaign tracking URLs with UTM parameters for analytics, ads, email, social posts, and marketing links.
Enter the destination URL and campaign parameters. Existing query parameters and hash fragments are preserved.
Add non-UTM query parameters such as audience, placement, or internal routing values.
Final URL, query preview, copy actions, and optional QR preview.
Enter a base URL or load a preset to append UTM parameters while preserving existing query strings and fragments.
Build consistent campaign tracking links for analytics, ads, email, social posts, QR codes, and partner placements.
UTM parameters are query string keys used by analytics tools to group visits by campaign context. The common keys are utm_source, utm_medium, utm_campaign, utm_term, and utm_content.
utm_source names where the click came from, such as google or newsletter. utm_medium names the channel type, such as cpc, email, social, referral, or qr.
utm_campaign should stay stable across all links for one promotion. Use utm_content for button, creative, subject line, or placement variants.
Email links often use utm_source=newsletter and utm_medium=email. Paid search commonly uses utm_source=google, utm_medium=cpc, and a term value.
Parameter names and values are encoded with browser URL APIs so spaces, ampersands, hashes, and punctuation do not break the final link.
Destination URLs can already include parameters like ref=nav or plan=team. This builder preserves those values, replaces old UTM keys, and keeps hash fragments at the end.
Avoid changing campaign names mid-flight, mixing source and medium, using spaces inconsistently, or adding secret tokens to campaign URLs that may be copied into ads and reports.
For flyers and signage, use a short readable campaign name and a medium such as qr. Test the QR image with the final URL before printing.
The builder does not fetch, validate, or log the destination URL. Copying, downloading, opening, and QR generation happen only from explicit user actions.
No. It only validates URL syntax in your browser and never checks whether the destination exists.
Existing UTM keys are removed and replaced with the current field values so the final link has one clear set of campaign parameters.
Yes. Non-UTM parameters already on the destination URL are preserved unless you add a custom parameter with the same key.
Many teams prefer lowercase slug-style values because analytics tools usually treat different casing as different labels. The lowercase and slugify option helps enforce that convention.
Yes. The QR preview uses the existing local QR Code Generator service and is created only when you press Generate QR.