UTM Stands for Urchin. The Company Was Named After Sea Urchins. Google Bought It in 2005 and Kept the Name.

The Company Behind the Standard

Scott Crosby and Paul Muret founded a small web hosting company called Quantified Systems in 1996. Muret developed the first version of what would become Urchin in 1997, initially as a tool to parse server log files and calculate how much bandwidth each customer was using. Over time the log parser expanded to show pageviews, sessions, and referral sources. Scott's brother Brett Crosby joined the company in 1997. The company eventually renamed itself Urchin Software Corporation, taking the sea urchin as its mascot.

The business model shifted from web hosting to selling the analytics software itself, targeting mid-size businesses that needed to understand their web traffic without building custom log analysis pipelines. By the early 2000s Urchin had built enough market presence that Google took notice. In April 2005, Google acquired the company. Brett Crosby has recounted that he was in his tuxedo on his wedding day when he signed the acquisition contract. Google relaunched the product as Google Analytics in 2006, making what had been a paid enterprise tool available for free to any website owner.

The decision to keep the UTM parameter names intact when launching Google Analytics was practical. Thousands of existing Urchin customers had already built URLs with utm_source, utm_medium, and utm_campaign appended. Renaming the parameters would have broken all of that tracking data retroactively. The names from 2002 became permanent fixtures of the web analytics ecosystem.

What Each of the Five Parameters Tracks

UTM source identifies where the traffic originated: a specific newsletter, a social network, a paid advertising platform, or a referring website. Source answers the question of origin. Common values include newsletter, facebook, google, twitter, or a partner site domain.

UTM medium identifies the marketing channel type. Medium provides the category that allows aggregation of sources into meaningful groups. All paid search campaigns, regardless of which search engine, can be grouped under cpc. All social media traffic, regardless of platform, can be grouped under social. Email campaigns from multiple senders can all be grouped under email. Standard medium values have emerged over time: email, cpc, organic, social, referral, display, affiliate.

UTM campaign identifies the specific promotional initiative that generated the click. If a company runs a summer sale promoted through email, paid search, and social media simultaneously, all three should share a utm_campaign value such as summer-sale-2026 so that total campaign traffic can be measured as a unit across channels.

UTM term was designed to capture the specific search keyword for paid search campaigns, allowing the keyword responsible for a click to be passed into analytics. Most paid search platforms now pass keyword data directly to analytics integrations, reducing the need to manually populate utm_term in most workflows, but it remains available.

UTM content distinguishes between multiple links in the same campaign pointing to the same destination. A two-button email with a blue button and a red button both linking to the same landing page can use utm_content=blue-button and utm_content=red-button to determine which drove more clicks, supporting multivariate analysis within a single send.

Why Inconsistent UTMs Break Reports

The most common UTM problem is inconsistent naming. Google Analytics treats utm parameters as case-sensitive strings. A campaign tagged as Summer-Sale in one email and summer-sale in another appears as two separate campaigns in reports. A medium value of Email in one campaign and email in another splits what should be one channel into two.

Inconsistency accumulates over time across teams. A marketing team with three people who each build their own UTM links without a shared convention will produce reports that require manual cleanup before analysis is possible. Common issues include mixed capitalization, spaces instead of hyphens, different abbreviations for the same medium, and campaign names that vary between channels when they should be identical.

The solution is a shared naming convention documented before it is needed and enforced at the point of link creation. Standard conventions for medium values have broad adoption: lowercase, no spaces, using cpc rather than paid-search or ppc, using email rather than e-mail or Email. Campaign names should match across all channels for the same initiative.

Source names should correspond to something recognizable in an analytics report. Using fb instead of facebook or ig instead of instagram makes reports harder to read for anyone who did not create the links. Using the full platform name produces reports that are self-explanatory.

How UTMs Affect Direct Traffic

Traffic that arrives without UTM parameters and without a referring domain shows up in analytics as direct. This category is often misunderstood. Direct does not mean the user typed the URL directly; it also includes traffic from links in native apps, PDF documents, certain email clients, and any context where the browser does not pass a referring URL.

Dark social, a term coined by Alexis Madrigal in a 2012 Atlantic article, describes shared links that appear as direct traffic because they traveled through messaging apps, email threads, or copied-and-pasted URLs. A link shared in a WhatsApp group has no referring URL when clicked from the app. Analytics reports it as direct. If the original link had UTM parameters, those parameters survive the share and the click is correctly attributed.

Adding UTM parameters to links before distributing them through any channel, including channels where attribution would otherwise be impossible, is the mechanism for recovering dark social attribution. An email newsletter link tagged with utm_source=newsletter and utm_medium=email will correctly appear as email traffic even if the recipient forwards the email or clicks the link from an email client that strips referring headers.

Building UTM Links That Work

A UTM link appends parameters to the base URL as a query string. If the base URL already contains a query string, UTM parameters are appended with an ampersand rather than a question mark. A UTM link to a page that already has tracking parameters in its URL requires attention to the separator character.

Character encoding matters. Spaces in parameter values must be encoded as plus signs or percent-encoded as %20. Most UTM builders handle encoding automatically, but manual construction can produce malformed URLs if spaces or special characters are not handled.

The URL length limit in practice is around 2,000 characters for most browsers and web servers, but UTM parameters should never approach that limit for normal use. A complete UTM URL with all five parameters rarely exceeds 200 characters beyond the base URL.

The five parameters are all optional except source and medium for the combination to be useful. Leaving source or medium blank produces attribution gaps. Including campaign, term, and content where they apply produces the richest data.

Conclusion

The UTM system that runs through most digital marketing attribution today is the direct product of a small San Diego company that named itself after sea urchins in the 1990s. Paul Muret, Scott Crosby, Brett Crosby, and Jack Ancone built a log parsing tool that became a commercial analytics platform that Google acquired in 2005 and gave to the world for free.

The five parameter names they chose have not changed in over twenty years. For building correctly formatted UTM links, ToolHQ's UTM builder generates the complete URL with consistent formatting, handling encoding and parameter assembly automatically.

Frequently Asked Questions

Try These Free Tools