> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Conversion Rate (User), Google Analytics 4 > Conversion Rate (User) for Google Analytics 4 stores. User-based equivalent of session conversion rate, typically higher because the same user has multiple sessions. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Analytics](/nerve-centre/connectors#connectors-by-type) ## At a glance > The percentage of GA4 *users* who converted at least once in the period, the user-based companion to [Conversion Rate (Session)](/nerve-centre/kpi-cards/google-analytics/ecommerce-conversion-rate). Where session conversion rate asks "what share of visits ended in a purchase", this card asks "what share of people bought". **It is typically higher than session conversion rate** because one user can open several sessions before buying, but only needs to convert once to count. Requires GA4 key events to be configured. Reading the two together tells you whether you have a conversion problem (low on both) or a multi-visit consideration cycle (session rate low, user rate healthy). | | | | ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | GA4's `userConversionRate` metric: the count of users who fired at least one *key event* (typically `purchase`) divided by total active users, returned as a percentage. A user who buys three times still counts once in the numerator; a user who visits five times without buying counts once in the denominator and zero in the numerator. | | **Sample basis** | Users, not sessions. GA4 identifies a user by a combination of first-party cookie, Google Signals (where consent allows), and the `user_id` you pass if you have logged-in identity. The denominator is *active users* (users with at least one engaged session in the window), not lifetime users. For the visit-based view, see [Conversion Rate (Session)](/nerve-centre/kpi-cards/google-analytics/ecommerce-conversion-rate). | | **Sampling threshold** | GA4 standard properties sample reports above roughly 10M events per query window; GA4 360 raises this to 1B. The connector requests `runReport` with the property's default settings and `T/7D/30D vsP` windows sit well below the standard threshold for most stores. Sampled responses carry a `samplingMetadatas` flag; suspiciously round numbers are the visible tell. | | **Bot traffic filter** | Filtered. GA4 applies its built-in bot exclusion (the IAB/ABC International Spiders and Bots list) plus any internal-traffic or custom filters configured at the property level. The card respects whatever the merchant has set; it does not add or remove filters. | | **Key Event dependency** | **Critical.** Since the late-2024 rename of *Conversions* to *Key Events*, the `purchase` event must be marked as a key event in GA4 Admin → Events for this metric to populate. If it is not marked, this card returns **0** even while orders flow normally. The engine surfaces a setup-hint card when traffic is healthy but conversions read zero. | | **Identity and consent gaps** | User counting depends on identity. Ad blockers, cookie-consent rejection, Safari ITP cookie expiry, and cross-device journeys without a shared `user_id` all cause one real person to be counted as several users. This inflates the denominator and **depresses user conversion rate relative to the true person-level rate**. The effect is structural, not a connector defect. | | **Time zone** | The merchant's GA4 property time zone, set in Admin → Property → Property Settings. The connector does not override; multi-property merchants see each property in its native zone unless aggregated at the profile level. | | **Currency (revenue events)** | n/a, this is a user-count ratio. The underlying `purchase` events carry `value` in the property's reporting currency, but the rate itself is unitless. | | **Relationship to session conversion rate** | User rate is normally **higher** than session rate, because the numerator (users who bought) is divided by a smaller denominator (people) than the session rate's denominator (visits). The ratio between the two is itself a signal: a wide gap means a long, multi-visit consideration cycle; a narrow gap means people tend to buy on the same visit they arrive. | | **Time window** | `T/7D/30D vsP` (default 30 days vs the prior 30 days). Daily aggregation. | | **Alert trigger** | `drop >15% vsP`. A user-rate drop with a flat session rate points at an identity or audience-mix shift; a drop on both rates points at a genuine conversion or measurement regression. | | **Sentiment key** | `ga_conversion_rate_user` | | **Roles** | owner, marketing | ## Calculation Calculated automatically from your Google Analytics 4 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example The numbers below are illustrative, chosen to show how the two conversion rates read together. They are not drawn from a real merchant's account. A UK supplements brand on Shopify with GA4 connected, 30-day window ending Wednesday 14 May 26. | View | Denominator | Converters | Rate | | ----------------------------- | ------------------: | ------------------------: | --------: | | **Conversion Rate (Session)** | 162,400 sessions | 3,890 converting sessions | **2.40%** | | **Conversion Rate (User)** | 96,100 active users | 3,540 converting users | **3.68%** | | Prior period (user) | 99,800 active users | 3,690 converting users | 3.70% | What the two-rate comparison is telling us: 1. **User rate sits above session rate, as expected.** 3.68% of people bought versus 2.40% of visits. The gap exists because the average buyer in this account opens roughly 1.5 sessions before purchasing, so each converting user is spread across more than one session in the denominator of the session rate. **The gap being stable period-to-period is the health test**, not the absolute size of the gap. 2. **The session-to-user ratio reveals the consideration cycle.** A user rate that is \~1.5x the session rate signals a moderate multi-visit cycle: people research, leave, and return before buying. A brand selling considered purchases (furniture, high-AOV electronics) would show a wider gap; an impulse-buy brand (snacks, low-AOV accessories) would show the two rates almost on top of each other. Reading the ratio tells you what kind of buying behaviour you are actually running. 3. **The alert would not fire here.** User rate moved from 3.70% to 3.68%, a 0.5% change, far below the 15% trigger. The metric is steady. 4. **What a divergence between the two rates would mean.** If user rate held at 3.68% while session rate fell sharply, the likely cause is a traffic-mix shift, a burst of low-intent sessions (a new paid campaign, a bot wave, a viral referral) inflating the session denominator without adding buyers. The people who were going to buy still bought; there are just more non-buying visits diluting the session rate. Conversely, if user rate fell while session rate held, suspect an identity or audience change: Google Signals turned off, a consent-banner update fragmenting users, or a cohort of habitual repeat buyers dropping out. 5. **Why user rate is the better lens for loyalty and retention questions.** Session rate answers "is each visit productive". User rate answers "are we turning people into customers". For decisions about acquisition cost (you pay to acquire *people*, not sessions) and for lifetime-value modelling, the user rate is the cleaner input. Pair it with [New vs Returning Users](/nerve-centre/kpi-cards/google-analytics/new-vs-returning-users) to see whether converting users skew new or returning. The diagnostic flow when this card flags amber: 1. **Compare against [Conversion Rate (Session)](/nerve-centre/kpi-cards/google-analytics/ecommerce-conversion-rate) first.** Both down together points at a real conversion or measurement regression; user-only down points at identity or audience mix. 2. **Check identity settings.** Confirm Google Signals is still enabled (Admin → Data Settings → Data Collection) and that any `user_id` implementation is still firing. A change here re-counts people as more users and drags the rate down without any behaviour change. 3. **Decompose by new vs returning.** Returning users convert at a materially higher user rate than first-time users; a shift in the new-to-returning mix moves the blended figure. [New vs Returning Users](/nerve-centre/kpi-cards/google-analytics/new-vs-returning-users) isolates this. 4. **Cross-reference [GTM Tag-Fire Rate](/nerve-centre/kpi-cards/google-analytics/gtm-tag-fire-rate).** If the `purchase` key event stopped firing reliably, both rates fall and the cause is measurement, not behaviour. ## Sibling cards merchants should reference together * **[Conversion Rate (Session)](/nerve-centre/kpi-cards/google-analytics/ecommerce-conversion-rate)** is the direct counterpart. Read the two together: the user rate over the session rate tells you how many visits the average buyer takes before converting. * **[New vs Returning Users](/nerve-centre/kpi-cards/google-analytics/new-vs-returning-users)** explains shifts in the user rate. Returning users convert at a much higher user rate; a change in the new-to-returning mix moves the blended number. * **[Returning Users](/nerve-centre/kpi-cards/google-analytics/returning-users)** for the loyalty-cohort view that pairs naturally with a person-level conversion rate. * **[Conversion by Source](/nerve-centre/kpi-cards/google-analytics/conversion-by-source)** to see which channels acquire users who actually convert, the user rate's per-channel decomposition. * **[Cart Abandonment Rate](/nerve-centre/kpi-cards/google-analytics/cart-abandonment-rate)** decomposes where intending buyers fall out before they convert. * **[GTM Tag-Fire Rate](/nerve-centre/kpi-cards/google-analytics/gtm-tag-fire-rate)** is the first stop when both conversion rates drop without an obvious checkout reason; tag regressions hit conversion before any other metric. * **[Revenue per User](/nerve-centre/kpi-cards/google-analytics/revenue-per-user)** is the commercial companion. User conversion rate counts how many people buy; revenue per user sizes what each buying (and non-buying) person is worth. ## Reconciling against Google Analytics 4 **Where to look in Google Analytics 4's own dashboard:** * **Reports → Acquisition → User acquisition** carries a "User key event rate" column, the closest match to this card's headline. * **Reports → Monetization → Ecommerce purchases** shows purchase activity; pair with the user-acquisition report for the user-rate framing. * **Explore → Free-form exploration** for custom segmentation: use `userConversionRate` (or the key-event-rate metric) with a dimension such as `newVsReturning` or `firstUserDefaultChannelGroup` to replicate the card's decomposition. * Note that GA4's standard reports default to **session** key-event rate in several tables; check the column header carefully so you are comparing user-to-user, not user-to-session. **Why the Vortex IQ user conversion rate may legitimately differ from GA4's UI count:** 1. **User-rate versus session-rate column confusion.** The single most common reconciliation error is comparing this card to a GA4 table that is showing the *session* key-event rate. Confirm the GA4 column reads "user", not "session", before assuming a divergence. 2. **Sampling thresholds.** Above the property's sampling threshold both views show sampled data, and GA4's UI may use a different sampling token than the API request, producing small rounding differences. 3. **Identity-model timing.** User counts depend on Google Signals, cookie state, and `user_id`. GA4 re-evaluates identity as data arrives; a report pulled before late-arriving identity resolution can show a slightly different active-user denominator than one pulled later. 4. **Time-zone alignment.** GA4 reports in the property's configured time zone; Vortex IQ aligns to the merchant's profile time zone, so boundary-day users can land on different days. 5. **Filter-application timing.** GA4 internal filters apply at processing time; data processed before a filter was added stays in historical reports, so recently added filters apply inconsistently across older periods. **Cross-connector reconciliation:** * **GA4 user conversion rate vs your commerce platform's customer conversion rate**: not definitional twins. Shopify, BigCommerce, and Adobe Commerce count *customers* with their own identity logic (email, account, device), which differs from GA4's cookie-plus-signals identity. Expect the commerce-platform figure to read higher, because it does not fragment one person into several cookie-users the way GA4 does under consent and ITP pressure. * **GA4 user conversion rate vs Klaviyo converting-profile rate**: Klaviyo counts profiles (email identities) that placed an order; GA4 counts cookie-or-signals users. The two move together directionally but will not match in absolute terms because the identity unit differs. ## Known limitations / merchant FAQs **Why is my user conversion rate higher than my session conversion rate?** By design. The user rate divides converting people by active people; the session rate divides converting visits by all visits. Because the average buyer opens more than one session before purchasing, the session denominator is larger relative to its numerator, so the session rate comes out lower. A user rate above the session rate is the normal, healthy pattern. If the two were equal it would imply every buyer purchased on their very first visit, which is unusual outside pure impulse-buy categories. **My user rate dropped but my session rate is flat. What happened?** The likely cause is an identity or audience-mix change, not a conversion problem. Check whether Google Signals was disabled, whether a consent-banner update started fragmenting users into more cookie-users, or whether a `user_id` implementation stopped firing. All three inflate the active-user denominator without changing real behaviour, which drags the user rate down while the session rate, computed on visits, holds. A genuine drop in buying behaviour would pull both rates down together. **My user conversion rate is showing 0%. Is everything broken?** Most often the `purchase` event is not marked as a key event in GA4. After the late-2024 rename of Conversions to Key Events, the metric only populates for events flagged as key events. Go to Admin → Events, find your `purchase` event, and toggle "Mark as key event". The rate repopulates within a few hours. Vortex IQ detects the pattern of healthy traffic with zero conversions and surfaces a setup-hint card. **Is this number affected by consent mode and ad blockers?** Yes, and more so than the session rate. Identity is the input that consent rejection, ad blockers, and Safari ITP attack hardest. When a person is counted as several cookie-users across blocked or expired sessions, the active-user denominator grows and the user rate falls below the true person-level rate. The effect is structural; treat the trend against the brand's own baseline rather than against a theoretical "real people" rate. **Should I report the user rate or the session rate to my board?** Neither GA4 number is the source-of-truth conversion rate; the commerce platform owns that. Within GA4, use the session rate as the cleanest change-detector for checkout and tag health, and use the user rate when the question is about turning people into customers, acquisition economics, or retention. Reporting both, with the gap between them as a third line, is the most informative framing. **Does a repeat buyer inflate my user conversion rate?** No, the opposite of double-counting. A user who buys three times in the period counts once in the converter numerator, not three times. That is precisely what distinguishes the user rate from order-count metrics: it measures the breadth of conversion (how many people bought) rather than the volume (how many orders). Use [Revenue per User](/nerve-centre/kpi-cards/google-analytics/revenue-per-user) for the value-per-person view. **Can Vortex IQ trigger actions in GA4?** Read-only by design. Vortex IQ surfaces the user conversion pattern and flags movement; the merchant's team executes inside GA4 (identity settings, key-event configuration, audience definitions) or upstream (acquisition and landing-page work). Ask Viq lets you interrogate the number in plain English, and Vortex Mind traces the upstream cause when it moves. *** ### Tracked live in Vortex IQ Nerve Centre *Conversion Rate (User)* is one of hundreds of KPI pulses Vortex IQ tracks across Google Analytics 4 and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.