Map the event to a business action

List each key event and describe what a single occurrence represents. A completed purchase, a booked appointment and a click on a contact button have different implications for counting and optimization.

Record the event name, triggering condition, expected frequency, responsible owner and downstream source of truth. Do not mark every engagement event as a primary business conversion.

Understand counting choices

GA4 supports counting once per event or once per session for key events. Once per event counts each qualifying occurrence; once per session limits the count to one occurrence per session for that key event.

Neither choice repairs a duplicate tag. If a confirmation page fires twice for one purchase, investigate the implementation and transaction identifiers rather than hiding the error with a counting setting.

Test realistic user journeys

In a controlled environment, complete one action, refresh the confirmation page, return to the site and complete another legitimate action. Inspect event payloads, timestamps and identifiers in DebugView and relevant event reports.

Compare the observed behaviour with the intended rule. A single customer may legitimately submit two separate service requests, while two events from one button press may be a bug. The counting method should reflect that distinction.

Reconcile with operational systems

For ecommerce, compare transaction IDs and purchase totals against the order system. For leads, compare unique CRM records and accepted inquiries against analytics counts. Document cancellations, spam and duplicate submissions separately.

Use a reconciliation table with event count, unique business records, differences and reasons. A reporting dashboard should not silently equate analytics key events with customers or booked revenue.

Manage reporting changes

When changing counting methods, record the effective date, stakeholders and dashboard impact. Historical comparisons may not be like-for-like, especially when downstream Google Ads conversions use different settings or attribution rules.

Annotate major changes in monthly reporting and retain a versioned measurement specification. Do not promise that changing a GA4 setting will retroactively make all connected reports comparable.

Decision checklist

Before approving a key event, confirm the event fires only when the user action succeeds, has a documented counting rule, includes appropriate identifiers and can be reconciled with a business system.

Review after site releases and tag-manager updates. Report uncertainty explicitly when identity, consent or attribution prevents exact parity, and prioritize correcting implementation defects before optimizing campaigns from the data.

Counting example

A confirmation event fires when a visitor submits a request, then fires again when they refresh the success page. Counting once per session can conceal the duplicate, while counting once per event exposes it. The implementation still needs to be repaired.

Conversely, two legitimate requests in one session may deserve two counted events. Test both scenarios with known CRM record IDs before choosing a reporting definition.