Unlocking the Power of GA4: A Complete Guide for eCommerce Success

No, and this is the single most common error in GA4 guides from this period. Enhanced Ecommerce was a Universal Analytics feature with its own toggle. GA4 has no such switch. Ecommerce reporting populates only when your site sends the reserved ecommerce events with a correctly structured items array, specifically view_item, add_to_cart, begin_checkout and purchase. If those events are not firing with the right names and parameters, no configuration screen will fix it. The work is in your tag setup or platform integration, not in the GA4 admin.

Google renamed conversions to key events across GA4 in March 2024, changing the admin toggles, report columns and API fields. The term conversion is now reserved for the Google Ads side, which was the point of the change: GA4 key events and Ads conversions were never counted the same way, and the shared label caused years of arguments about which number was correct. Nothing about how you mark an event changed. If a guide still refers to marking conversions in GA4, it predates the rename.

Three. Data-driven attribution, which is the property default, paid and organic last click, and Google paid channels last click. First click, linear, time decay and position based were all removed in November 2023, so any guide describing a choice between them is out of date. In practice this means you cannot recreate the first click view many teams built their reporting on. If you need custom attribution logic, the route is exporting to BigQuery and modelling it yourself.

Probably not, and guides rarely mention the thresholds. To generate purchase probability or churn probability, GA4 requires that within a seven day window over the previous 28 days at least 1,000 returning users triggered the relevant condition and at least 1,000 did not, with model quality sustained over time. Only purchase and in-app purchase events are supported. Small and mid sized stores routinely fail that bar and never see the metrics populate. Check eligibility in the predictive section of the Audience Builder before planning campaigns around it.

Because two months is the default retention setting and most properties are never changed. Standard GA4 properties can be raised to 14 months, which is the maximum outside Analytics 360, where 26, 38 and 50 month options exist. The limit applies to the user level and event level data that powers Explorations, funnels, path analysis and custom segments. Standard aggregated reports such as Traffic Acquisition and Ecommerce Purchases are retained beyond it. Change the setting to 14 months today, because it is not applied retroactively.

Export to BigQuery, which is free to link from GA4 and bills only for storage and queries. The export writes daily event level tables that you own and control, unaffected by GA4's retention ceiling. For most stores the cost is small relative to the value of multi year cohort and lifetime value analysis. Set the export up before you need it, since it is not retrospective and only captures data from the day it is enabled. That single configuration step is the highest value thing most GA4 properties are missing.

They almost never match exactly, and expecting them to causes needless work. GA4 records what the browser successfully sent, so ad blockers, consent rejections, network failures and users leaving before the purchase event fires all create gaps. Your platform records what was actually charged. GA4 also attributes revenue to the session that converted, while your platform records the order date. Differences within a few percent are normal. Treat your commerce platform as the financial record and GA4 as the behavioural one, and reconcile trends rather than totals.

It is a clearer one, but it is not magic. GA4 counts a session as engaged if it lasts over ten seconds, includes a key event or has at least two page views, and engagement rate is the share of sessions meeting that bar. Bounce rate in GA4 is simply its inverse and was reintroduced in 2022. The advantage is that a visitor who reads one page for two minutes is no longer counted as a failure. The limitation is that a ten second threshold is arbitrary and shallow.

Not strictly, but it remains the practical choice for ecommerce. You can install the Google tag directly and use automatically collected events for basic reporting. The moment you need ecommerce events with correctly structured item arrays, custom parameters, consent handling or third party tags, Tag Manager gives you a place to manage all of it without a developer deployment for every change. The exception is platforms with a well maintained native GA4 integration, where the built in ecommerce events are usually more reliable than a hand built container.

Five things, in order. Raise data retention to 14 months, because it is not retroactive and you lose history every day you wait. Link BigQuery export for the same reason. Verify that your four core ecommerce events fire with correct item arrays using DebugView. Mark the events that matter as key events. Link Google Ads if you advertise. Everything else, including audiences, custom dimensions and explorations, is easier to add later and useless without the foundation. Resist the urge to build dashboards before any of that is in place, because a dashboard over incomplete data simply distributes the error faster.

GA4 withholds rows when a report could allow an individual user to be identified, typically where Google signals is enabled and the segment is small. You will see a notice in the report rather than an error. It affects demographic and interest breakdowns most, and small date ranges or narrow segments most of all. The workarounds are widening the date range, removing demographic dimensions, or using the BigQuery export, which is not subject to reporting thresholds because it contains your own raw event data.

For behaviour and acquisition, largely yes. For financial truth, no, and it was never designed to be. Use your commerce platform for revenue, margin, refunds and inventory. Use GA4 for how people arrive, what they browse, where they abandon and which channels contribute. Add BigQuery when you need history beyond 14 months or joins against order data. The failure mode we see most often is teams trying to make GA4 answer finance questions, then losing confidence in it when the numbers do not reconcile.