You will create the events from your plan, mark them as key events, and prove they fire correctly.
The first time Priya checked her new key events, the report said her site had produced 41 enquiries in a week. Her inbox had 19. The number looked great and was wrong, because the thank-you page was firing the event twice: once from the website builder's own GA4 integration and once from a tag she had added in Tag Manager. She had set it up carefully and never watched it fire.
This exercise is the watching part. You create the events from your list in lesson 3.3, mark them as key events, and prove each one fires once for each real action. You finish with a tracking log that anyone who inherits the setup can read.
Work through your list from lesson 3.3 one line at a time.
For a thank-you page, use the create event option in GA4's admin settings, under events. Give the new event a name such as generate_lead, and set the matching conditions so it is created whenever a page_view event happens on a page whose address contains /thank-you. Copy the exact path from your site, since a small difference like /thankyou will match nothing. Add the value and currency parameters here if you are giving the event a value.
For a click, such as Priya's WhatsApp button, use Google Tag Manager. Create a trigger for link clicks where the click URL contains the WhatsApp link address your button uses. Then create a GA4 event tag named whatsapp_click that fires on that trigger. Preview the container before you publish it.
For a booking tool or form tool that sends its own events to GA4, read its help page to find the exact event name it uses, so you mark the right one.
Created events only apply to data from the moment they exist. They do not rewrite last month.
In the admin settings, open key events and add each event name you want counted as a result. You can add a name before the event has happened for the first time, which saves waiting. Priya added generate_lead, whatsapp_click and her booking event.
Mark only the events from your plan. A list of fifteen key events is as unhelpful as a report with forty charts.
Now test in real time, because the standard reports can take a day or more to show new events.
Open Tag Assistant from Google, connect it to your website, and your browser tab goes into debug mode. Then open DebugView in GA4's admin settings. DebugView shows a live stream of events from browsers in debug mode, one by one, with their parameters. Tag Assistant shows which tags fired on each page and what they sent.
Click through your site as a visitor would. For each key event, do the real action. Priya sent the enquiry form with "TEST" in the message, tapped the WhatsApp button, and booked a trial class under a test name, then told her admin to ignore and delete those entries. If your internal traffic filter from lesson 3.2 is active and your test visits do not appear, switch to your phone on mobile data.
For each action, check three things in DebugView:
The event appears with the name you expect, spelled exactly as in your plan. It appears once. Two identical events a second apart usually mean the tag is installed twice, as in Priya's case. Its parameters are there, including value and currency if you set them.
Also check the opposite case. Load the enquiry page without sending the form, or press send with a required field empty, and confirm that no key event fires. An event that fires on failure will inflate every report.
When the event fires once with the right details, take a screenshot of DebugView or Tag Assistant showing it. That screenshot is your proof.
Priya's double count came from two installations of GA4. She switched off the builder's integration, kept Tag Manager, published the change and repeated the test. One event per enquiry. Other common faults: a trigger that matches too many links, a thank-you path that differs from what you typed, or a form tool that shows its success message without changing the page, so a page-based event never fires.
Fix one thing at a time and retest after each change. After a day or two, check the standard events report as well, and compare the count of generate_lead with the enquiries that really arrived over the same days.
The last step is a short document. Priya's tracking log is a sheet with these columns: event name, key event (yes or no), what triggers it, where it is set up (GA4 admin, Tag Manager or the website builder), value and how it was estimated, date tested, tested by, and a link to the screenshot.
Her finished log has three rows and took fifteen minutes to write. It would take the next person a day to work out the same things from scratch. When a website redesign breaks tracking next year, as redesigns often do, the log tells whoever fixes it exactly what to rebuild and how to check it.
Once your own events fire cleanly and the log is written, you have the GA4 setup that every later module relies on, starting with the reports in module 4.
Produce a tracking log listing each key event, how it fires and a screenshot from DebugView or Tag Assistant proving it fired once.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).