E-commerce
October 29, 2026
Are you wondering how to structure your data to obtain reliable analysis in Google Analytics?
The key lies in a clear view architecture, data enrichment, and rigorous cleaning before recording.
Without a solid foundation, reports can become misleading, decisions erroneous, and optimizations limited.
So, how to structure your data for reliable analysis in Google Analytics? On the agenda:
Why create a view hierarchy in Google Analytics?
What are the three types of views to set up for e‑commerce?
How to add additional context to e‑commerce data?
What best practices for data cleaning to apply before recording?
How Qstomy facilitates the implementation of a reliable data strategy?
Let's go.
In the following, you will discover concrete examples, configuration recipes, and pitfalls to avoid to ensure that every hit sent to GA reflects the reality of your business.
These best practices will allow you to optimize your campaigns, improve ROI, and obtain actionable insights quickly.
By applying these principles, you create a robust data foundation that supports your long-term marketing decisions, while facilitating compliance and scalability of your tracking.
Summary
Why create a view hierarchy in Google Analytics?
Google Analytics relies on a structure account > property > view. This hierarchy allows you to segment data and protect the integrity of the original dataset. By separating production, test, and backup environments, you avoid applying filters that irreversibly alter data. Thus, each analyst can work on a view tailored to their needs without compromising the complete history.
For example, by creating a dedicated view for A/B tests, you can compare page variants without polluting production metrics, while maintaining a historical record for each experiment.
Also ensure you document each applied filter so your colleagues can understand the transformations applied to the data.
It is recommended to keep a shared registry (e.g., Google Sheet or Confluence) where each filter is described, dated, and justified, which simplifies maintenance and future audits.

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
What are the three types of views to set up for e‑commerce?
1️⃣ Vue Production : this is the main view used daily for reports. 2️⃣ Vue Staging : secure space where you test filters, segments, and configurations before pushing them to production. 3️⃣ Vue Raw : unfiltered backup of the dataset, indispensable in case of error or audit. Create each view as soon as tracking starts to save time and avoid late rework.
It is recommended to prefix view names with the project reference (e.g., « Prod‑Shop‑FR », « Staging‑Shop‑FR », « Raw‑Shop‑FR ») to facilitate searching in the GA interface, especially when managing multiple properties.
Furthermore, use the Google Analytics Management API to create these views programmatically as soon as a new store is deployed.
How to add additional context to e‑commerce data?
Mandatory fields (product name, transaction ID) are often insufficient for fine-grained analysis. Enrich each hit with attributes such as the type d’utilisateur, the statut client or the aggregated product category. These additional variables allow you to create cohorts, compare ranges, and identify friction points.
For example, associating each visitor with a non-personal internal ID gives you visibility into the multichannel journey.
Custom dimensions such as type d’abonnement, source de trafic premium ou loyalty level offer even more granularity. Coupled with specific events (add to cart, start of checkout funnel), they open the door to detailed funnel analysis.
These enrichments are easy to send via the GTM dataLayer and can be centralized in Qstomy to ensure consistency.
Use GA's DebugView mode or browser extensions to verify in real-time that each custom dimension is correctly transmitted before deploying to production.
What advantages does using a non-personal User ID bring?
The User ID, if privacy-compliant, links sessions of the same customer across multiple devices. This allows you to measure true retention rates, identify high-conversion paths, and create segments based on customer value. This approach combines perfectly with Qstomy's product recommendation module, which uses purchase history to suggest relevant upsells.
To remain GDPR compliant, the User ID must be generated from an anonymous identifier (e.g., SHA‑256 hash) and must never contain personally identifiable information. Keep the mapping server-side and never transmit it in URLs.
This approach ensures reliable cross-device tracking while meeting legal requirements.
How to distinguish customers from simple visitors in reports?
If the User ID is complex to implement, a simple marker suffices: tag visitors who have completed a transaction or return via a post-purchase campaign as client. This rule gives you access to separate 'customers' vs 'prospects' reports, helping you optimize underperforming pages and manage re-engagement campaigns via Qstomy's abandoned cart system.
Once customers are tagged, you can create dynamic audiences in Google Ads or Facebook to retarget recent buyers with cross-sell offers, thereby increasing average order value.
Use Qstomy reports to visualize the conversion rate of each segment and adjust your campaigns in real time.
Why logically group product content?
The Content Grouping feature allows you to classify product pages by category (e.g., men's jackets, women's, children's). By comparing the performance of each group, you quickly identify underperforming ranges and adjust your assortment or copy. This method pairs well with the guide E-commerce SEO strategy for category pages de Qstomy.
By grouping content, you also simplify tracking SEO signals (bounce rate, time on page) by category, which helps content teams prioritize pages for optimization.
Qstomy offers a dedicated dashboard that cross-references GA performance with keyword positions for each group.
What best practices for data cleaning to apply before recording?
Google Analytics offers filters that modify data on the fly. Use them with caution: first create a Raw view to keep the original, then test filters in the Staging view. The most common filters include lowercasing URLs, removing spammy referrals, and consolidating multiple access paths.
Set up automated alerts via Google Analytics or Data Studio whenever a filter causes a sudden drop in data volume, so you can intervene quickly before reports are contaminated.
Document each cleaning rule in a shared repository to ensure traceability.
To simplify implementation, create GTM tag templates that automatically apply URL parameter transformations and path normalizations, reducing the risk of human error.
What essential filters should be implemented to ensure data quality?
Force lowercase : prevents page fragmentation caused by case sensitivity. Exclude spam referrals : blocks fraudulent visits that inflate traffic. Consolidation d’URL : removes suffixes like index.html to unify identical pages. Exclude unnecessary parameters : define the list of query strings to ignore in view settings. These filters ensure clean and actionable metrics.
Before validating a filter in production, test it on a data sample in the Staging view for at least one week to verify its impact on key metrics like bounce rate and conversions.
This prevents configuration errors that could mask significant variations.
How to manage URL parameters and unnecessary queries?
Analyze your parameter catalog: utm_* are useful, but trk_module ou session_id pollute reports. Add them to the 'Exclude URL Query Parameters' list in view settings. You will reduce the number of unique pages and achieve more consistent bounce rates.
Automate parameter management by creating a script that regularly scans your marketing campaign catalog, identifies new parameters, and automatically adds them to the exclusion list.
This approach keeps your reports clean without constant manual intervention.
What method should be adopted for effective cross-domain tracking?
When your store uses multiple domains (e.g., main site + blog subdomain or payment platform), the session may be fragmented. Enable the cross‑domain tracking by sharing the same client ID via the parameter _ga. First test this configuration in the Staging view to ensure the cookie persists across domains. Comprehensive tracking gives you a holistic view of the customer journey, essential for optimizing conversion funnels.
Use the GA debugging tool (Real-Time > DebugView) to validate that the client ID persists when moving from the main domain to the payment subdomain. Also verify that the cookie does not reset after a refresh.
Once confirmed, you can disable double tracking to avoid double-counting of sessions.
How Qstomy facilitates the implementation of a reliable data strategy?
Qstomy, your Shopify AI assistant, automates the creation of GA views, applies standard filters, and enriches each transaction with the status client ou prospect. Thanks to its integrated passerelle de paiement module, purchase identifiers are transmitted flawlessly, preventing data loss. Additionally, Qstomy synchronizes tracking information and customer service data, providing a single source of truth for your reports.
Qstomy's AI assistant offers contextual recommendations when creating new views, suggesting the most suitable filters based on the store type (fashion, electronics, services).
It also generates a compliance report listing the data security practices implemented.
What checklist to follow before finalizing your GA configuration?
In short
Create the three views : Production, Staging, Raw.
Add a non-personal User ID to each session.
Tag customers from the first transaction.
Configure filters : lowercase, spam, URL consolidation, parameter exclusion.
Enable cross-domain tracking if you have multiple domains.
Check reporting in the Staging view before switching to Production.
FAQ
Q : Can I modify filters after going live? R : Yes, but test first on Staging to avoid losing historical data.
Q : Should the User ID be encrypted? R : It must remain anonymous and comply with Google's privacy rules.
By following this checklist, you ensure a clean, reliable, and actionable database for all your e-commerce decisions.
Schedule a quarterly audit of your GA configuration by reviewing each filter, each custom dimension, and each URL parameter to ensure collection remains aligned with your evolving business objectives.
Integrate the results of this audit into your product backlog to prioritize improvements.
To go further: How to build an e-commerce Facebook Ads strategy? - Qstomy, Which e-commerce platform to choose for a small business? - Qstomy, Which platform to choose to create an e-commerce site? - Qstomy, How to use an AI chatbot to compare two products in your store? - Qstomy, Can you use Wix for an e-commerce site? - Qstomy.
This enriched version offers additional instructions for technical implementation and governance, thereby consolidating the reliability of your tracking.

Enzo
October 29, 2026


