What is Cross Network Traffic in Google Analytics?

Seeing "Cross-network" pop up as a traffic source in your Google Analytics 4 reports can be confusing. It wasn't a standard channel in Universal Analytics, and now it might be accounting for a significant chunk of your traffic and conversions. This article will explain exactly what this channel is, why you're seeing it, and how to properly analyze it.

Graphed

Still Building Reports Manually?

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

Watch the Demo

What is Cross-network Traffic in Google Analytics?

Cross-network is a default channel grouping in Google Analytics 4 that bundles traffic from advertising campaigns running across multiple Google networks. Think of it as Google's way of labeling ad traffic when it can't cleanly attribute a session to a single, specific channel like just Paid Search or just Display.

The most common and definitive source of Cross-network traffic is Performance Max (PMax) campaigns. PMax is a highly automated campaign type in Google Ads that dynamically serves your ads across Google's entire advertising inventory, including:

• YouTube
• Display Network
• Search
• Discover
• Gmail
• Google Maps

Because a single PMax campaign touches all these channels, GA4 can't logically categorize a resulting click as coming from only one of them. For instance, if a user saw your ad on YouTube, later conducted a search, and then clicked a PMax shopping ad, which channel gets the credit? To solve this, GA4 simply labels the traffic "Cross-network."

Is "Cross-network" the Same as "Unassigned"?

No, they are distinct. "Unassigned" traffic is a catch-all category for when GA4 has insufficient or conflicting data to classify the traffic source at all. This often points to issues with UTM tagging, improper URL parameters, or other tracking gaps.

"Cross-network," on the other hand, is much more specific. GA4 knows the traffic is the result of a paid Google advertising effort, it just can’t isolate it to a single channel because the campaign itself is multi-channel by design. Seeing Cross-network is usually an indicator that you are running specific kinds of campaigns in Google Ads, not that your general tracking is broken.

Graphed

Still Building Reports Manually?

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

Watch the Demo

The Main Reasons You're Seeing Cross-network Traffic

If you've spotted this channel making an appearance, it's almost certainly due to one of the following reasons. For most advertisers today, the first one is the culprit.

You're Running Performance Max (PMax) Campaigns

This is, by far, the number one reason you're seeing Cross-network traffic. As explained above, PMax campaigns are inherently "cross-network." They are designed to find converting customers wherever they are in the Google ecosystem. When you link your Google Ads and Google Analytics 4 accounts and have auto-tagging enabled (which you should), GA4 automatically recognizes the nature of this traffic and buckets it accordingly.

If you recently launched your first PMax campaign or migrated your Smart Shopping campaigns to PMax, you should expect to see Cross-network traffic appear in your reports from that point forward.

Remnants of Smart Shopping Campaigns

Before PMax, Google Ads had a similar, albeit less expansive, automated campaign type called Smart Shopping. Like PMax, these campaigns also served ads across multiple networks (Search, Display, YouTube, Gmail). Smart Shopping campaigns have since been automatically upgraded to Performance Max for all users.

However, if you're looking at historical data in GA4 from a period when you were actively running Smart Shopping campaigns, you may still see that traffic attributed to the Cross-network channel. Essentially, it was the predecessor that exhibited the same multi-channel behavior.

Potential Tagging and Integration Issues

While much less common, incorrect tagging or integration settings can sometimes cause classification conflicts. For your Google Ads campaigns, the best practice is to rely entirely on auto-tagging.

Auto-tagging automatically appends a "Google Click Identifier" or gclid parameter to your destination URLs. This gclid contains a wealth of encrypted information that GA4 knows how to decrypt, giving it precise data on the campaign, ad group, keyword, and more. When your Google Ads and GA4 properties are linked, this process is seamless.

You can run into trouble if you try to manually override this by adding your own UTM tags to the URLs used in your PMax campaigns. For example, adding ?utm_source=google&utm_medium=cpc to a finalized PMax URL might send conflicting signals to GA4 along with the gclid data. In an effort to reconcile the campaign's known cross-network origins with your manual "cpc" tag, it may still default to being categorized as Cross-network. To avoid this, let the GA4 and Google Ads integration handle the labeling for PMax traffic.

Graphed

Still Building Reports Manually?

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

Watch the Demo

How to Investigate Your Cross-network Traffic

Seeing the Cross-network label isn't enough, you need to confirm what's behind it. Luckily, it’s easy to drill down in your GA4 reports to get more clarity.

The best way to do this is by adding a secondary dimension to your traffic acquisition reports. This adds another layer of detail to your primary dimension (in this case, the channel group).

Step-by-Step Guide to Verification:

1. Navigate to your GA4 property.
2. In the left-hand menu, go to Reports > Acquisition > Traffic acquisition. This report shows traffic grouped by the "Session default channel group."
3. You will likely see "Cross-network" listed in the primary dimension table.
4. To find out which campaigns are responsible, click the blue "+" icon to add a secondary dimension.
5. A search box will appear. Type "campaign" and select Session campaign (alternatively, you can select 'Google Ads campaign' for even more specific filtering).

Once you add this secondary dimension, your report will expand. You can now look at the "Cross-network" row and see the corresponding campaign names next to it. You will almost certainly see the names of your PMax campaigns listed there. This quick check gives you confirmation that your PMax traffic is being categorized as expected.

Is Cross-network Traffic a Problem? (And What to Do About It)

Cross-network traffic is not a problem to be "fixed." It is the intended classification for traffic sourced from hybrid campaign types like Performance Max. Panicking and thinking your tracking is broken is a common mistake. Instead, you should simply accept it as GA4's native label and focus on analyzing its performance.

Here’s how to think about and act on this data:

1. Confirm the Source, Then Trust the Data

First and foremost, follow the steps in the section above to add a secondary dimension and confirm your PMax and Smart Shopping campaigns are the source. Once confirmed, you can trust that your integration is working correctly. Don't try to create custom channel groups or filters to force this traffic into "Paid Search" or "Display." Doing so would misrepresent how the campaign actually works and would obscure the true nature of your traffic.

Graphed

Still Building Reports Manually?

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

Watch the Demo

2. Evaluate On-Site Performance Within GA4

The real value of seeing PMax data in GA4 is understanding what those users do after they click. Use the Traffic Acquisition report to analyze key metrics for your Cross-network segment:

• Engaged sessions: Is this traffic more or less engaged than traffic from other channels?
• Event count & Conversions: Is the Cross-network channel driving key actions on your site, like lead form submissions or purchases? How does its conversion rate compare to your other paid channels?
• Total revenue: For e-commerce sites, this is the bottom line. Are your PMax campaigns driving sales effectively?

Viewing this data alongside other channels like Organic Search and Paid Social in GA4 helps you understand the holistic impact of PMax on your website's ecosystem.

3. Use Google Ads for In-Depth Campaign Analysis

While GA4 is excellent for analyzing on-site behavior, the Google Ads platform itself is better for analyzing campaign performance. Within Google Ads, you can get granular data on your PMax campaigns that GA4 can't provide, such as:

• Cost-per-acquisition (CPA)
• Return on ad spend (ROAS)
• Impressions and clicks
• Asset group performance (which headlines, images, and videos are working best)
• Listing group performance for e-commerce stores

Think of it this way: use Google Ads to optimize the campaign itself, and use Google Analytics to understand how the traffic from that campaign contributes to your overall site goals and user journeys.

Final Thoughts

In short, the "Cross-network" channel in Google Analytics 4 is primarily your traffic from Performance Max advertising campaigns. It's not a sign of broken tracking, but rather an intentional label for ad campaigns that run across multiple Google properties. By using secondary dimensions, you can confirm the exact campaigns driving this traffic and evaluate its performance alongside your other marketing efforts.

Pulling reports from Google Ads, Google Analytics, and all your other sales and marketing platforms is difficult and what holds most teams back. Because of this, we built a tool that connects your data sources so you can get the answers you need in seconds. With Graphed , you link platforms like Google Ads and GA4 just once and then ask questions in plain English like, "show me my Performance Max spend YoY compared to revenue from Google Analytics." You get instant, real-time dashboards that eliminate the manual work required to get performance insights fast.