Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To make an online store measurable, connect an analytics destination such as Google Analytics 4 (GA4), send ecommerce events with the required product and transaction details, and verify the event payloads before relying on reports. A general analytics tag alone does not automatically provide every ecommerce event. What is collected depends on your platform and integration: some platform setups track selected actions automatically, while custom events and other implementations may need additional configuration.
Decide what the store needs to measure
Start with the decisions you want analytics to inform, rather than adding tags first. A useful measurement plan identifies which shopper actions matter and what details are needed to interpret them.
- Which products and product lists shoppers view.
- Where shoppers add items to a cart, remove them, or leave the checkout journey.
- Whether promotions are associated with purchases.
- Which purchases and revenue should be attributed to campaigns or other sources.
Google describes ecommerce measurement as a way to analyze product interaction and shopping behavior. Its setup depends on how the website or app is implemented, so identify your store platform and any existing analytics integration before installing another tag. See Google’s GA4 ecommerce measurement guide.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesChoose an implementation that fits the platform
A hosted platform’s integration may reduce the amount of event wiring you have to maintain, while a custom implementation can offer more control over the data layer, parameters, and checkout flow. Neither route guarantees that every reporting need is covered.
#1 Best Overall
| Choice | What to check |
|---|---|
| Hosted platform integration | Which recommended ecommerce events are already collected, what event details are sent, how much checkout and consent configuration is available, and how you can debug the implementation. |
| Custom implementation or extension | Who maintains the event code or extension, whether it can send the needed item and transaction details, how accessible the data layer and checkout events are, and how consent is handled. |
Shopify documents automatic tracking for certain events after its GA4 setup and provides for manually implementing other recommended or custom events. Its documentation also notes that events cannot be tracked while a store is in private mode. WooCommerce’s Google Analytics Pro documentation describes tracking purchases, product reviews, coupon use, and refunds through the extension. Confirm the current documentation and capabilities for your own platform and version before treating any event as automatic.
Connect GA4 without duplicating existing tags
- Create the analytics destination. Set up a GA4 property and web data stream, or identify the existing property and stream that should receive store data.
- Inspect the current installation. Check the platform’s analytics settings, theme or site code, and any tag-management setup. Avoid adding another Google tag or Tag Manager container until you know what is already present.
- Use the documented platform integration or a deliberate tag setup. For a Google Tag Manager implementation, Google describes using a data layer as the event data source and configuring GA4 event tags with triggers that match ecommerce events. The tag must receive the ecommerce data and fire on the corresponding shopper action.
- Document what is automatic and what is manual. Make a checklist of the events and parameters your platform sends, then identify gaps that require configuration or an extension.
Google’s ecommerce event guidance explains the event and item data expected for measurement. A configuration screen showing that a tag exists is not proof that the right event data is being sent.
Send events that match real shopping actions
Use Google’s recommended ecommerce event names for the actions your site actually supports. The journey can include product and product-list views, cart additions and removals, checkout steps, purchases, refunds, and promotion interactions. Do not send an event simply because a name is available; it should correspond to an actual customer action.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Use the recommended event name and relevant parameters. Consistent names and parameters make ecommerce reporting more useful and easier to validate.
- Include item details where relevant. Send the item array and the product information your store actually has, such as identifiers or names, rather than inventing values.
- Include currency with revenue values. When sending a purchase value or other revenue value, provide the event-level currency as well as the value.
- Represent transactions consistently. Ensure purchase details correspond to the real checkout and transaction, and use transaction identifiers as appropriate to help with duplicate-event handling.
For the supported event names and parameter requirements, use Google’s current ecommerce reference rather than relying on a generic page-view tag to infer shopping activity.
Know which events need platform-specific work
Shopify
Shopify’s documented GA4 setup tracks certain ecommerce events automatically, but it also allows manual implementation of other recommended or custom events. Check the current Shopify instructions to establish exactly what your store sends; do not assume every custom dimension or reporting requirement is included. Events are not tracked while the store is in private mode. See Shopify’s GA4 setup documentation.
WooCommerce
WooCommerce’s Google Analytics Pro extension documents tracking for purchases, product reviews, coupon use, and refunds. Confirm that the extension’s current capabilities and configuration match the events and details your store requires. See WooCommerce Google Analytics Pro documentation.
Other platforms or custom stores
Use the platform’s own implementation guidance to determine whether ecommerce events are collected by default. If not, configure the event source and triggers yourself or use a maintained extension that supports the required event data. Google’s ecommerce guidance describes the event model, but the site or app still needs to send those events.
Test event names and payloads before using reports
- Enable debugging for the implementation. Follow Google’s validation instructions for the tag or Tag Manager setup you use.
- Perform test shopper actions. View a product, add and remove an item, proceed through checkout, and test any other actions in your measurement plan.
- Inspect DebugView. Confirm that the expected event names arrive and inspect their parameters, including item data and currency or revenue details where applicable.
- Test the real purchase flow. Verify that a completed purchase event fires once and contains the correct transaction details. A test of a button or configuration screen alone does not validate the actual checkout.
- Check for duplicate installations. Google advises using only one Google tag or Tag Manager instance per page to avoid duplicate events. Review all theme, platform, and container installations if an event appears more than once.
Use Google’s DebugView validation instructions to inspect events. If a purchase is duplicated, review the tag setup and transaction handling described in Google’s ecommerce documentation.
Best Value
Build consent and data minimization into tracking
Consent handling is part of the tracking design, not a substitute for it. Google Consent Mode communicates a user’s consent state to Google tags so they can adjust their behavior; it does not provide a consent banner or consent-management platform (CMP). Your site needs a compatible consent solution and an implementation that sets and updates consent state appropriately. See Google’s Consent Mode guidance.
Google Analytics policy requires appropriate notice and consent or an opt-out opportunity, and prohibits uploading data that allows Google to personally identify an individual. Examples in Google’s policy include certain names and email addresses. Keep directly identifying information out of analytics event parameters and review data collection before sending it. Read the Google Analytics SDK and User ID Feature Policy.
These are Google platform requirements and implementation considerations, not a complete explanation of privacy law. Applicable obligations vary by jurisdiction; consult qualified counsel about the rules that apply to your store and customers.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
