Free UTM Builder for Facebook
Facebook traffic appears in GA4 as "Organic Social" for organic posts and "Paid Social" for Facebook Ads. Facebook's referral traffic can come from both desktop (facebook.com) and mobile (m.facebook.com), so normalize your utm_source to just "facebook" for consistency.
Organic Facebook
facebooksocialPaid Facebook
facebookpaid_socialWorked Examples
Build Your Facebook UTM Link
Common utm_content Values for Facebook
feedreelstorygroup-postpage-posteventmarketplaceCommon Pitfalls
Multiple Facebook domains (m.facebook.com vs facebook.com)
Mobile traffic shows as m.facebook.com. Always normalize utm_source to "facebook" regardless of desktop or mobile to avoid splitting your data.
Facebook auto-tagging with manual UTMs
If you're running Facebook Ads with automatic tracking enabled, Facebook may add its own fbclid parameter. This doesn't conflict with UTMs, but be consistent with your utm_source=facebook.
Using uppercase or spaces in parameters
GA4 treats "Facebook", "facebook", and "FACEBOOK" as different sources. Always use lowercase and replace spaces with hyphens.
Facebook UTM FAQs
Should I use "facebook" or "m.facebook" for utm_source?
Always use "facebook" to normalize mobile and desktop traffic. GA4 will group them together under one source, making reporting cleaner.
How do I track Facebook Group posts vs Page posts?
Use utm_content to differentiate: utm_content=group-post for group shares and utm_content=page-post for page content. This helps you understand which community drives more engagement.
Can I use the same UTMs for Facebook and Instagram ads?
You should use different utm_source values: "facebook" for Facebook and "instagram" for Instagram. This separates platform performance even if they're part of the same Meta ad campaign.