Choose an action that represents business progress
A button click describes an attempt; a confirmed submission describes a later outcome. A sales-accepted opportunity is later still. Choose the event that answers the reporting question and preserve those stages separately. Google Analytics also distinguishes key events from conversions used to measure and optimize advertising.
Illustrative enquiry trace: request REQ-DEMO-23 is accepted by the form endpoint, the visitor receives a confirmation and the CRM creates one request record. The analytics event corresponds to that successful acceptance, rather than firing every time the Send button is clicked. If the CRM handoff fails, the operational log preserves the failure instead of quietly calling the request a qualified opportunity.
Avoid treating every click as a lead
A key-event label does not establish message delivery, sales qualification or revenue. Consent choices, duplicate firing and disconnected systems can affect the reported count. The counting method matters too: Google Analytics can count a key event once per event or once per session. Neither setting replaces checking the underlying business record. Do not place personal enquiry details in analytics payloads to make reconciliation easier.
Next, define the confirmation condition and trace an authorized test from the browser to the business record. Verify a failed submission and a repeated confirmation visit as well as the successful path before relying on the report.
Website field guide · Verify purchase and demo events after a website change · Qualified demo
Reference: Google Analytics: conversions and key events; Google Analytics: key-event counting methods. Checked November 4, 2026.