E-commerce
October 31, 2026
Are you wondering how to track the multi-device purchase journey to better understand your customers?
In a few steps, you can identify the actions of the same user, even if they switch from mobile to desktop and then to a tablet.
Without this visibility, each device is counted as a distinct visitor, which distorts your analysis and marketing decisions.
So, how to track the multi-device purchase journey to better understand your customers? Here is the agenda:
Which devices do your buyers actually use before converting?
Why does standard visitor counting mask the multi-device reality?
How does Google Analytics User ID solve the attribution problem?
How to enable the User ID feature in your GA account?
How to leverage cross-device reports to optimize your campaigns?
Let's go.
In addition to these points, you will discover how to align your product and marketing teams around these insights, what best practices to adopt to ensure GDPR compliance, and how to concretely measure the impact of cross-device tracking on your ROI.
By adopting these best practices, you will transform your fragmented data into a single dashboard, facilitating more precise marketing decisions and a better return on investment.
Summary
Which devices do your buyers actually use before converting?
A single customer never limits themselves to just one screen. They might discover your product on a desktop via an organic search, check the details on their smartphone in-store, and then complete the purchase on a tablet from the couch. This sequence, called the multi-device journey, is now the norm. By capturing each step, you gain a holistic view of the path to conversion and can identify friction points specific to each device. The tool Google Analytics for e-commerce allows you to visualize these transitions as soon as User ID is activated.
By analyzing these sequences, you can identify key moments where the user hesitates and test micro-optimizations like persistent add-to-cart buttons or product reminders to increase conversion chances.
For example, syncing the cart between mobile and tablet reduces abandonment by an average of 12%.

Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion



Empowering 200+ e-commerce merchants
Why standard counting masks the multi-device reality
By default, Google Analytics creates a new session ID with every browser or device change. Thus, the three actions described above are recorded as three unique visitors, artificially inflating the user count and underestimating the true value of a customer. This fragmentation prevents associating the behaviors of the same individual, making it impossible to analyze complete purchase paths. Ignoring this problem leads to marketing decisions based on fragmented data, such as over-allocating budget to a channel that actually only generates part of the journey.
This fragmentation makes it difficult to detect advertising campaigns that act upstream of the funnel. By correcting attribution via User ID, you often observe a 10 to 20% increase in revenue attributed to retargeting channels.
The role of User ID in consolidating sessions
User ID is a value you assign to each authenticated user (after login or registration). Unlike Client ID, which changes with each device or cookie deletion, User ID remains constant, allowing you to link all sessions of the same customer, regardless of the device used. By activating this feature, you get a complete view of the purchase journey, from the first visit to the transaction, within a single user identity. This unified view improves the accuracy of attribution reports and helps you identify the most effective conversion points.
Thanks to this unification, you can also segment your audiences by multi-device behavior, create personalized journeys, and automate email campaigns that pick up exactly the product viewed on the last device.
Difference between Client ID and User ID
The Client ID is automatically generated by the tracking code and couples navigation-device. It disappears as soon as the user changes browsers or devices, or when they delete their cookies. The User ID, on the other hand, is defined by you and remains attached to the user as long as they stay logged in. Thus, the User ID represents a real account, while the Client ID represents an anonymous session. By combining both, you can compare anonymous traffic (useful for non-logged-in visitors) and identified traffic to refine your re-engagement strategies.
In practice, it is recommended to keep both identifiers in your data-layer to be able to cross-reference anonymous analytics with identified profiles, especially when part of your traffic remains unconnected.
Procedure to activate User ID in Google Analytics
Activating User ID is done from the Google Analytics (Universal Analytics) admin interface. Go to Admin > Property > Tracking Info > User ID, then follow the assistant. You must accept the data usage policy, activate the blue button, and click on « Next step ». Do not forget to save your settings. Once the feature is active, you can start sending User ID values from your site. Consult the article Google Analytics for marketing for more details on configuration.
Also remember to update your view filters to exclude internal traffic and verify that IP anonymization settings do not block the transmission of the User ID.
Do not forget to test the login flow on different browsers to validate the persistence of the User ID.
Technical implementation of User ID on the site
After activating User ID, you must inject the value into every hit sent to GA. Add the following line before sending any hit: ga(’set’, ’userId’, USER_ID); where USER_ID corresponds to your client's unique identifier (e.g., Shopify ID). If you use Google Tag Manager, create a variable Fields to Set and set the field userId from a cookie or data layer containing the identifier. Ensure that the data contains no personally identifiable information, in accordance with Google's policy.
On e-commerce sites, it is common to add the User ID in e-commerce transactions (enhanced e-commerce) to link each purchase to a unique user, which enriches revenue per customer reports.
Creating a dedicated view for User ID reports
Once User ID is active, create a special view to visualize associated reports. In the GA interface, click on Create Viewassign it an explicit name like « User ID View », choose the time zone, and validate. This view cannot be converted to a standard view later, so it must be created from the start. All User ID reports (Device Overlap, Device Paths, Acquisition Device) will be accessible only from this view. Remember to apply the same filters as your main views to ensure data consistency.
Once the view is created, activate custom reports and configure threshold alerts to be quickly informed of any collection or performance anomalies.
Exploring Cross-Device reports
In the section Audience > Cross‑Device, three key reports help you break down multi-device behavior:
Device Overlap : indicates the combinations of devices used and the revenue generated by each combination.
Device Paths : shows the order of devices traversed before conversion, with up to 50 possible steps.
Acquisition Device : reveals which device initiated the first session that led to conversion.
These reports are essential for adjusting your marketing budget based on the devices that generate the most value.
These reports also allow you to visualize the share of organic versus paid traffic in each device sequence, offering a valuable insight to reallocate the budget more effectively.
Leveraging the Device Paths report for retargeting
The report Device Paths tells you, for example, that 30% of buyers switch from mobile to tablet before purchasing. By targeting retargeting ads on transition devices, you can shorten the purchase cycle. Use these insights to create specific audiences in Google Ads a 'Mobile → Desktop' audience for retargeting campaigns, or even tablet-specific messages for users finalizing purchases on tablets. This segmentation improves advertising ROI by reaching the right device at the right time.
By combining these insights with synchronized push notification campaigns, you can remind users of products added to their cart on their previous device, thereby increasing the final conversion rate.
Interpreting the Device Overlap report for budget optimization
The report Device Overlap shows the percentage of visitors using multiple devices simultaneously and the associated revenue. If you find that users switching between smartphone and desktop generate 45% of revenue, you must ensure a seamless experience across these devices: cart synchronization, identical recommendation displays, and even continuity in the customer support chat thread. Conversely, if a device contributes little to revenue, you may reconsider your advertising investment on that device.
If you observe low contribution from a device, consider adjusting the responsive design or simplifying the checkout process on that device to reduce friction.
This optimizes the overall customer experience.
How Qstomy simplifies multi-device tracking
Qstomy, Shopify's AI assistant, automatically associates each customer account with a unique identifier, regardless of the device used. Thus, your store sees the customer moving from the mobile site to the app and then to desktop as a single entity. Qstomy enriches this tracking by offering:
Consistent product recommendations across devices thanks to shared history.
A persistent cart that follows the customer from one screen to another, reducing abandonment.
Automated order tracking and customer support that resumes with the same ID, facilitating multichannel support.
Integrated reports in the Qstomy dashboard displaying device paths, without additional GA configuration.
Thanks to Qstomy, you benefit from a unified view of the customer while maintaining the flexibility of your multichannel campaigns.
Furthermore, Qstomy offers automatic triggers that update the customer status in real-time as soon as an action is taken on any channel, ensuring a seamless experience.
Deployment checklist and FAQ
Deployment checklist
Verify that your users log in to your Shopify store.
Enable User ID in Google Analytics (Admin → Property section).
Implement the code
ga(’set’,’userId’, ID_CLIENT)or the corresponding GTM variable.Create a dedicated view for User ID reports.
Test tracking by navigating across multiple devices and validate the Device Paths and Device Overlap reports.
FAQ express
Does User ID work with anonymous visitors? No, it applies only to authenticated users.
Should I disable cookie tracking? No, User ID works in conjunction with the Client ID.
Does Qstomy require additional configuration? No, the AI automatically associates IDs and populates the reports.
By following this checklist, you ensure reliable and actionable data collection.
To go further: What is Google Shopping for e-commerce? Definition, feed, and benefits for a store - Qstomy, E-commerce conversation analysis: understanding real customer questions - Qstomy, How to create a payment gateway for an e-commerce site? - Qstomy, What is Enhanced Ecommerce Google Analytics? UA, GA4, and shopping reading for a store - Qstomy.
Finally, ensure you document each step of the deployment in your internal wiki to facilitate maintenance and knowledge transfer to new team members.

Enzo
October 31, 2026


