Key takeaways
- GA4 records page views, scrolls and outbound clicks automatically through enhanced measurement, but it does not reliably track leads until you set up events for form submissions, phone taps and chats.
- Google renamed conversions to key events in GA4 in March 2024. You mark lead events as key events in Admin so they appear in reports and attribution.
- Standard GA4 properties allow 30 key events and 25 parameters per event, so reserve key event status for real lead actions.
- Event parameters such as form name and lead type let you see which forms, pages and channels produce leads.
- Google Tag Manager is the most flexible way to add and maintain lead events without editing site code.
GA4 is built around events: every interaction, from a page view to a form submission, is an event. For lead generation sites, the events that show where leads come from need configuration. This Emulent guide covers which events to track, how to set them up in Google Tag Manager, how to mark them as key events and how to keep them accurate.
Which events should lead generation websites track?
Track the actions that produce leads first, then a few signals of intent. Tracking everything clutters reports.
| Event | Why to track it |
|---|---|
| Form submissions | fire an event only on successful submission for every lead form, including contact, quote and demo requests. Google’s recommended event name is generate_lead. |
| Phone taps | track clicks on tel: links, especially on mobile. Pair them with call tracking if you need to know which calls became customers. |
| Chat starts | track when a visitor opens a conversation in your chat widget, using the vendor’s GTM integration or event callbacks where available. |
| CTA clicks | track “Get a quote” and “Schedule a demo” buttons as engagement steps, not key events. |
| Content downloads | track gated guides and templates that capture an email address. |
| Pricing and service page views | use these for audiences and analysis rather than marking them as key events. |
Enhanced measurement includes form interaction events, but they fire on many forms, including search boxes, and can count attempts that failed validation. Most lead sites get more accurate counts from a custom generate_lead event.
How do you implement events using Google Tag Manager?
Create a trigger for each action and a GA4 event tag that sends the event name and parameters.
- Form submissions by thank-you page: trigger on the confirmation URL and send generate_lead with a form_name parameter. This is the most reliable method when every form redirects.
- Form submissions without a redirect: use your form plugin’s success event pushed to the data layer. Gravity Forms, Contact Form 7 and HubSpot forms all support this.
- Phone taps: use a “Just Links” click trigger where the click URL contains tel:, and send a phone_click event with the page path.
- CTA clicks: use an “All Elements” click trigger filtered by the button’s CSS class or ID, and send a cta_click event with the button text.
- Downloads: enhanced measurement already logs file_download for common file types; add a custom event only for gated assets that need extra parameters.
Register parameters you want in reports, such as form_name, as custom dimensions in GA4 Admin. Standard properties allow 25 parameters per event and 50 event-scoped custom dimensions.
How do you turn events into key events in GA4?
Creating an event and marking it as a key event are separate steps, and teams often skip the second.
- Wait for the event to fire. New events can take up to 24 hours to appear in Admin.
- In Admin, open Data display, then Events, and mark generate_lead, phone_click and chat_start as key events. You can also create a key event ahead of time by entering its exact name.
- Check the Key events column in your acquisition reports and the Advertising section after 24 to 48 hours.
- Keep the list short. GA4 standard properties cap you at 30 key events per property.
- If you run Google Ads, link the property and import the same key events as conversions so bidding uses lead data.
How do you validate and maintain event tracking?
Test at launch and after every site change, because form and theme updates break tracking without warning.
- Use GTM preview mode with GA4 DebugView. Complete each action and confirm the event and its parameters arrive once.
- Retest after plugin, form or theme updates. On WordPress, a page builder layout change or form plugin update can rename the CSS class your trigger relies on.
- Compare GA4 generate_lead counts with CRM leads each month. A gap above 10% to 20% usually means a broken trigger, spam submissions or consent opt-outs.
- Set data retention to 14 months in Admin, since the default is two months for exploration reports.
How can the Emulent team help?
Emulent configures GA4 and Google Tag Manager for lead generation sites, from event plans and key events to CRM reconciliation and Google Ads imports. For larger organizations, our enterprise SEO team ties lead tracking to organic performance. A caveat: consent choices, blockers and Safari restrictions mean GA4 will undercount leads compared with your CRM, so treat your CRM as the source of truth for lead totals. Contact the Emulent team to set up lead tracking.