GA4 Key Events Setup with Google Tag Manager: A Marketer's Guide
Short answer: To set up key events in GA4, create the events you care about (for example generate_lead, whatsapp_click and call_click) with Google Tag Manager, test them in GTM Preview and GA4 DebugView, then mark them as key events in GA4's Admin under Events. Key events are what GA4 used to call conversions.
Most small business sites do not need fifty tracked events. They need three or four that match how the business actually gets customers, set up so they fire once and only when the action really happens. Getting those right matters more than any dashboard you build later.
It is written for marketers, not developers, and explains the rename from conversions to key events, gives a minimal event plan, and walks through building and testing it in Google Tag Manager.
What happened to conversions in GA4?
In 2024 Google renamed GA4 'conversions' to 'key events'. The word 'conversion' now refers to actions counted in Google Ads, which you usually import from GA4 key events or track with the Google Ads tag.
In practice: you mark important events as key events in GA4. If you also want Google Ads to optimise for them, you import them into Google Ads as conversions (or set up Google Ads conversion tracking directly). The trade-offs between importing from GA4 and using the Ads tag are covered in our guide to Google Ads conversion tracking with GTM.
Which key events does a small business site need?
Start with the actions that mean someone wants to buy or talk to you. For most Indian small business sites, that is three events.
| Event name | Fires when | Trigger idea in GTM | Mark as key event? |
|---|---|---|---|
| generate_lead | A form is successfully submitted | Thank-you page view, or the form plugin's success event | Yes |
| whatsapp_click | Someone clicks a WhatsApp button or wa.me link | Click URL contains 'wa.me' or 'api.whatsapp.com' | Yes |
| call_click | Someone taps a phone number | Click URL starts with 'tel:' | Yes |
| file_download (optional) | Brochure or price list download | Usually no GTM tag needed: GA4's enhanced measurement collects file_download automatically when it is switched on | Usually no; track, but do not optimise on it |
generate_lead is one of Google's recommended event names, which helps GA4 reports recognise it. The other two are custom names; keep them lowercase with underscores and use the same names everywhere, including in your Meta setup from our Meta Pixel and Conversions API guide.
Say you run a CA firm in Janakpuri. Most enquiries come by WhatsApp and phone, a few through the contact form. Without whatsapp_click and call_click, GA4 would suggest your site produces almost no leads.
How do you set up GA4 with Google Tag Manager?
Install GTM once, load the Google tag through it, and then add one GA4 event tag per action. This keeps all tracking in one place you can edit without touching site code again.
- Create a GA4 property and a web data stream for your site. Copy the Measurement ID (it starts with G-).
- Create a GTM container and add its two code snippets to every page, or use your CMS's GTM plugin or setting. Remove any GA4 code pasted directly in the theme so data is not counted twice.
- In GTM, add a Google tag with your Measurement ID, triggered on all pages.
- Turn on the built-in Click variables (Click URL, Click Text) under Variables.
- Create a trigger 'WhatsApp click': Click – Just Links, firing on some link clicks where Click URL contains wa.me.
- Create a GA4 Event tag named whatsapp_click using that trigger. Repeat for call_click (Click URL starts with tel:).
- For forms, the cleanest trigger is a Page View on the thank-you page URL. If your form has no thank-you page, ask whoever built the site to push a dataLayer event on success, or use the form plugin's own integration.
- Do not publish yet. Test first.
How do you test GA4 events with DebugView?
Use GTM's Preview mode to confirm the tag fires once, then GA4's DebugView to confirm the event arrives with the right name. Both are free and take a few minutes.
- In GTM, click Preview and enter your site URL. A Tag Assistant window opens alongside your site.
- On your site, click the WhatsApp button, tap the phone number and submit a test form.
- In Tag Assistant, check that each tag shows as fired exactly once on the right action, and not on page load.
- In GA4, open Admin, then DebugView. Your device should appear with the events arriving in a timeline within seconds.
- Click an event to check parameters such as page location.
- If everything looks right, go back to GTM and click Submit to publish the container with a clear version name like 'Lead events v1'.
How do you mark events as key events in GA4?
Once an event has been received, go to Admin, then Data display, then Events, and toggle 'Mark as key event' for it. You can also create the key event in advance by typing the exact event name under Key events.
- New events can take up to a day to appear in standard reports, even though DebugView shows them instantly.
- Key event counting can be once per event or once per session. For leads, once per session avoids counting a nervous double-submit as two leads; check the current setting options in your property.
- Only mark real business outcomes. Marking scrolls or page views as key events makes your 'conversion rate' meaningless.
- Menu names in GA4 change from time to time. Google's Analytics Help Centre is the reference if your screens differ.
How do you send GA4 key events to Google Ads?
Link GA4 to Google Ads, then import the key events you want to optimise for as conversions. Import only the ones that represent real leads or sales, and set one as primary so bidding focuses on it.
- In GA4 Admin, open Product links and link your Google Ads account. You need admin access on both.
- In Google Ads, go to Goals, then Conversions, and choose to import from Google Analytics 4.
- Select generate_lead, whatsapp_click and call_click, or whichever you actually use.
- Mark the strongest one (usually generate_lead) as a primary action, and the others as primary or secondary depending on how much you trust them as signals of a real enquiry.
- Wait a day or two, then confirm the conversions appear in Google Ads with recent activity. If they do not, compare the dates against DebugView.
- Avoid tracking the same action twice, once imported from GA4 and once from a Google Ads tag, both set as primary. Bidding would then count each lead twice.
Worked example: a filled event plan for a CA firm site
Writing the plan down before you open GTM saves hours of guessing later. Here is a filled version for the Janakpuri CA firm scenario. Copy the format for your own site.
| Action | GA4 event name | GTM trigger | Key event | Import to Google Ads |
|---|---|---|---|---|
| Contact form submitted | generate_lead | Page View, Page Path equals /thank-you/ | Yes | Yes, primary |
| WhatsApp button clicked | whatsapp_click | Link click, Click URL contains wa.me | Yes | Yes, secondary at first; promote to primary once clicks match real chats |
| Phone number tapped | call_click | Link click, Click URL starts with tel: | Yes | Yes, secondary |
| Fee brochure downloaded | file_download (automatic) | None needed if enhanced measurement is on | No | No |
| GST services page viewed | page_view (automatic) | None needed | No | No; use as an audience instead |
Share the plan with whoever manages the website, so a redesign does not silently break the thank-you page or the WhatsApp link that your tracking depends on.
Mistakes marketers make with GA4 key events
- Tracking the contact page view as a lead. Visiting the page is not submitting the form.
- Having GA4 installed twice, once in the theme and once through GTM, which doubles every event.
- Different event names in different tools (Lead, lead_submit, generate_lead), which makes reporting messy.
- Never testing on mobile, where WhatsApp links often behave differently.
- Building dashboards before the events are verified. Once they are, a simple Looker Studio ads report can show key events next to ad spend.
Measurement is the foundation of performance marketing: without trustworthy key events, every optimisation decision is a guess. GA4 and GTM setup on a live site is one of the practical modules in our Advanced Digital Marketing & Performance Ads course.
Frequently asked questions
Are GA4 key events the same as conversions?
Key events are what GA4 used to call conversions. Conversions now refers to actions counted in Google Ads, often imported from GA4 key events.
Do I need Google Tag Manager to set up GA4 key events?
No, you can create events in GA4 itself or add code directly. GTM makes it much easier to track clicks and forms and change tracking later without editing site code.
Why are my GA4 key events not showing in reports?
Standard reports can take up to a day to update. If the event also does not appear in DebugView, the tag is not firing; check it in GTM Preview.
How do I track form submissions in GA4?
The most reliable method for beginners is a thank-you page after submission, tracked as a generate_lead event. GA4's automatic form tracking exists but can misfire on many form types, so test it before relying on it.
Can I track WhatsApp clicks in GA4?
Yes. Create a GTM trigger for link clicks where the URL contains wa.me or api.whatsapp.com and send a whatsapp_click event to GA4.
Keep reading in Meta and Google Ads
- What Is Performance Marketing? A Practical Guide for India Start here
- How to Build a Looker Studio Report for Google Ads and Meta Ads
- Facebook Ad Creative Testing on a Small Indian Budget
- ROAS Calculation Explained: Break-Even ROAS, CPL and CPA in ₹
- Google Ads Conversion Tracking with Tag Manager: Forms, Calls, WhatsApp
Related: Advanced Digital Marketing & Performance Ads · Google Ads Conversion Tracking with Tag Manager: Forms, Calls, WhatsApp · All guides in Meta and Google Ads