You are spending real money and real hours bringing people to your website — running Google Ads, writing blog posts, posting on Instagram. Then you open Google Analytics 4 to see what actually worked, and you meet a wall of events: page_view, scroll, session_start. Nothing there says "this person asked about a course" or "this person signed up". That gap is exactly what GA4 event tracking closes. Done properly, it turns raw clicks into named, countable actions — a course enquiry, a form submission, a sign-up — so you can finally see which campaign fills your enquiry pipeline and which just burns budget. This guide shows you how, step by step, with no guesswork and no code you cannot copy.
What GA4 event tracking actually means
The first thing to understand about Google Analytics 4 is that everything is an event. In the old Universal Analytics world you had pageviews, sessions, and separate "events" bolted on the side. GA4 threw that out. A pageview is an event. A scroll is an event. A video play, a file download, a form submission — all events. This single model is why GA4 feels unfamiliar at first, and it is also why it is so powerful once it clicks.
But not every event matters equally. Measuring a scroll is interesting; measuring a course enquiry is the whole point. GA4 lets you flag the events that represent real business outcomes. These used to be called "conversions". In 2024 Google renamed them key events, and reserved the word "conversion" for Google Ads. If you marked anything as a conversion before the change, it quietly became a key event in your property — nothing was lost, only relabelled.
So GA4 event tracking is really two jobs stacked together. First, make sure the action you care about is being captured as an event. Second, tell GA4 that this particular event is a key event so it shows up in the reports, columns, and audiences that drive decisions. Skip the second job and your enquiries sit buried among scrolls and pageviews, invisible to the one report your boss actually reads.
Getting this foundation right is the difference between a dashboard you trust and a dashboard you ignore. If you would rather learn it in a structured sequence than piece it together from scattered videos, a hands-on digital marketing course walks you through analytics, tracking, and campaign measurement end to end.
The four ways GA4 collects events
Before you add a single line of tracking, it helps to know what GA4 already captures on its own. Events reach your property through four channels, and two of them need no work from you at all. Knowing which is which stops you from rebuilding something Google gives you for free.
Only two of GA4’s four event layers need your hands-on setup
Source: Google Analytics Help, events documentation, 2026.
Automatic and enhanced measurement — the free layers
Automatically collected events like page_view and session_start fire the moment GA4 is installed. Enhanced measurement sits one toggle above them: switch it on in your data stream settings and GA4 starts logging scrolls, outbound clicks, site searches, file downloads, video engagement, and a generic form_submit. For many small sites this already captures 80% of behaviour.
Recommended and custom events — the layers you build
Here is the catch. Enhanced measurement knows a form was submitted; it does not know it was a course enquiry. For meaningful outcomes you use recommended events — a list of standard names Google publishes, such as generate_lead for a lead form and sign_up for account creation. These are not sent automatically; you implement them yourself, but you use Google’s exact spelling so your data unlocks current and future reporting features. Anything Google has no name for becomes a custom event with a name you invent.
Each event can also carry parameters — small pieces of context sent alongside it. A generate_lead event can include which course the enquiry was about, the form’s location on the page, or an estimated value. Parameters are what let you later ask sharper questions: not just "how many leads", but "how many leads for the stock-market course from the pricing page". You do not need them on day one, but designing a couple of sensible parameters early saves a rebuild later. The rule of thumb: get the event name right first, add parameters once the basic count is trustworthy.
How to track a course enquiry and a sign-up
Now the practical part. Say you want to measure two outcomes: someone submitting the "Request a callback" form (an enquiry) and someone creating an account on your portal (a sign-up). Here is the full path from raw click to a number you can report on.
Each step of an enquiry maps to one named GA4 event
Source: Google recommended events (generate_lead, sign_up), 2026.
Step 1 — Decide the exact action that counts. Not "someone visited the contact page", but "someone successfully submitted the form and saw the thank-you message". A precise definition keeps your numbers honest.
Step 2 — Fire the event. You have two clean routes. If your site uses Google Tag Manager, you create a trigger (for example, a thank-you page view or a form-submission trigger) and a GA4 event tag named generate_lead. No developer needed. We explain the whole tool in our guide to what Google Tag Manager is and why marketers use it. If you prefer code, you call gtag('event', 'generate_lead') on the confirmation action. Either way, use Google’s spelling exactly.
Step 3 — Mark it as a key event. In GA4 go to Admin, then Data display, then Events. Find generate_lead in the list and switch on the "Mark as key event" toggle. Repeat for sign_up. When you mark it, GA4 asks for a counting method — "once per event" or "once per session"; for leads, once per event is usually right.
Step 4 — Verify before you trust it. Open DebugView or the Realtime report, complete the form on your own site, and watch the event appear. If it fires, you are done. If it does not, your trigger or tag name is wrong — fix it before a month of data goes missing.
Want to set this up with confidence, not trial and error?
NIFM’s digital marketing programme covers GA4, Tag Manager, and campaign measurement with guided, hands-on projects — delivered in Hindi and English, at your own pace, with a certificate on passing the course exam.
Explore the digital marketing training courses →form_submit vs generate_lead: which should you use?
This is where most beginners trip. Enhanced measurement already gives you a form_submit event, so why bother with generate_lead? Because they answer different questions. form_submit fires on any form on your site — newsletter boxes, search bars, login fields, and your enquiry form all look identical to it. generate_lead is the name you attach to the one submission that means a real business lead.
| Question | form_submit (enhanced measurement) | generate_lead (recommended) |
|---|---|---|
| How it is set up | ✓ Automatic, one toggle | ✗ You implement it |
| What it measures | Any form on the site | Only the submission you define as a lead |
| Precision for reporting | Low — noisy, mixes form types | High — one clean outcome |
| Best use | A quick sanity check that forms work | The key event you optimise campaigns against |
The practical answer: keep enhanced measurement on so you never miss a form, but build generate_lead as the event you actually mark as a key event and report on. Think of form_submit as a smoke alarm and generate_lead as the meter that bills your campaigns.
Five mistakes that quietly break GA4 event tracking
GA4 rarely throws an error when tracking is wrong. It simply records nothing, or records the wrong thing, and you only notice when the numbers look impossible. These are the five traps that catch most marketers.
- Getting the spelling wrong. Event names are case-sensitive. generate_lead and Generate_Lead are two different events to GA4, and only the exact lowercase spelling unlocks Google’s built-in lead reporting. Copy the name, never retype it.
- Double-counting the same action. If you mark both a filtered form_submit and generate_lead as key events for one enquiry, every lead counts twice and your conversion rate doubles on paper. Pick one event per outcome.
- Expecting it to work backwards. Marking an event as a key event applies only going forward. GA4 does not reprocess history, so last month’s enquiries will not suddenly appear in the key-events column. Set it up before the campaign, not after.
- Hitting the key-event ceiling. A standard property allows up to 30 key events. If you mark every tiny interaction, you crowd out the handful that truly matter. Reserve key-event status for genuine outcomes — enquiries, sign-ups, purchases.
- Never checking DebugView. The single most common reason a lead number reads zero is that the event was never verified live. Thirty seconds in DebugView or Realtime saves weeks of missing data.
Fix these five and your GA4 event tracking will hold up to scrutiny — which matters the moment someone asks why the ad spend is worth it.
What to do next
GA4 event tracking is not really an analytics skill; it is a measurement habit. You decide the actions that represent value, you capture each one as a cleanly named event, you promote the important ones to key events, and you verify every single one before you trust the report. Do that, and the wall of events becomes a clear line from campaign to enquiry to enrolment.
Once the leads are flowing in as data, the next question is which ones are worth chasing first — that is where lead scoring for education enquiries takes over. And to actually read the numbers your events produce, see our walkthrough of the GA4 reports that matter. Measurement, reporting, and action are three parts of one loop.
Learn GA4 and campaign measurement the structured way
Trusted by 50,000+ learners since 2012 · Hindi + English · Learn at your own pace
Start the digital marketing trainingFrequently Asked Questions
What is the difference between an event and a key event in GA4?
Every interaction in GA4 is an event — a pageview, a scroll, a form submission. A key event is an event you have flagged as a business outcome, such as a course enquiry or a sign-up. The flag tells GA4 to surface it in the reports, columns, and audiences you use to judge campaigns. Key events are what Google used to call "conversions" before the 2024 rename.
Do I need code to set up GA4 event tracking?
Not necessarily. If you use Google Tag Manager, you can create triggers and GA4 event tags entirely in its visual interface, with no developer. Direct code using the gtag function is an option if you prefer it or your setup needs it, but most marketers handle course-enquiry and sign-up tracking through Tag Manager alone.
Which GA4 event should I use for a course enquiry form?
Use Google’s recommended event name generate_lead, spelled exactly in lowercase. It is the standard name for a form submission that produces a lead, and using it unlocks GA4’s built-in lead-generation reporting. For an account creation, use sign_up. Mark both as key events in Admin so they appear in your reports.
Why is my GA4 key event showing zero after I set it up?
The usual causes are a misspelled event name, a trigger that never fires, or the fact that marking a key event only counts data from that point forward — it is never retroactive. Open DebugView or the Realtime report, perform the action yourself, and confirm the event appears. Key-event totals in standard reports can also take roughly a day to finalise.
How many key events can I track in GA4?
A standard GA4 property lets you designate up to 30 key events; the 360 version allows more. Because the limit is modest, reserve key-event status for genuine outcomes like enquiries, sign-ups, and purchases, and leave minor interactions as ordinary events you can still analyse without promoting them.
Can I use GA4 event tracking data in Google Ads?
Yes. Once an event like generate_lead is marked as a key event in GA4, you can import it into Google Ads as a conversion and optimise your bidding towards it. This is one reason the exact, standard event name matters so much — it keeps your analytics and your ad platform speaking the same language, so the lead you count in GA4 is the same lead Google Ads learns to find more of.
Is GA4 event tracking the same as the old Universal Analytics goals?
No, and the difference trips up anyone migrating. Universal Analytics used "goals" built on pageviews and separate event categories. GA4 has no goals — it has events, and the important ones become key events. There is no direct one-to-one copy, so treat a migration as a chance to redefine what truly counts as an outcome rather than porting old goals mechanically.






-–-full-preparation-strategy-for-high-marks.png)


.jpg)




-%E2%80%93-full-preparation-strategy-for-high-marks.png)


.jpg)










.jpg)


