Standardizing Source Names: Facebook vs FB vs facebook.com
Facebook, FB, and facebook.com look identical to a marketer but are three separate values to an analytics platform, splitting one channel's traffic apart.
Devon Clarke
Head of Marketing Operations
UTM Parameters Basics Blueprint Guide
Why Does Facebook vs FB vs facebook.com Matter?
Facebook, FB, facebook.com, and fb.com might all refer to the same channel in a marketer's mind, but to an analytics platform each is a completely distinct, unrelated value. Inconsistent source naming for the same platform is among the most common and most avoidable ways UTM tracking data gets fragmented, quietly undermining reporting accuracy.
Why Is This Particular Problem So Common?
Unlike a typo, which is usually an accident, inconsistent source naming stems from genuinely reasonable but differing choices made independently by different people, or the same person on different days. One team member types facebook.com out of habit, referencing the domain; another types the shorter facebook. Neither is objectively wrong, the problem emerges only when both are used interchangeably without anyone realizing the platform treats them as entirely separate sources.
Which Other Platforms Commonly Suffer This Problem?
Beyond Facebook, this pattern shows up constantly: Instagram versus insta versus instagram.com; Google versus google.com versus google (organic) as an automatically generated default; LinkedIn versus linkedin versus linked_in; YouTube versus youtube versus yt. Each pair creates the same fragmentation when used inconsistently, however sensible each individual choice seems.
How Does Source Fragmentation Distort Your Reporting?
When a platform's traffic splits across two or three differently named source values, every report filtered or grouped by source understates that platform's true performance, since the total is scattered across multiple disconnected rows. This is especially misleading in comparative reports, a channel comparison chart can produce a genuinely inaccurate ranking if one platform's traffic happens to be more fragmented than another's.
How Do You Establish One Definitive Value Per Platform?
The fix is straightforward: for every platform your business regularly uses, designate exactly one approved utm_source value and document it in your naming convention reference. There's no strong technical argument for preferring facebook over facebook.com, what matters is that the entire team consistently uses the same single choice, every time.
What's a Reasonable Default Standard to Adopt?
If establishing this from scratch, use the platform's short, common name rather than its full domain, facebook rather than facebook.com, instagram rather than instagram.com, linkedin rather than linkedin.com. This is shorter to type and less prone to variation than a domain-based approach, though the specific choice matters less than consistent application.
How Do Automatically Generated Source Values Fit In?
Some traffic arrives with source values automatically generated by the analytics platform itself rather than through your manual UTM tags, organic search traffic is typically labeled google or bing automatically, distinct from any UTM tag you'd apply. Make sure your manual source naming doesn't accidentally collide with these automatically assigned values.
How Do You Audit for Existing Source Name Fragmentation?
Review your analytics platform's complete list of source values, looking for multiple entries that clearly refer to the same platform under slightly different names. You generally can't merge this historical data retroactively, but identifying the pattern lets you fix the process going forward and manually combine fragmented totals when reporting on historical periods.
Frequently Asked Questions
Should I use facebook or facebook.com as my utm_source value?
Either works, but pick one and use it exclusively. A common default is the short platform name, facebook rather than facebook.com, since it's shorter to type and less prone to variation.
Can I merge historical data after fixing inconsistent source names?
Generally no, most analytics platforms don't support retroactively merging historical values. You can manually combine the fragmented totals when reporting on past periods, and fix the process going forward.
Why does organic Google traffic show up separately from my UTM-tagged Google traffic?
Organic search traffic is automatically labeled by the analytics platform itself, typically as google or bing, distinct from any utm_source value you manually apply to a tagged link.
Join 14,000+ marketing growth leaders
Receive our bi-weekly breakdown of campaign analytics setups, attribution rules, naming tactics, and link-stitching blueprints. Direct to your inbox.
Continue reading blueprints
All ArticlesHow to Create a UTM Naming Convention Your Whole Team Follows
A UTM naming convention only protects your data if people actually use it, short documents, real examples, and tooling drive adoption.
How to Audit and Clean Up Messy UTM Data
A nine-step audit process finds fragmented UTM values, prioritizes fixes by traffic impact, and stops the same inconsistency from recurring.