UTM Source (utm_source) — Guide & Examples
utm_source tells analytics where traffic came from: a platform, publisher, or partner. Consistent source values keep reports clean across campaigns.
Build your tagged URL
UTM URL builder form
Need the full toolkit? Use our free UTM builder on the homepage.
What utm_source means in campaign tracking
The utm_source parameter answers a single question: who sent this visit? It identifies the origin platform, publisher, or partner—Google, a newsletter product, Facebook, a podcast show notes link, or an affiliate blog. Analytics tools bucket sessions by source first, so inconsistent naming here ripples through every dashboard you trust for marketing attribution.
Unlike medium, which describes the channel type, source names the specific sender. That distinction matters when you run the same campaign on multiple networks: spring-sale might be the utm_campaign, while source differentiates linkedin from twitter and medium marks both as social.
Why utm_source is essential for reporting
Google Analytics 4 maps utm_source to the session source dimension. Without it, traffic from paid and owned campaigns collapses into referral or direct buckets. Executives asking which partner drove trials need source-level clarity, not guesses from referer headers which are often stripped on mobile apps and email clients.
Source also powers campaign tracking URLs in spreadsheets: media buyers paste tagged links into ad platforms; lifecycle marketers embed them in templates. When everyone uses the same source vocabulary, year-over-year comparisons become possible.
Best practices for naming utm_source
- Use lowercase platform names: google, bing, facebook, linkedin.
- For email, pick either your ESP (mailchimp) or channel label (newsletter)—not both randomly.
- Affiliates: use a stable partner slug (partner_acme) rather than changing URLs per month.
- Avoid spaces; use underscores or hyphens if you need separators.
- Never use utm_source for internal site sections—that belongs in content or campaign.
Real-world utm_source examples
| Scenario | utm_source | Pair with medium |
|---|---|---|
| Google Ads search | cpc | |
| Monthly newsletter | newsletter | |
| Organic Instagram bio link | social | |
| Podcast show notes | podcast_name | referral |
| Partner co-marketing | partner_brand | referral |
Common utm_source mistakes
Teams often invent new sources per email blast (march_email, april_email) instead of keeping source stable and moving the send identifier into utm_campaign. Another mistake is using campaign names as source, which makes cross-channel launches impossible to compare. Finally, copying competitor UTMs without adapting taxonomy pollutes your data with meaningless labels.
How utm_source works with other parameters
Source never stands alone in well-formed tracking links. Pair it with utm_medium (cpc, email, social) and utm_campaign (initiative slug). Add utm_content when testing creatives and utm_term for paid keywords. Test links in GA4 DebugView before scaling spend.
Channel-specific guides: Google Analytics, Facebook Ads, email marketing.
utm_source in multi-touch journeys
First-touch reporting credits the initial utm_source on the landing session. If a user later returns via direct, the original campaign may still influence assisted conversion reports depending on your attribution model. That is why overwriting source on retargeting landing pages without documenting the change misleads funnel analyses—use a new campaign slug or content label instead of redefining source mid-journey unless intentional.
For mobile apps that deep-link to the web, ensure the web fallback URL includes the same UTMs you use in app install campaigns so web analytics do not undercount mobile-driven signups.
Auditing existing utm_source values
Export twelve months of GA4 session source rows. Sort by sessions and flag sources appearing fewer than ten times—often typos. Merge duplicates in future links only; historical sessions remain unchanged. Share the cleaned list with agencies and require approval for new sources not on the list.
Use cases by team
Growth and performance marketing
Performance marketers standardize source per ad platform so blended ROAS models and GA4 explorations align with Facebook Ads Manager and Google Ads campaign views.
Content and SEO
Content teams tag guest posts and syndication partners with distinct sources to prove which placements drive assisted conversions without claiming paid medium.
Partnerships
Each partner receives a unique source value in contracts, simplifying payout verification when combined with campaign slugs agreed in advance.
Frequently Asked Questions
- What is a good utm_source for Google Ads?
- Use google as the source and cpc as the medium unless your tracking plan standardizes a different value. Keep source stable across ad groups so GA4 aggregates spend-aligned sessions.
- Can utm_source be a partner name?
- Yes. Affiliate and co-marketing programs often use the partner brand as source (e.g. partner_acme) with medium referral.
- Should newsletter and email share the same source?
- Pick one convention: either source=newsletter with medium=email, or source=your_esp_name. Document the choice so teams do not invent new sources per send.