A buyer sees your Instagram ad on their phone during lunch, searches for your brand on their desktop that evening, and completes the purchase. Without cross-device tracking, that desktop purchase appears as a standalone session with no connection to the mobile Instagram touchpoint. Cross-device tracking attempts to link those two sessions to the same user and give a more accurate picture of the full purchase journey.
Why Cross-Device Tracking Is Difficult
Cookies are device and browser-specific. A cookie set on Safari on an iPhone is completely separate from the Chrome cookie on a Windows desktop. Without a way to link the same person across their devices, each device session looks like a different anonymous user in analytics and ad platform data.
This causes:
- Over-counting of unique users (one person with 3 devices = 3 “users” in analytics)
- Under-attribution of mobile and upper-funnel touchpoints (the desktop purchase gets all the last-click credit)
- Inflated new visitor counts (each device appears as a new visitor)
How GA4 Handles Cross-Device Tracking
User ID
If your Shopify store requires customers to log in, you can pass a hashed user ID to GA4 when the user is authenticated. GA4 uses this User ID to link sessions across devices for that logged-in user. Sessions with the same User ID (on phone and desktop) are merged into a single user journey.
Implementation: in your GA4 configuration tag (via GTM or the GA4 config call), pass the user_id parameter when a user is logged in. The value must be consistent across all devices and cannot be PII (email address directly) — use an internal hashed user ID instead.
Google Signals
If you enable Google Signals in GA4 (Admin → Data Settings → Data Collection → Google Signals), GA4 uses Google account sign-in data to link sessions across devices for users who are signed into their Google account. This works across all platforms and browsers where the user is signed into Google.
Google Signals requires user consent where applicable (EU). Enable it with appropriate consent mode configuration. In GA4 reports, Google Signals data appears in cross-device reports under Explore → User Explorer or in the User Acquisition reports’ cross-device section.
Modelled Behaviour
GA4 uses machine learning to model cross-device behaviour even without User ID or Signals data, by identifying probabilistic matches based on behaviour patterns. This modelled data informs aggregate reports but cannot be used for individual user identification.
How Meta Handles Cross-Device Tracking
Meta’s cross-device tracking relies on its logged-in user graph. When a user is signed into Facebook or Instagram on multiple devices, Meta can link the same person’s interactions across those devices. This is why Meta advertising often has better cross-device attribution than browser-cookie-based tools — the identity layer is the Facebook/Instagram account, not a device cookie.
Meta Pixel and CAPI events are matched to Facebook user accounts via the user data parameters (email, phone, fbp, fbc). Hashed email matches work across devices because the same email address is associated with the same Meta account regardless of device.
How Google Ads Handles Cross-Device
Google Ads uses Google account sign-in (the same mechanism as Google Signals in GA4) to track users across devices. When a user is signed into their Google account on multiple devices, Google Ads can attribute a conversion on desktop to an earlier ad click on mobile.
In Google Ads, cross-device conversions are visible in the Conversion column. Google Ads reports show whether a conversion was “same device” or “cross-device” in the conversion type breakdown.
Practical Steps to Improve Cross-Device Tracking
- Implement User ID in GA4 if your store has customer accounts. This is the most reliable cross-device link for your logged-in buyers.
- Enable Google Signals in GA4 with proper consent mode to capture Google account-linked cross-device sessions.
- Send hashed email to Meta CAPI on purchase events. This improves Meta’s ability to match your checkout events to the correct Meta account regardless of device.
- Use consistent UTM tagging so that even when cross-device stitching fails, you can see which campaigns drove traffic across the full session mix.
Accept the Limits
No tool achieves 100% cross-device tracking. Privacy regulations, browser restrictions, and users who are not logged into accounts create unavoidable gaps. The goal is to improve cross-device visibility enough to make better budget decisions, not to achieve perfect individual-level tracking.
Book your free Shopify tracking audit here and we will review your GA4 User ID configuration, Google Signals setup, and Meta CAPI data quality for cross-device attribution.