Google Analytics Lead Generation Events and Key Event Set-Up
Plan events for forms, calls and chats.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan tracking for a lead generation site in Google Analytics. Actions that count as leads (form submit, click to call, chat start, booking): [LEAD_ACTIONS]. Pages and tools involved: [PAGES_AND_TOOLS]. Consent approach: [CONSENT]. For each lead action define the event name, the trigger in plain words (such as the thank-you page loading, or the form-submitted event firing only after validation passes), parameters such as form name, page and button label with no personal data, whether it is a key event, and a test. Count each lead once, with duplicate protection and a view on thank-you page versus event approaches. Click-to-call records an intention, not a call, so label it accordingly. Test: submit a form with test details three times and confirm exactly three events appear, then submit with a required field blank and confirm none do. Keep a testing log and a record of the date each event changed. Reconcile monthly with CRM leads: 52 events against 47 CRM leads is a gap of 5, or 9.6 percent, with causes to check (spam, tests, duplicates, blocked tracking). Mark tool steps [VERIFY] and check settings against the current documentation.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.