What is l.facebook.com in Google Analytics?

If you've spent any time in your Google Analytics traffic reports, you’ve probably seen l.facebook.com and m.facebook.com show up as traffic sources. It's often confusing to see these next to the expected facebook.com traffic source, leading to questions like "Is this spam?", "Is it real traffic?", and "Why is Google messing up my attribution?" This article will clarify exactly what this traffic source is, why it appears, and how you can clean it up for more accurate reporting.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What is l.facebook.com?

In short, l.facebook.com is a "Link Shim." It’s an intermediate domain that Facebook uses to process all outbound links clicked by its users. When someone on Facebook (or Threads, or Messenger) clicks a link to your website, they aren’t sent directly to your site. Instead, they are first rerouted through this Link Shim before landing on your page.

The "l" stands for "linker," and this system serves a few key purposes for Facebook:

• Protecting User Privacy: The Link Shim strips sensitive personal information from the referrer URL (the address of the specific Facebook page the user was on). This prevents your website from knowing unnecessarily specific details, such as which user profile or private group the click came from.
• Enhancing Security: Facebook checks the destination URL against its database of malicious websites known for spam, malware, or phishing attempts. If the link is deemed unsafe, Facebook will display a warning page, preventing the user from navigating to a potentially harmful site.
• Improving Analytics for Facebook: While protecting privacy, it also allows Facebook to gather anonymous click data, helping them understand what content is engaging for their users.

You may also see variations like m.facebook.com or lm.facebook.com. The "m" simply indicates the click came from a mobile device or the mobile version of their website, but the function is the same. All are legitimate traffic from the Meta ecosystem.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

So It's Real Traffic, But Why Is It A Problem for Analytics?

Since l.facebook.com is a redirect, it becomes the immediate source (or "referrer") of the traffic that arrives at your website. When Google Analytics records the session, it looks at the final page that sent the visitor over. Instead of seeing the original source as facebook.com, it often sees l.facebook.com or m.facebook.com.

This creates two frustrating problems for anyone trying to analyze their marketing performance:

1. Incorrect Traffic Categorization: The biggest issue is that Google Analytics classifies this traffic as "Referral" instead of "Organic Social" or "Paid Social." Google's default channel definitions are very specific. While it recognizes facebook.com as a social source, it doesn't always apply that same rule to its subdomains like l.facebook.com. Your social media performance reports are now understated, while your referral traffic is artificially inflated with social visitors.
2. Fragmented Traffic Sources: Instead of seeing a single, clean line item in your reports for "facebook," your data gets split across multiple rows: facebook.com, l.facebook.com, m.facebook.com, and more. This forces you to manually add these sources together every time you want to understand your total traffic from the platform.

Essentially, this Link Shim obscures the true source medium, making it much harder to accurately measure the return on your social media efforts.

How to Clean Up Facebook Traffic in Google Analytics 4

Fortunately, you can teach Google Analytics how to correctly categorize this traffic. The best approach is to create a Custom Channel Group. This allows you to define new rules for sorting incoming traffic without permanently altering the original data, giving you a clean, unified view of your Facebook performance.

Quick Note: It is possible to edit your Default Channel Grouping, but this is a destructive change that permanently alters how your incoming data is processed. Creating a Custom Channel Group is the recommended and safer method as it is retroactive and reversible.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Step-by-Step: Creating a Custom Channel Group in GA4

Follow these steps to group all your Facebook traffic under "Organic Social."

Step 1: Navigate to Admin and Find Channel Groups In your GA4 property, click on the Admin gear icon in the bottom-left corner. Under the "Property" column, select Data Settings > Channel Groups.

Step 2: Create a New Channel Group On the top right, click the blue "Create new channel group" button. You'll be taken to a new screen to define your grouping. Start by giving your new group a recognizable name like "Marketing Channel Grouping - Custom."

Step 3: Define a New Channel for Facebook You can either modify an existing channel definition (like "Organic Social") for this group only or create an entirely new one.

Click "Add new channel" to create a fresh channel specifically for this purpose. You will need to provide both a channel name (e.g., “Organic & Paid Social”) and an Expression to match the specified traffic:

• Give your new channel the name “Organic Social.”
• Under the “Channel condition” section, define a new Expression using source and medium information: Set the dropdown menu for conditions to "Match all conditions in one group (OR)".

Let’s define our criteria to ensure we capture all variants of your Facebook traffic based on what makes sense for your business:

• For all social Facebook traffic: Set this simple condition as 'source / medium' 'contains' 'facebook'. This covers domains such as <code>l.facebook.com</code>, <code>m.facebook.com</code>, or any UTM-tagged social media traffic.
• Only organic traffic from Facebook: if your reporting structure demands this distinction, consider relying on a different condition. For example, use source as matching regex (l|m|web|lm)\.facebook\.com as a more robust choice.

After defining the conditions, remember to save your changes and use them within your reports.

Step 4: Using Your Custom Channel Group In Reports Now that you have your new custom channel group, it will begin appearing in your GA4 reports. In the Traffic Acquisition Report, you'll see your newly created custom channel group listed under 'Primary' dimensions. It provides an accurate snapshot of your traffic coming from all different Facebook sources, consolidated and categorized as you defined.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Alternative Method: Unifying Traffic Sources with CASE Statements

Another excellent way to clean up your reporting is to use CASE statements within your dashboards. This approach is versatile and efficient. In Looker Studio, or any other tool like Tableau or Power BI, you can create a custom dimension using "CASE" logic to reclassify your sources.

If you are using GA4 data connected to Looker Studio, this technique can significantly enhance data clarity:

CASE
  WHEN Source IN ('facebook.com', 'l.facebook.com', 'm.facebook.com') THEN 'Facebook'
  ELSE Source
END

This ensures your reports combine the fragmented traffic sources like "l.facebook.com", "m.facebook.com" into a single labeled category of "Facebook".

Proactive Solution: Always Use UTM Parameters for Your Campaigns

For a more comprehensive and preventative measure, use UTM parameters for your campaign links. UTM parameters allow you to specify details such as "Source", "Medium", and "Campaign" for your links, and this is respected in GA4.

For example, construct your links as follows:

https://yourwebsite.com/product-page?utm_source=facebook&utm_medium=social&utm_campaign=winter_sale

By tagging your links with UTM parameters, you ensure that Google Analytics correctly attributes the traffic to the appropriate source, medium, and campaign, helping you maintain cleaner, more accurate reports.

Final Thoughts

Cleaning up your Facebook traffic sources in Google Analytics provides a clearer view of your performance and helps you measure the true impact of your social media efforts. By using Custom Channel Groups, reclassifying with CASE statements, and proactively tagging with UTM parameters, you ensure your data is accurate and valuable.

With the right setup, you can confidently report on your social media ROI and make informed marketing decisions based on reliable data.

Try Graphed for a streamlined approach to managing your campaigns and understanding your analytics.