Launch helper
UTM Builder
Create campaign URLs that stay readable after launch. Keep naming consistent before links spread across newsletters, social posts, docs, partners, and product CTAs.
Production UTM checklist
- Name the campaign before writing the link. Do not invent new variants per channel.
- Use source for the platform/referrer and medium for the traffic type.
- Add content only when comparing placements on the same page or campaign.
- Test the final URL after copy/paste so existing query parameters are preserved.
Direct answer
A browser-first UTM builder that creates consistent campaign URLs and explains naming choices so analytics stays readable after launch.
What this tool solves
Generate campaign links with source, medium, campaign, term, and content parameters before publishing a marketing or product launch link.
Input and output
- Input: Destination URL plus UTM source, medium, campaign, term, and content values
- Output: A clean campaign URL, copyable parameter summary, and naming checklist
- Privacy: Runs entirely in the browser
Best used for
- Product launches, newsletter links, social posts, partner campaigns, and creator collaborations.
- Keeping analytics readable when several channels point to the same landing page.
- Documenting link naming rules before a campaign goes live.
Do not use it blindly when
- You are linking to private pages where tracking parameters could expose sensitive context.
- Your analytics stack already rewrites or enforces campaign naming automatically.
Pre-publish checklist
- Use lowercase, hyphenated campaign names so reports do not split across variants.
- Keep source as the platform or referrer and medium as the traffic type.
- Use content only when comparing versions of the same placement.
Example searches
Useful starting inputs include: newsletter launch, linkedin post, partner link, docs CTA.
Production use
Use the result as a decision aid, then verify it in the real product context. Browser support, API contracts, validation behavior, timezones, accessibility, monitoring, and handoff documentation can still change the right implementation.