What is m.facebook.com in Google Analytics?
Ever had that moment when you're digging into your Google Analytics referrals, feeling like a data detective, only to be stopped by a mysterious source: m.facebook.com. You see traffic from facebook.com, but then there's this "m" version right below it, cluttering up your reports. This article explains exactly what m.facebook.com is, why it appears separately in your analytics, and how you can combine it with your other Facebook traffic for a much cleaner, more accurate view of your social media performance.
What is m.facebook.com?
The short answer is surprisingly simple: the "m" in m.facebook.com stands for "mobile."
This is referral traffic from users who clicked a link to your website while browsing Facebook on their mobile device, either through the Facebook app or the mobile version of the Facebook website in their phone's browser. When someone on their phone taps a link you shared, this is often the source that Google Analytics records.
You’ll typically see a few variations of Facebook traffic in your report, including:
- facebook.com: Traffic from users on a desktop or laptop computer.
- m.facebook.com: Traffic from users on a mobile device.
- l.facebook.com: The "l" stands for "link shim." This is a security feature used by Facebook to protect users from malicious links. When a user clicks a link, Facebook first sends them through a redirect (l.facebook.com) to check the destination for spam or malware before forwarding them to your site.
Seeing all these different sources isn't an error, it's just how Google Analytics processes the raw referral data it receives from users' browsers. However, it can create a real headache for reporting.
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
Why Fragmented Facebook Traffic Is a Problem for Reporting
The main issue with having separate traffic sources for m.facebook.com, l.facebook.com, and facebook.com is that it fractures your data. Instead of seeing a single, consolidated number for "Facebook," you get three or more different line items that you have to mentally (or manually, in a spreadsheet) add together. This makes it annoyingly difficult to answer a simple question: "How much traffic did Facebook send us?"
Think of it like getting three separate bills for your electricity: one for your kitchen, one for your living room, and one for the bedroom. To know your total electricity cost, you’d have to find all three bills and add them up every single month. It’s inefficient and leaves room for error. The same is true for your analytics. Fragmented data leads to:
- Manual Work: You have to export your data to a spreadsheet and create formulas just to combine the numbers, wasting valuable time you could be spending on analysis.
- Difficulty in Comparison: It’s harder to quickly compare Facebook's performance against other channels like Google Search or email when you have to look at multiple rows for a single platform.
- Inaccurate High-Level Reports: If you or a stakeholder glances at a standard GA report, you might underestimate Facebook's total impact because you're only seeing one piece of the puzzle at a time. The true contribution is hidden across several lines.
Fortunately, you can fix this. The method depends on which version of Google Analytics you’re using.
How to Combine Facebook traffic in Google Analytics 4
In GA4, the recommended approach isn't to set up a view-level filter like in the old Universal Analytics. Instead, you can adjust your Default Channel Grouping settings to tell GA4 to group all variations of Facebook into a single social channel.
Here’s how you can do it:
Step 1: Navigate to channel Groups in the Admin panel
Log in to your GA4 property. Click on the Admin gear icon in the bottom-left corner. Then, under the "Property" column, find and click on Data Settings > Channel Groups.
Step 2: Create a New custom Channel Group
While you can edit the Default Channel Grouping, it's safer to duplicate it and create a custom version. Click on "Create channel group". Choose "Create new from scratch".
Give your new group a name, like "FB Consolidated Channels".
Step 3: Define a new Channel for Facebook
Now you'll create a new rule that bundles all Facebook traffic. Click "Add new channel" and give it a name like "Social Facebook".
Set up the following condition:
- Under "Meet ALL of the following", select Source / medium matches regex
^(.*facebook.*)$
This regular expression (regex) tells GA4 to include any traffic source that contains the word "facebook". This is broad enough to catch m.facebook.com, l.facebook.com, facebook.com, and any other variations. You're creating your own bucket dedicated to all Facebook-related traffic.
Step 4: Save & Reorder your Channels
After defining your new channel, click Save channel. It's important to make sure GA4 processes your new custom rule first. Drag your newly created "Social Facebook" channel to be one of the first conditions, before the default "Organic Social" or "Referral" channel rules. GA4 processes rules in order, so placing yours near the top ensures it catches the traffic first. Finally, click Save group.
Now, when you use this custom channel group in your reports (you can select it from the dropdown in the Acquisition reports), you will see 'Social Facebook' as one clean source.
For Historical Data: How to Combine in older Universal Analytics
If you're looking at historical data in an older Universal Analytics (UA) property, the process involves creating a filter. Note: Filters in UA only affect data from the moment they are created forward, they don't apply retroactively.
Here’s the step-by-step process:
- Navigate to the Admin section of your UA property.
- Under the “View” column on the right, click on Filters.
- Click the red + ADD FILTER button.
- Give your filter a descriptive name, like “Combine Facebook Referrals.”
- For Filter Type, select Custom.
- Select the Search and Replace option.
- For the Filter Field dropdown, choose Campaign Source.
- In the “Search String” box, enter this regular expression (regex):
^(l|m|business)\.facebook\.com$ - In the “Replace String” box, enter:
facebook.com
This filter looks for campaign sources that are exactly l.facebook.com, m.facebook.com, or business.facebook.com and replaces them with a uniform facebook.com source in your reports. After you save it, all incoming traffic from those mobile sources will be cleanly grouped together going forward.
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
Best Practice: Use UTM Parameters to Take Control of Your Data
While filters and channel groups are great for cleaning up incoming data, the most powerful way to maintain clean and reliable analytics is by using UTM parameters for every link you share.
UTM parameters are tags you add to the end of a URL to tell Google Analytics exactly where the traffic came from. A properly tagged URL might look like this:
https://www.yourwebsite.com?utm_source=facebook&utm_medium=social&utm_campaign=summer-sale
By specifying utm_source=facebook you override any referral information from the user's browser. This guarantees that traffic from this link will always be attributed to "facebook" as the source in GA4, no matter if the user clicked it on desktop, mobile, or via a link shim. Consistent use of UTMs is the best way to ensure your campaign tracking is organized, consistent, and easy to analyze.
Final Thoughts
In the end, seeing m.facebook.com in your Google Analytics account is completely normal and simply represents traffic from mobile Facebook users. While not an error, it clutters your reports and makes it harder to assess performance. By customizing your channel groupings in GA4, or by using filters in a legacy UA property, you can consolidate all your Facebook traffic into a single source to make your life much easier and your data much cleaner.
Manually fixing referral sources and setting up filters is precisely the kind of tedious reporting task that keeps so many businesses from acting on their data quickly. At Graphed, we handle this complexity for you by connecting directly to your tools like Google Analytics and Facebook Ads. Instead of fiddling with settings, you can ask in plain English, "Show me my total traffic and conversions from all Facebook sources," and get a unified, real-time dashboard instantly. This completely removes the manual setup, so you can focus on insights, not input.
Related Articles
How to Create Facebook Ads API for Claude Code
Create a Meta Marketing API access token that never expires, using a system user, so Claude Code can pull Facebook ad reports and manage campaigns.
ClickHouse vs Postgres: When to Switch to Columnar
Comparing ClickHouse vs PostgreSQL means matching storage architecture to workload. Row storage wins for transactions. Columnar wins for scan-heavy analytics.
Google Ads for Orthodontists: Get More Booked Consults
Most orthodontic Google Ads campaigns waste money on low-intent searches. The problem is structure, not the platform.