E-commerce
August 13, 2026
The ecommerce conversion rate Google Analytics number you remember from Universal Analytics (UA) is not under the same label in Google Analytics 4. UA had an Ecommerce conversion rate. GA4 has a session key event rate and a user key event rate. If you open Reports and look for "ecommerce conversion rate", you will think the tracking is broken. Usually, it's not. The metric was renamed when conversions became key events.
Google's help on the Traffic acquisition report defines the session key event rate as the percentage of sessions in which a user triggered at least one key event: sessions with a key event divided by total sessions. This is the closest native stand-in for an ecommerce conversion rate, if you isolate the purchase event. Google automatically marks purchase as a key event (UA conversions to GA4 key events). If you leave the rate on "all key events", add_to_cart or a newsletter signup will inflate the percentage.
This URL answers where to look and how to calculate an e-commerce only rate. The sister article what is the ecommerce conversion rate in Google Analytics stays on definitions. The conversion figure specific to Shopify lives in Shopify analytics and will not match GA4. Consent, ad blockers, and dropped thank-you pages explain most of the gap, not a second secret formula.
What you will clarify: session vs user key event rate, and why purchase must be selected.
What you will be able to do: find the rate in Traffic acquisition, Monetization and Explorations, then plug in Shopify or GTM so that purchase actually fires.
To connect: the GA4 e-commerce tracking setup, conversion rate definitions and Shopify conversion benchmarks.
Don't fixate on a "good" percentage from a 2019 UA screenshot. Use your own purchase key event rate, then compare channels and devices within the same property.
Summary
What is the ecommerce conversion rate in GA4, if UA is dead?
For a store, ecommerce conversion rate means: out of all sessions (or users), how many resulted in an order. In GA4, this order is the purchase conversion event, with value, currency, transaction_id, and an items array (item category, item list, quantity, price). Conversion tracking is not a vanity dashboard. It is how you decide if SEO traffic, paid social, or email is actually buying, and whether conversion rate optimization should target the product page CTA or the checkout process.
Vocabulary UA vs GA4
Universal Analytics: Goals plus Ecommerce conversion rate (transactions / sessions). Sunsetted for standard properties in July 2023.
GA4: every conversion is an event that you mark as a key event. Session key event rate and user key event rate replace the old conversion rate widgets.
Google Ads: you can create Ads conversions from GA4 key events so that bidding and Analytics speak about the same action (About key events).
Why the rename exists
GA4 is event-based for web and app. A purchase, a lead form, and a key CTA click are the same class of object. This flexibility explains why there isn't a single "ecommerce conversion rate" tile. You have to tell the report which key event is the commerce conversion. If you also mark generate_lead or a custom newsletter event as a key event, the conversion rate metric in Traffic acquisition becomes a blended score. Useful for "did something valuable happen". Useless as a Google Analytics ecommerce conversion rate KPI.
Treat purchase as the only conversion event in the headline rate. Keep add_to_cart and begin_checkout as funnel events, not as substitutes. Cart abandonment then has a clear definition: sessions that reached the cart or checkout and never fired purchase. Mixing these events into a single key event rate hides the leak.
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
How does this differ from Shopify analytics and the definition article?
Prevent three Qstomy URLs from colliding. What is the ecommerce conversion rate is the business definition. What is the ecommerce conversion rate in Google Analytics is the GA4 concept. This page is the operator guide: where the conversion rate metric lives, how to filter for purchase, and how Shopify tracking feeds it.
Shopify analytics is not GA4
Shopify analytics counts the orders that Shopify has recorded. GA4 counts the purchase events that the browser or server actually sent. PayPal redirects, strict cookie policy, consent banners, and ITP will make GA4 lower. Treat Shopify as the operational truth for revenue, GA4 as the marketing truth for channel, landing page, and item list. See does Shopify support Google Analytics.
The Shopify conversion rate in the admin is generally orders / sessions in Shopify's own session model. Google Analytics ecommerce reports use GA4 sessions and GA4 purchase events. Never paste both percentages into a weekly slide without a footnote. Finance must reconcile the number of orders, not the two rates.
Which formula: session, user, or purchases?
Write the formula on a post-it before opening Explore. Mixing up numerators is how teams report a 12% "conversion" that is actually add_to_cart.
Session key event rate
Google: sessions with at least one key event / all sessions. For e-commerce, restrict the key event to purchase. This is the session conversion rate for orders. A user who purchases twice in one session still counts as one converted session.
User key event rate
Users who triggered a key event / users. Better for "what proportion of people have already purchased in the window", less suitable for a media site judged by visit. Returning customers inflate this compared to the session rate.
Ecommerce purchases / sessions
Purchases in GA4 are the count of purchase events (how Google populates ecommerce purchases). Dividing this by sessions is close to the old UA ecommerce conversion rate, except that multiple purchases in a session increase the numerator. The session key event rate does not. Choose one and label the dashboard.
Counting method
Key event counting: once per event (recommended) vs once per session (legacy, default for some migrated UA goals). Changing it only affects future hits. For purchase, once per event is generally correct, so that two orders in one session are two purchases. The session key event rate still caps at "this session converted" once.
How to make purchase a reliable key event?
If purchase is not a key event, there is no Google Analytics ecommerce conversion rate to show you, only raw event counts.
Marking the event
Admin: Property > Events, or Data Display > Events depending on the UI version.
Find purchase: Toggle "Mark as key event". Google already does this for the recommended purchase event.
Do not mark everything: add_to_cart as a key event will pollute the session key event rate in reports that do not filter.
Optional funnel keys: begin_checkout can be a key event for a second column, never as a substitute for purchase in the headline KPI.
Debug before trusting the rate
Use DebugView or DebugView GA4 + Chrome GA Debugger during a test order. Confirm the event name purchase, a unique transaction_id, value, currency, and items[]. Duplicate transaction_ids from a reloaded thank-you page inflate purchases. Deduplicate in GTM or server-side if you see this.
Where can I find the rate in the standard GA4 reports?
There is still no report titled Ecommerce conversion rate. You assemble it.
Traffic acquisition (the fastest)
Reports > Acquisition > Traffic acquisition: session default channel group.
Pencil / Customize: add the Session key event rate metric if it is not already there (Google has added it by default to this report in the recent UI).
Key event dropdown: select purchase, not "all key events".
Save as new report or library view: so the team does not go back to the mixed rate.
This view is your ecommerce conversion rate per channel. Pair it with sessions and ecommerce revenue so that a 4% rate on 20 sessions is not celebrated. The session conversion rate here is a session key event rate, not a user conversion rate. If the team asks for session conversion rate vs user conversion rate, respond with two saved reports, not an overloaded table.
Useful secondary dimensions: device category, country, and landing page. SEO landing pages with a high session key event rate and low volume are expansion candidates. Paid campaigns with volume and a crashing rate are creative or offer problems, not "GA4 is broken". Do not use a blog's average conversion rate as a target for a luxury SKU on mobile.
Monetization / Ecommerce purchases
The Ecommerce purchases report is for items: item revenue, items purchased, items added to cart. This is not a conversion rate report. Use it after knowing the rate, to see which item category is actually selling and which item list (collection, search, related) contributed. Google notes that some item metrics only populate from September 8, 2022. If item category is "(not set)", your purchase event is missing the items array, not your conversion rate formula.
User acquisition vs landing pages
User acquisition reports also expose a Key events column. The session key event rate on landing pages answers "which SEO or ads landing page converts". The user key event rate answers "which first-touch source produces buyers". Do not mix them in a slide.
Google Benchmarks
GA4 benchmarking includes session key event rate and user key event rate among comparable metrics. This is industry context in Analytics, not a promise of a 2% "average conversion rate". For published ranges, see ecommerce conversion benchmarks.
How to rebuild the rate in Explorations?
Explorations are where teams recreate a clean UA-style ecommerce conversion rate.
Blank exploration
Explore > Blank: free form.
Dimensions: Session default channel group, Device category, Event name as needed.
Metrics: Sessions, Ecommerce purchases, Session key event rate, Purchase revenue.
Filter (critical): Event name matches regex
session_start|purchaseif you slice by event name. Including session_start keeps non-purchasers in the denominator. Filter purchase-only and every row looks like 100%.
Calculated metric alternative
Admin > Custom definitions > Calculated metrics: ecommerce purchases / sessions. Some UIs need a * 100 and cannot show a % unit. Document the formula in the metric description. This does not replace marking purchase as a key event. It gives you a number that ignores newsletter key events.
Funnel checkout process
A funnel exploration with view_item > add_to_cart > begin_checkout > add_payment_info > purchase is conversion rate optimization, not the headline CR. Cart abandonment is 1 minus (purchase / add_to_cart) only if both events fire reliably. The native Shopify set includes these recommended names when the Google channel is connected. If add_to_cart is missing, you cannot diagnose cart abandonment in GA4. You can only fix a low purchase session key event rate.
How does Shopify send e-commerce events to GA4?
On Shopify, do not start with a custom dataLayer if you have not tried the official path.
Google and YouTube Channel
Shopify Help: Set up Google Analytics 4 and the Google note on the E-commerce purchases report: once the GA4 tags are on the store, certain e-commerce events are collected automatically, including add_to_cart, begin_checkout, and purchase. Google's Shopify event parameter reference lists page_view, view_item, view_item_list, view_cart, add_to_cart, remove_from_cart, begin_checkout, add_payment_info, add_shipping_info, search, and purchase. This is Google Analytics e-commerce tracking without a custom dataLayer, as long as the Google and YouTube channel is connected to the correct GA4 property.
Setup sequence that actually works
Create the GA4 property: a web data stream for the storefront. Do not reuse a UA view ID.
Install the Google and YouTube channel: paste the Measurement ID. Confirm that the sales channel is published.
Place a test order: guest checkout and Shop Pay if you use it. Open DebugView while the thank-you page loads.
Confirm purchase in Realtime: then wait 24 to 48 hours before judging standard reports.
Enable Google signals only if policy allows: and document the cookie policy / consent banner that gates analytics storage.
The thank-you page gap
Purchase generally fires on the order status / thank-you page. If a customer pays off-site (certain PayPal or bank flows) and never returns, the order exists in Shopify and is missing from GA4. This is a tracking path issue. Server-side tracking or a server purchase ping with transaction_id is how the biggest stores close this. Do not "fix" the rate by adding a fake purchase at the start of the checkout.
Cookie policy and consent
If analytics storage is denied, GA4 will undercount. User data on Shopify purchase events also depends on consent and GA settings. Compare GA4 purchases to Shopify orders for the same day before blaming ads. A 20% gap with a strict banner is common. A 90% gap means the tag is not on the checkout. Draft the cookie policy in a language that customers can accept or decline. Do not hide analytics behind a pre-checked box in regions that require a real choice. Consent mode can model some conversions. It does not magically restore a missing purchase event.
When should you use GTM or server-side tracking?
Google Tag Manager is optional on Shopify if the Google channel is already sending the recommended events. Use GTM when you need extra parameters, a second pixel, or a server container. Many agencies still install a full GTM stack "because that's how we used to do Universal Analytics". Duplicate purchase tags are the fastest way to fake a higher ecommerce conversion rate.
Web GTM
Map ecommerce dataLayer objects to GA4 Event tags. Duplicate purchase tags plus the Shopify channel will result in double-counting. Choose a single purchase sender, or deduplicate using transaction_id.
Server-side tracking
A server GTM or a Measurement Protocol hit survives ad blockers better. This is not a CRO tactic. It is measurement integrity. If you add it, keep the same transaction_id as the browser hit and enable deduplication. Otherwise, ecommerce conversion rates will spike overnight for the wrong reason.
Google Ads
Import the purchase key event as an Ads conversion rather than firing a second, unrelated conversion tag. Google documents that Ads conversions created from Analytics key events can be managed in both UIs and used for bidding. Do not optimize ads towards a conversion different from the one on your GA4 dashboard.
What mistakes hurt an ecommerce conversion rate?
These errors produce a Google Analytics "ecommerce" conversion rate figure that is not actually e-commerce.
All key events mixed together: the session key event rate includes every starred event. Select purchase.
Explore filter = purchase only: the denominator collapses. Add session_start to the regex.
Comparing to UA: different session definition, different attribution, apples to oranges.
Items purchased vs purchases: items are units. Purchases are orders. The rate should use orders unless you specify otherwise.
Marking view_item as a key event: almost every session "converts".
Ignoring consent: EU/UK properties look worse than US ones without a modeled path or server-side setup.
Thank-you page not loading: PayPal and some wallets. Reconcile with Shopify.
Cross-domain checkout: broken sessions that split landing and purchase. Fix referral / domain exclusions.
If the figure looks too good to be true, you are probably looking at key events, not purchase. If it looks too bad, you are probably missing purchase hits.
How to use the rate to improve the checkout process?
A rate without a funnel is a vanity KPI. Use GA4 to find where the checkout process dies, then change the store, not the report.
Reading the drop-offs
view_item to add_to_cart: PDP trust, price, size. See how to improve conversion rates.
add_to_cart to begin_checkout: shipping surprise, account wall.
begin_checkout to purchase: payment methods, Shop Pay, PayPal redirect.
Segment before you redesign
Device category, country, and first user source. The mobile session key event rate is often the real issue. Paid social vs organic SEO will not share the same rate. Conversion rate optimization is a list of segments, not a homepage A/B test. If organic landing pages convert and paid landing pages do not, fix the CTA and offer on the ads URL before rewriting the theme.
The user conversion rate is the correct companion metric only when the buying cycle is long: furniture, B2B samples, high AOV. The session conversion rate is the correct daily KPI for media. Publish both. Never average them into a single "average conversion rate" for the board.
CTA and merchandising
The item list and promotion parameters (view_item_list, view_promotion) tell you whether the collection grid or a banner won the purchase. If these events are empty, you only have a store-wide rate. Implement the recommended e-commerce events that Google lists in Set up ecommerce events.
What should be done with sessions that never trigger a purchase?
GA4 explains which sessions did not purchase. It does not sit on the PDP to answer "does this deliver to my zip code?". This question is often the conversion event that you never coded.
Using analytics to target the assistant
High view_item, low add_to_cart: Size, stock, and delivery FAQs in the chat.
High begin_checkout, low purchase: Payment and rights questions, not more Google Ads.
Channel with traffic and zero purchase key events: Landing page mismatch, not a GA4 bug.
Qstomy does not replace Google Analytics 4. It reduces silent exits that never become a purchase event. Keep finance focused on the session key event rate for purchase. Keep the bot on sales questions and support so you do not have to give every agent a GA4 login. Shopify stores can run both. Book a demo.
Checklist, sources and FAQ
Checklist
Confirm GA4 not UA: Property ID G-.
purchase is a key event: Admin > Events.
Test order in DebugView: transaction_id present once.
Traffic acquisition: session key event rate, dropdown = purchase.
Save this report: so that no one reads all the key events.
Reconcile 7 days: GA4 purchases vs Shopify orders.
Consent mode: documented, not wished away.
Single purchase sender: Shopify channel or GTM, not both non-deduplicated.
Funnel events: add_to_cart and begin_checkout firing.
Label the KPI: session purchase rate vs user purchase rate.
In short
Google Analytics Ecommerce conversion rate: in GA4, this is the session key event rate (or user key event rate) restricted to purchase.
No UA-style named metric: customize Traffic acquisition or build an exploration.
Never filter Explore on purchase only: keep session_start in the regex or the rate hits 100%.
Shopify can send purchase for you: Google and YouTube channel. Reconcile with admin orders anyway.
Improve the funnel: not the definition, once the number is honest.
External sources
Google Analytics Help: Traffic acquisition: session key event rate; About key events; UA conversions vs GA4 key events; Set up ecommerce events; Ecommerce purchases report; Key event counting method.
Shopify Help: Set up Google Analytics 4 / automatic ecommerce events.
FAQ
What is a good ecommerce conversion rate in Google Analytics?
There is no single good rate. Use the session key event rate for purchase in your own property, split by device and channel. Compare with Google's in-product benchmarks and industry ranges, not a 2018 UA blog. See what is a good ecommerce conversion rate.
How do I track ecommerce conversions in GA4?
Send the recommended events, especially purchase with items and transaction_id. On Shopify, connect the Google and YouTube channel. Mark purchase as a key event. Check in DebugView.
How can I improve my ecommerce conversion rate using Google Analytics data?
Segment the purchase session key event rate, then inspect the funnel events that precede purchase. Fix the biggest drop-off (often mobile checkout or shipping). Do not increase ads budget on a broken thank-you tag.
What is the formula for ecommerce conversion rate?
GA4 practical: sessions with purchase / sessions, i.e., session key event rate with purchase selected. Alternative: ecommerce purchases / sessions. They diverge when a session contains two orders. State which one you are using.
What are common mistakes when measuring ecommerce conversion rates in GA4?
Reading all key events as ecommerce, filtering explorations on purchase only, comparing to UA, mixing items purchased and orders, and ignoring consent or missing thank-you hits.
Going further
Setup: GA4 ecommerce tracking setup
Enhanced ecommerce: Enhanced ecommerce in Google Analytics
Shopify rate: Good conversion rate for Shopify
Find the ecommerce conversion rate in Google Analytics by selecting purchase on the session key event rate, then trust the number only after a test order and a Shopify reconciliation. See Qstomy if the leak is questions on the product page, not the tag.
Enzo
August 13, 2026
