What Is UTM Source?
The utm_source parameter identifies where a visitor came from, such as the platform, website, publisher, or marketing source that sent traffic.
Updated 2026-06-28
Quick Definition
The utm_source parameter identifies where a visitor came from, such as the platform, website, publisher, or marketing source that sent traffic.
In plain English
Imagine someone walks into your store and you ask, Where did you hear about us? That answer is essentially what utm_source records. It identifies the platform or organization that referred the visitor to your website. Examples include google, facebook, linkedin, newsletter, bing, and reddit. Rather than simply knowing that someone visited your website, you know who sent them there.
Expanded explanation
The utm_source parameter tells analytics platforms where incoming traffic originated. It usually represents the company, platform, publication, or marketing property responsible for generating the visit. Google Analytics 4 stores this value alongside the session and uses it in reports, attribution, and channel classification. Source values should remain consistent across campaigns. Using newsletter, Newsletter, and email_newsletter for the same source creates fragmented reporting because Google Analytics treats each value as unique. GA4 also evaluates combinations of utm_source and utm_medium when determining a session's Default Channel Group. Consistent, recognizable values make it more likely that traffic will be classified into the expected channel, while inconsistent or non-standard values can lead to unexpected classifications or Unassigned traffic.
Why it matters
Consistent source values help teams understand which platform sends the most visitors, which source generates the most conversions, which publisher drives the highest quality traffic, and which partnerships are performing best. Without consistent source names, comparing campaign performance becomes much harder. Consistent utm_source values also improve campaign attribution, channel reporting, and long-term trend analysis by ensuring traffic from the same source is grouped together over time.
How it works
When someone clicks a tagged URL, the utm_source value is stored with the session. Google Analytics combines that information with other UTM parameters to understand the complete campaign. For example, utm_source=linkedin, utm_medium=social, and utm_campaign=product_launch tells analytics that linkedin was the source, social was the medium, and product_launch was the campaign.
Diagram
UTM source reporting flow
flowchart LR
A[Marketing Link] --> B[utm_source=linkedin]
B --> C[Google Analytics 4]
C --> D[Source Reports]Common misconceptions
- Source and medium do not mean the same thing. Source identifies where the visitor came from, while medium identifies how they arrived.
- Google Analytics does not automatically fix inconsistent source names. Facebook, facebook, and FB are three different values.
Common mistakes
- Mixing uppercase and lowercase values.
- Using abbreviations inconsistently.
- Renaming sources halfway through a campaign.
- Using different names for the same platform.
- Using campaign names as source values, such as utm_source=spring_sale instead of utm_campaign=spring_sale.
- Putting channel types like email, cpc, or paid_social in source instead of medium.
Examples
Practical example
A company promotes the same webinar on linkedin, facebook, and newsletter. Each campaign uses the same landing page. By assigning different utm_source values, the marketing team can identify which platform generated the most registrations while keeping every other campaign parameter consistent.
Best practices
- Use lowercase values consistently.
- Use one agreed-upon name for each source.
- Avoid unnecessary abbreviations.
- Document approved source names.
- Review naming conventions periodically.
Implementation tips
- Think of utm_source as the answer to: Who sent this visitor?
- Use lowercase values consistently.
- Avoid spaces and unnecessary special characters.
- Prefer simple names using hyphens or underscores when needed.
- Document approved source names so everyone on your team follows the same convention.
Lessons learned from real implementations
From Experience
One of the easiest ways to create reporting problems is allowing every team member to invent their own source names. Organizations often track traffic from Facebook using values like facebook, Facebook, fb, facebook.com, and meta. To a person, those all describe the same platform. To Google Analytics, they represent five different traffic sources. A shared naming convention prevents unnecessary reporting cleanup and makes campaign performance much easier to compare over time.
Role-based notes
Marketers
Keep source names simple, recognizable, and consistent across campaigns.
Analysts
Review source reports periodically to identify duplicate or inconsistent values before they become widespread.
Developers
Source values are provided as URL parameters. No website code changes are required to use them.
FAQs
Should I use facebook or meta as the source?
Choose one naming convention and use it consistently. The specific value matters less than consistency across all campaigns.
Can I create my own source names?
Yes. UTM parameters are free-form values. However, custom names should follow your organization's naming standards to avoid fragmented reporting.
Is utm_source case-sensitive?
Yes. Google Analytics treats Facebook, facebook, and FACEBOOK as separate values. Using consistent lowercase naming is considered a best practice.