UTM Builder
Campaign URLs without the typos โ lowercase enforced, conventions kept.
About this builder
URL plus the five utm parameters, assembled live with the discipline that keeps analytics clean: everything lowercased, spaces hyphenated, the three required parameters checked before the copy button unlocks, and one-tap combos for the common channel pairs.
The conventions that keep reports readable
UTM tags are how a click tells analytics where it came from, and their whole value depends on consistency: Email, email and E-mail are three different rows in every report, forever โ hence the enforced lowercase. The scheme in one line each: source is the specific place (newsletter, google, facebook), medium is the channel type (email, cpc, social, referral โ analytics groups by these, so stick to the standard vocabulary), campaign names the push (spring-sale). Term and content are for paid keywords and A/B variants. The two rules learned by post-mortem: never tag links between pages of your own site (it overwrites the visitor's true origin), and keep a spreadsheet of the names you've used, because consistency across a team is where taxonomies go to die. Shorten or QR the result with the QR generator, and the URL parser dissects anyone else's tagged links.
Frequently asked questions
What do utm_source, medium and campaign mean?
Source: the specific site or property the click comes from (newsletter, google). Medium: the channel type (email, cpc, social). Campaign: which marketing push (spring-sale). Analytics wants all three.
Why must UTM values be lowercase?
Analytics treats Email and email as different values and reports them as separate rows permanently. Lowercase-with-hyphens is the convention that keeps a year of data aggregable.
Should I tag internal links on my own site?
Never โ clicking a tagged internal link restarts the visitor's session with the new source, erasing where they really came from. Tag only inbound links from elsewhere.
Do UTM parameters affect SEO?
They can create duplicate-URL noise if such links get indexed; canonical tags (which this site's pages carry) are the standard defence. For search engines the parameters are otherwise inert.