Skip to content
All field notes
Measurement
Published
Nov 1, 2026
Reading time
10 min read

GA4 Key Event Rates: Audit Counts, Filters and Denominators

Reconcile GA4 session and user key event rates with the right numerator, specific-event metrics, complete populations and aggregation before changing tracking.

AP
AdProof Research
Independent measurement desk
Repeated action receipts belong to distinct visit folders, while a rate compares qualifying visits with the complete set and keeps user identity separate.
Count the sessions or users that qualified, then preserve the population used as the denominator.
In this guide (9 sections)

When a GA4 key-event rate does not equal Key events divided by Sessions or Users, check the numerator before changing tracking. A session key-event rate counts sessions in which the selected qualifying action occurred. A user key-event rate counts users who performed it. Neither numerator is simply the number of event occurrences.

Then preserve the original population. Selecting a particular key-event rate, filtering a report to that event and averaging daily percentages are different operations. They can answer different questions even when the chart labels look similar.

The practical diagnostic is to specify the action and denominator, retrieve the supported rate for that scope, and compare it with compatible counts. Treat a difference as evidence to investigate, not an automatic duplicate-event finding.

Three real questions expose different counting mistakes#

An older dashboard question asks why dividing key-event count by sessions does not reproduce Session key event rate. A reply explains that several occurrences can belong to one qualifying session. That is a plausible mechanism to test, not proof of the original implementation's exact event distribution.

A separate user-rate question describes a built-in User key event rate that is higher than an attempted event-count-to-user calculation. The author later points to ISO-week regrouping. That comparison needs date, field, event-selection and aggregation checks; repetition alone does not explain every direction of disagreement.

A third question describes rates approaching 100% after adding Event name and filtering for individual conversions. It asks how to obtain a rate for one action without losing the intended baseline.

These are verified older questions, not evidence of a fresh GA4 outage. The articles use older conversion terminology in places; the current metric and selected report should determine the analysis.

Related guide

Check the population behind each rate

Record the numerator, denominator and filters before comparing key-event rates.

Use the tracking QA checklist

Opens a practical guide. No email required.

1. Write the rate as a sentence before writing a formula#

Define the action and population in plain language. For example: “Among the sessions in this property, date range and session-source cohort, what proportion included the registered generate_lead key event?”

Google's Traffic acquisition reference defines Session key event rate using sessions in which a key event happened, divided by total sessions. Its User acquisition reference separately defines User key event rate using users who performed a key-event action, divided by total users.

MeasureUnit in the numeratorDenominator or interpretation
Key-event countCounted occurrences under the applicable counting policyA count, not a session/user rate
Session key-event rateSessions containing the selected qualifying actionCompatible total sessions
User key-event rateUsers performing the selected qualifying actionCompatible total users
Key-event count divided by sessionsCounted occurrences per sessionFrequency of counted actions, not necessarily the share of sessions qualifying
Accepted-lead rateBusiness-accepted leads under an explicit definitionThe chosen eligible business population

Record the exact denominator field. Total users, Active users, New users and Sessions are different fields; do not substitute the most convenient one. Also record whether the rate covers any key event or one named action.

A lead-submission key event does not establish a qualified lead. If accepted business outcomes are the question, keep their definition and evidence separate from Analytics' event classification.

2. Keep the report population unchanged#

Save the property, stream selection, dates, timezone, reporting surface, dimension scope, filters, comparisons and key-event selection. Retain the original export before simplifying the report.

Start with a minimal acquisition view: the relevant session-scoped source or channel, Sessions and the supported session rate for the chosen action. For a user-based question, use a compatible user population and rate. A first-user acquisition row and a session-source row do not automatically describe the same set of visits.

Remove optional breakdowns one at a time and record which change alters the discrepancy. Do not erase a reporting filter just because its removal makes the headline percentage more reassuring; it may define the business question you actually need to answer.

When testing an event-name filter, compare the denominator before and after it. If the result only contains sessions or users already associated with the qualifying action, that is a conditional population. It is not the original all-traffic baseline.

This does not mean every Event name filter always produces 100% in every surface. The exact query and reporting behavior matter. Inspect the retained population and request definition rather than copying that explanation across standard reports, explorations and connectors.

If a genuinely missing landing page or source is involved, use the GA4 missing-field diagnostic. Changing a denominator cannot recover an uncollected pageview or prove that a source label is correct.

3. Use a specific-key metric rather than inventing a denominator#

Where the report provides a key-event selector, verify that the displayed rate refers to the intended action. A chart restricted to one event name is not automatically equivalent to selecting that action's rate within the original population.

For a Data API implementation, Google's current metric schema documents both overall and event-specific rate metrics:

sessionKeyEventRate
sessionKeyEventRate:generate_lead
userKeyEventRate
userKeyEventRate:generate_lead

The unqualified metrics refer to any key event; the suffix selects a particular registered key event. These are metric identifiers to verify against the property, not a complete executable request or a guarantee that every connector exposes the same fields.

The schema says an event must be registered as a key event for its specific rate request to succeed. Use the property's supported metadata to discover the available identifiers rather than guessing from a renamed display label. Google's Metadata method reference describes retrieving available reporting fields.

Save the selected metrics and filters with the request. The runReport reference treats dimensions, metrics, date ranges and filters as separate parts of the request. Changing one is a methodological change, not merely a new column heading.

If a connector cannot expose the specific rate, document the limitation. A manual ratio is useful only when its numerator is actually qualifying sessions or qualifying users at the correct grain. Do not replace an unavailable unique-user numerator with event count and keep the old label.

A hypothetical example with repeated actions and overlap#

Assume one completely observed teaching population of 100 sessions and 70 distinct users, with Once per event counting for the occurrence column. Two registered key events, A and B, have these invented records:

ObservationAction AAction B
Counted event occurrences1810
Sessions containing the action128
Users performing the action97

Four sessions contain both A and B. Three users perform both actions during the period.

The session rate for A is 12/100 = 12%. Dividing its 18 occurrences by 100 gives 0.18 counted occurrences per session, or 18 occurrences per 100 sessions. It does not establish an 18% share of sessions performing A.

The user rate for A is 9/70, approximately 12.86%. There is no requirement for this percentage to equal the session rate; one user can have multiple sessions.

For any of these two key events, the qualifying-session union is 12 + 8 − 4 = 16, giving 16%. Adding the two individual session rates would give 20% and count the overlapping sessions twice.

The qualifying-user union is 9 + 7 − 3 = 13, giving 13/70, approximately 18.57%. Adding the action-specific user numerators would likewise double count people who performed both actions.

A useful sanity check follows: within this same complete observed population, users who performed an action cannot outnumber its observed occurrences, because each qualifying user needs at least one occurrence. Therefore, an unexpectedly higher built-in user rate than an event-count-to-user ratio should not be explained solely by repetition. First check whether the comparison truly shares event selection, dates, counting basis, identity and aggregation.

These figures explain the units. They do not prove how a real property's modeled, filtered or differently scoped reports will reconcile.

4. Recalculate the correct total instead of averaging rates#

For compatible, disjoint session populations, combine qualifying-session counts and session denominators before calculating the aggregate rate. Do not give a tiny row the same weight as a large one merely because both display a percentage.

Consider a separate hypothetical example:

Compatible session cohortQualifying sessionsTotal sessionsRate
Small cohort51050%
Large cohort99010%
Combined1410014%

The simple average of 50% and 10% is 30%, which does not describe the combined session population. The correct combined calculation is (5 + 9)/(10 + 90) = 14%.

Google's calculated-field reference illustrates aggregate ratios by aggregating the numerator and denominator explicitly. That does not authorize replacing a built-in rate with a formula whose components are unavailable or already summarized at an incompatible grain.

Users require additional care. A person present on Monday and Tuesday contributes to each day's distinct-user population, but may be one user over the combined interval. Even weighting daily user rates by daily user counts cannot generally reconstruct the full-period distinct-user rate. Request the metric for the intended week or month at source where supported.

This is why changing a chart from daily to ISO-week grouping needs a comparison with a direct, same-period source report. Do not infer that a higher or lower weekly result necessarily means the underlying events disappeared.

5. Check counting policy without using it to hide a trigger defect#

Google's key-event counting reference distinguishes Once per event from Once per session. Record the selected policy and its effective period when interpreting the count column. It is a separate configuration question from the proportion of sessions or users that performed an action.

If an accepted lead emits several unintended events, investigate the collection path. Reducing a counted total through a policy change does not establish that repeated execution was repaired. The platform-versus-independent guide owns the detailed comparison among per-event, per-session and advertising conversion policies.

Use the tracking QA checklist to trace one authorized journey and its actual outgoing events. Avoid generating fake production leads or changing conversion settings solely to make two displayed rates agree.

Keep engagement rate separate too. It classifies sessions under its own qualification rules; it is not another label for the selected business action's rate. A high rate of either type does not identify humans or establish causal sales performance.

Close with an evidence packet another analyst can reproduce#

Retain the original report, simplified comparison, metric identifiers, action selection, date and identity scope, filters, count policy and aggregation method. Record the direct source result for the same period and what changed when the chart was regrouped.

Classify the finding narrowly: wrong numerator, changed denominator, overlapping actions, incompatible aggregation, unsupported field or an actual collection defect. Keep any unresolved portion explicit. A plausible arithmetic explanation should not become a claim that every missing business outcome was measured correctly.

For an advertising review, preserve a separate delivery baseline. The anonymous fashion-retail case study establishes impression measurement, not a verified user conversion rate or sales uplift. AdProof supports scoped campaign exports with dates, timezone and available dimensions. Use those advertising records alongside the GA4 rate contract and business-outcome evidence; AdProof does not repair GA4 denominators or automatically reconcile individual users with orders.

Frequently asked questions#

Why does Key events divided by Sessions differ from Session key event rate?

The count can include several occurrences in one session. Session key event rate instead measures the share of compatible sessions in which the chosen action occurred. Verify action selection, count policy, dates and population before concluding that duplication explains the difference.

How do I report the rate for one key event?

Use the report's supported action selector or a property-supported event-specific rate metric. The Data API documents session- and user-based metrics with an event-name suffix for registered key events. Filtering Event name is a different operation whose population needs checking.

Can I add the rates for several key events?

Not to obtain the share performing any of them when sessions or users overlap. Use the union of qualifying members within the same denominator. Keep per-action rates when the business question concerns each action separately.

Why does the weekly user rate differ from an average of daily rates?

Daily percentages have different denominators, and the same user can appear on several days. Request the intended full-period distinct-user metric rather than assuming that averaging or summing daily rows reconstructs it.

Your next step

Check the population behind each rate

Record the numerator, denominator and filters before comparing key-event rates.

Use the tracking QA checklist

Opens a practical guide. No email required.

Back to all field notes