What is Cross Device in Google Analytics?
Ever look at your analytics and wonder if the person who browsed your site on their phone during their lunch break is the same person who made a purchase from their laptop that night? Without the right setup, Google Analytics sees them as two separate users, completely breaking their customer journey in half. This article explains how cross-device tracking in Google Analytics works, how to use it, and why it gives you a much more accurate picture of how people interact with your business.
What is Cross-Device Reporting?
Cross-device reporting is the process of connecting a single user's activity across multiple devices - like a smartphone, tablet, and desktop computer - into one unified user journey. The goal is to move beyond tracking isolated sessions and start tracking people.
Let's use a common scenario. A user:
- Taps on your Instagram ad while scrolling on their phone in the morning.
- Browses your products but doesn't buy anything.
- Later that evening, opens their laptop and searches for your brand directly.
- Lands on your site again and completes their purchase.
In a standard analytics setup, this looks like two different users from two different sources. The first "user" from social media looks like they bounced without converting. The second "user" from a direct search gets all the credit for the sale. You end up overvaluing direct traffic and undervaluing the Instagram ad that started the whole journey. Cross-device tracking fixes this by recognizing that this was all one person and connects the dots.
How Google Analytics Powers Cross-Device Reporting
Tying user activity together across different browsers and devices is a technical challenge. Cookies, the small files websites use to track browsers, don't work across devices. A cookie on your iPhone’s Safari browser has no connection to the one on your Windows Chrome browser.
To solve this, Google Analytics 4 uses a few different methods to identify users, stacking them together to create the most accurate picture possible. It does this through your "Reporting Identity" settings, which primarily rely on two signals: a User-ID you provide and Google's own data.
Method 1: The User-ID Feature
The most accurate way to track users across devices is with a User-ID. This method works for websites and apps where users can log in to an account.
Here’s how it operates:
- When a user creates an account or logs in, you assign them a unique and non-personally identifiable ID (like an internal database ID, e.g., "user-12345").
- You then pass this User-ID along with your standard GA4 tracking data every time that user is logged in.
- GA4 uses this stable ID to link every action - page views, clicks, purchases - from any device to that single user profile.
As long as the user is authenticated, it doesn't matter if they're on their phone, work computer, or tablet. GA4 knows it's the same person. The main consideration is that this requires involvement from a developer to properly implement the User-ID in your site's code. It only tracks activity for users who are logged in, so you won't get a full picture of anonymous or first-time visitors.
Method 2: Google Signals
What about users who don't log in? That's where Google Signals comes in. Google Signals uses data from users who are signed into their Google accounts and have turned on Ads Personalization.
Since billions of people use Gmail, Google Search, Chrome, and Android devices, Google can associate website visits from different devices back to a single person without relying on your website's login system. Here’s the process:
- Someone signs into their Google account on their Chrome browser on their laptop.
- They visit your website.
- Later, using the same Google account on their Android phone, they visit your website again.
- Google can recognize it's the same person and stitch their sessions together in your GA4 reports.
This all happens in an anonymized, aggregated way to protect user privacy. No personal data is ever exposed to you. Activating Google Signals is as easy as flipping a switch in your GA4 Admin settings - no code required. The trade-off is that it only applies to a portion of your audience (those signed into Google with the right settings enabled), and your reports may have data thresholds applied, meaning GA4 might hide some data to prevent the identification of individual users.
The Key Advantages of Using Cross-Device Reports
Enabling cross-device features isn't just a technical exercise, it has a direct impact on your marketing strategy and business decisions. Here are the biggest benefits:
- Get a More Accurate User Count: Your "user" metric becomes much more realistic. Instead of seeing your user count inflated by people visiting from multiple devices, you get a deduplicated total that more closely reflects your true audience size.
- Understand the Full Customer Journey: You can finally see the path users take from discovery to conversion, even when it spans multiple days and devices. This helps you understand which devices are used for initial research versus those used for final purchases.
- Improve Marketing Attribution: Correctly assigning credit to your marketing channels becomes possible. You can see how a mobile-first channel like Facebook Ads influences a later desktop conversion, proving its value beyond just last-click performance.
- Optimize for a Better Cross-Device Experience: If you notice users consistently abandon their carts on mobile but complete purchases on desktops, it might point to a friction point in your mobile checkout process. These insights allow you to improve the user experience where it matters most.
- Make Smarter Retargeting Decisions: With a unified view, you can retarget users more effectively. For example, you can avoid showing ads for a product on Facebook to someone who already bought it on their desktop an hour ago, saving you ad spend and preventing user annoyance.
Finding and Using the Cross-Device Reports in GA4
Unlike its predecessor (Universal Analytics), GA4 doesn’t have a dedicated "Cross-Device" section in the reports panel. Instead, its cross-device capabilities are woven directly into your standard reports once you configure your Reporting Identity.
Step 1: Enable Google Signals
Before you do anything else, you need to turn on data collection. This is a one-time setup:
- Go to your GA4 property and click Admin (the gear icon in the bottom-left corner).
- In the Property column, navigate to Data Settings > Data Collection.
- Find the toggle for Google signals data collection and turn it on. You will be asked to acknowledge the user data policies.
Step 2: Check Your Reporting Identity
This setting tells GA4 how you want it to identify users in your reports. Navigate to Admin > Reporting Identity.
You’ll have a few options:
- Blended (Recommended): This is the default and most comprehensive option. GA4 will first look for a User-ID. If it can't find one, it will use Google Signals. If neither is available, it falls back on the device ID (browser cookie). This gives you the most complete view.
- Observed: Similar to Blended, but it will not use modeled data to fill in gaps. It only includes User-ID, Google Signals, and Device ID when data is directly available. You may see "(not set)" more often but the data can feel more raw.
- Device-based: This is the old-school method. It only relies on the browser cookie ("Device ID"), meaning it cannot track users across devices at all. This option gives you inflated user counts and broken customer journeys.
For most businesses, sticking with the Blended identity is the best choice.
Step 3: Analyze Your Reports
Once your Reporting Identity is set to Blended, your standard reports are already powered by cross-device data. When you look at the Reports > Acquisition > Traffic Acquisition report and compare channels like Organic Social versus Direct, you can be more confident the data reflects unified users' behavior, not just isolated browsers and devices. The Device and Browser reports become particularly powerful. You can see not only how much traffic each device drives, but by using comparisons, you can observe how users from different devices behave. Analyze for patterns: do mobile users first land on your blog posts, while desktop users arrive via branded search? This insight is critical for budget allocation.
Limitations of Cross-Device Tracking
Cross-device tracking has come a long way, however, it is important to understand its limitations:
- Privacy Changes: Browser alternatives like Apple's Intelligent Tracking Prevention and the move away from third-party cookies continue to make device identification harder.
- Google Signals Reach: Google Signals only applies to your traffic who are signed in to their Google accounts and have ads personalization enabled. This means you are looking at a modeled view of a subset of your users.
- User-ID Dependency: The User-ID heavily relies on logged-in users. If your site doesn't have login functionality, your data will be limited.
- Data Thresholding: GA4 can and will apply thresholds to reports to prevent the identification of individual users. If your traffic volume is low, you may run into reports where some dimensions or values are hidden.
Final Thoughts
Cross-device tracking isn't just about cleaner data, it's about understanding the real paths that your users take on their journey to conversion. By unifying this journey across devices, you get a more holistic and accurate picture of which channels actually drive growth.
Analyzing this kind of data across GA4 and other tools can be tedious. We've built Graphed to automate the manual reporting work by letting you connect data sources like Google Analytics and Shopify and simply ask questions in plain English. Instead of stringing together dashboards, you can ask Graphed for a dashboard that shows you what channels contribute to sales and get an instant insight without taking valuable time away.
Related Articles
What SEO Tools Work with Google Analytics?
Discover which SEO tools integrate seamlessly with Google Analytics to provide a comprehensive view of your site's performance. Optimize your SEO strategy now!
Looker Studio vs Metabase: Which BI Tool Actually Fits Your Team?
Looker Studio and Metabase both help you turn raw data into dashboards, but they take completely different approaches. This guide breaks down where each tool fits, what they are good at, and which one matches your actual workflow.
How to Create a Photo Album in Meta Business Suite
How to create a photo album in Meta Business Suite — step-by-step guide to organizing Facebook and Instagram photos into albums for your business page.