GA4 Events and Conversions

GA4 events are the actions Google Analytics 4 records on a website or app, such as a page view, a scroll, a form submit or a purchase. Every piece of data in GA4 is an event with details attached, called parameters. You then mark the events that matter to the business as key events.

• Automatic events: Sent by the Google tag with no setup, such as first_visit and session_start.
• Enhanced measurement: A switch in the data stream that adds scrolls, outbound clicks, file downloads and form interactions.
• Recommended events: Names Google defines for common actions, such as generate_lead, sign_up and purchase.
• Custom events: Names you choose when nothing else fits, such as book_demo_class.
• Key events: The few events you mark as business results, used in reports and imported into ads.

This tutorial follows one example: a coaching institute in Lucknow that prepares students for bank exams. Its website has course pages, a fee page, a syllabus PDF, a WhatsApp button and a form to book a demo class. The owner wants to know which ads and posts bring students who actually book a demo.

Prerequisites for Setting Up GA4 Events

• A working GA4 property: The Google tag must already be on every page, as shown in the GA4 tutorial.
• Editor access: You need the Editor role on the property to create events and mark key events.
• A list of actions: Write down every action on the site that shows interest, from reading the fee page to submitting the form.
• A way to send events: Either access to the site code or a Google Tag Manager container.

Setup: Plan Your GA4 Events Before You Build

Planning first stops messy data. Make a simple sheet with four columns: the action, the event name, the parameters, and whether it is a key event.

Follow these naming rules for every event you create:

• Lowercase with underscores: Use whatsapp_click, not WhatsApp Click. Event names are case sensitive, so two spellings become two events.
• Short and clear: Keep names within GA4's length limit.
• No reserved names: Do not start names with google_, ga_ or firebase_, which GA4 keeps for itself.
• Recommended first: Check Google's list of recommended events before inventing a name.

Step-by-Step: Set Up GA4 Events for the Institute

Step 1: Check the Automatic Events

Open Reports > Engagement > Events. You should already see page_view, session_start, first_visit and user_engagement. If they are missing, the tag is not working, so fix that first.

Step 2: Review Enhanced Measurement

Go to Admin > Data streams, open the web stream, and select the gear icon on Enhanced measurement. Each switch controls one group of events: page views, scrolls, outbound clicks, site search, video engagement, file downloads and form interactions.

• Keep scrolls and file downloads on: The institute learns who reads the whole fee page and who downloads the syllabus.
• Watch form interactions: The automatic form events can fire on forms that are not lead forms, such as a newsletter box. If they add noise, switch them off and send your own lead event instead.

Step 3: Send a Recommended Event for the Lead Form

When the demo class form is submitted, the site should send the recommended generate_lead event with useful parameters. A developer can add it to the success step of the form:

gtag("event", "generate_lead", {
  form_name: "demo_class",
  course_name: "ibps_po",
  value: 0,
  currency: "INR"
});

• form_name: Tells demo forms apart from other forms on the site.
• course_name: Records which course the student asked about.
• value and currency: Optional for leads. Set a value only if the business agrees on what a lead is worth.

If the site uses Google Tag Manager, push the same details to the dataLayer and let a GA4 event tag send them. That route is covered in the Google Tag Manager tutorial.

Step 4: Create a Custom Event Without Code

The WhatsApp button opens a wa.me link, which enhanced measurement records as an outbound click. To give it its own name, go to Admin > Events > Create event and add a rule: create whatsapp_click when event_name equals click and link_url contains wa.me.

This method copies an existing event under a new name. It cannot record an action that GA4 never saw, so check the source event exists first.

Step 5: Register Custom Parameters

Go to Admin > Data display > Custom definitions and create a custom dimension for course_name and form_name, with the scope set to Event. Without this step the parameters are collected but do not appear in standard reports.

Step 6: Test in DebugView

Install Google's Tag Assistant or use GTM preview mode, then open Admin > DebugView. Submit a test demo form and confirm that generate_lead arrives with course_name and form_name.

Step 7: Mark GA4 Key Events

Once an event has arrived at least once, go to Admin > Data display > Events and turn on Mark as key event for generate_lead. Do the same for book_demo_class, sent by the booking calendar when a student picks a demo slot, once it starts arriving.

• Keep the list short: Mark only events that mean real business progress. Marking scrolls as key events makes every report look better than the business is doing.
• Link to Google Ads: Key events can be imported into Google Ads to guide bidding, explained in Google Ads conversion tracking.

Step 8: Read the Results

After a day or two, open Reports > Engagement > Key events and Reports > Acquisition > Traffic acquisition. Add the key event column to see which source and medium brings demo bookings, not just visits.

Common Mistakes with GA4 Events

• Two names for one action: DemoForm and demo_form become two events. Agree on one naming sheet and stick to it.
• Duplicate firing: The same lead sent by site code and by GTM counts twice. Send each event from one place only.
• Too many key events: A key event for every click makes the key event rate meaningless.
• Unregistered parameters: Forgetting custom dimensions means waiting weeks for data you thought you had.
• Personal data in parameters: Never send a student's name, phone number or email address as a parameter. Google's policies forbid it.
• Testing on the live property only: Use DebugView and filter out internal traffic, so staff tests do not look like real leads.

Next Steps

• Heatmaps: See where students tap and hesitate on the fee page with Microsoft Clarity heatmaps.
• Raw data: Export every event to BigQuery for your own analysis with the GA4 BigQuery export.
• Predictions: With enough key events, GA4 can predict who is likely to act, explained in GA4 predictive metrics.

How AI Changes GA4 Event Tracking

What AI Automates Now

AI assistants can draft a tracking plan from a list of pages, suggest recommended event names, and write the gtag or dataLayer code for a developer to review. GA4 also uses machine learning on your events to flag unusual changes as insights.

What Still Needs a Human

Deciding which actions count as business progress is a human call. Only the owner knows that a booked demo slot matters far more than a PDF download. A person must also test each event in DebugView before trusting it.

Risk to Watch

AI tools sometimes invent event names or parameters that GA4 does not recognise, or confuse older analytics code with gtag.js. Always check generated code against Google's current developer documentation before it goes live.

Do It with AI

Use this prompt to turn a list of site actions into a first GA4 tracking plan. It works in ChatGPT, Claude or Gemini.

1. List every page and action on your site in plain words.
2. Run the prompt and compare its event names with Google's recommended events list.
3. Build the events, then test each one in DebugView.
4. Mark only the agreed events as key events and review them after a week.

Check Before You Use It

• Facts: Confirm every recommended event name and parameter in Google's documentation; AI tools can get them wrong.
• Brand fit: Make sure the key events match what the business actually counts as success.
• Compliance: Keep personal data out of every event and follow the site's consent setup.