Free Tool · No signup

UTM builder. One convention forever.

Lowercase, hyphenated, validated. Build clean UTM-tagged URLs and lock the convention as a CSV.

Parameters

Tagged URL

https://catchbeforetheybounce.com?utm_source=linkedin&utm_medium=social&utm_campaign=q1-launch&utm_content=hero-ad

utm_sourcelinkedin
utm_mediumsocial
utm_campaignq1-launch
utm_contenthero-ad
Even perfect UTMs only attribute the 5% who fill a form. Catch before they bounce identifies the rest — anonymous visitors with intent. Catch before they bounce scores every website visitor by intent so your team focuses on the ones likely to buy. Try it free →

How it works.

clean = lowercase + hyphens + ascii-only · url = base + (utm_source + utm_medium + utm_campaign) [+ content + term]

The trick isn't the URL — it's the discipline. Document the convention, version it, and reject pull requests that break it. Inconsistent UTMs scatter attribution.

FAQ.

What are UTM parameters?+

URL tags (utm_source, utm_medium, utm_campaign, utm_content, utm_term) that pass attribution data to your analytics. Google Analytics, Mixpanel, Amplitude all read them.

What's a good UTM naming convention?+

Lowercase, hyphens not spaces or underscores, no special characters. Source = platform (google, linkedin). Medium = type (cpc, social, email). Campaign = your name (q1-launch). Stick to one convention forever.

Should I tag organic traffic?+

Never tag organic search. UTMs override referral data — tagging Google organic kills your organic attribution. UTM only paid, social, email and partner traffic.

Why does UTM consistency matter?+

GA treats 'Facebook', 'facebook' and 'fb' as three separate sources. Inconsistent UTMs scatter pipeline across rows that should be one. You can't measure what you can't aggregate.

Should I shorten UTMs?+

No — keep them human-readable. Shorteners (bit.ly) hide the params from preview tooltips and break audit trails. Use clean URLs and trust the parameter string.