Analytics
Conversion event
A conversion event is an instrumented occurrence chosen to represent a meaningful business outcome, although current GA4 calls the owned-site or app designation a key event.
What it means
An event first needs a stable name, trigger condition, parameters and validation rule. Marking it as a GA4 key event changes reporting from that point forward rather than rewriting history; a Google Ads conversion can then be created from the key event for campaign measurement and bidding, with its own counting and Attribution settings.
Why it matters
Separating raw event collection, key-event designation and advertising conversion configuration prevents one label from hiding different timestamps, scopes, counts and decision rights.
Example
A `generate_lead` event fires only after a server-accepted form submission, carries no unnecessary personal data, is marked as a GA4 key event and is tested before any separate Google Ads conversion is configured.
Common mistakes
Do not trigger on button Clicks when submission can fail, rename events without migration, mark broad pageviews as outcomes, send unnecessary personal data, assume retroactive reporting or confuse an event occurrence with a unique converting user.
How AYSA handles this
Signals reviewed
event name, trigger condition, parameters, validation response, key-event state, duplicate rule, consent state
Problem AYSA can identify
AYSA can identify a supported website event whose trigger fires too early, lacks validation, duplicates outcomes or conflicts with the documented contract.
Recommendation prepared
The review proposes a bounded instrumentation correction and a test protocol before changing key-event or advertising settings.
Approval preview
The user sees the exact trigger, parameters, data handling and supported WordPress code change before approval.
Execution
AYSA can apply an approved supported WordPress instrumentation change; GA4 and advertising configuration require the relevant authorized connection and separate approval.
Verification
Browser behavior, server acceptance, collection receipt and processed key-event reporting are checked as distinct stages.
Limits
Client blocking, consent, network failure, platform processing and CRM validity limit measurement, and an event record does not prove business value.
Sources and further reading
- Google Analytics — Recommended events — Official analytics documentation
- Google Analytics — Introducing key events for behavioral analytics — Official analytics documentation
- Google Analytics Data API — Dimensions and metrics — Official analytics documentation
Written by Marius Dosinescu. Reviewed by AYSA SEO Editorial Team · 2026-07-28 00:00:00.
Quick answers
Frequently asked questions
What is a conversion event called in current GA4?
An important website or app event is called a key event; conversion now refers to an important action configured for advertising measurement.
Does marking an event as a key event change historical data?
No. The designation affects reporting from the time it is created and does not retroactively rewrite earlier event data.
SEO execution campaign
Less SEO work. More organic growth.
AYSA monitors your website, finds opportunities, prepares the work, asks for approval and executes accepted changes so you can grow without living in SEO tools.
