Most WordPress site owners who’ve installed Google Analytics 4 end up looking at the same three numbers: users, sessions, and page views. Those figures tell you how many people visited — but nothing about what they actually did while they were there.
That’s what event tracking is for. An event fires whenever a visitor takes a specific action: scrolling to the bottom of a post, clicking an outbound link, submitting a contact form, or downloading a file. Once you can see which actions visitors are taking — and on which pages — you have data you can actually use to improve the site.
GA4 already tracks many of these events automatically. Most WordPress sites are one settings toggle away from getting meaningful action data, with no code involved — form tracking is the one notable exception, and it’s worth knowing why before you rely on it.
The Short Version
GA4 automatically tracks scrolls, outbound link clicks, file downloads, and site search via Enhanced Measurement — enable this in Admin → Data Streams → your stream → Enhanced Measurement. To mark a specific action as a conversion, go to Admin → Events, find the event, and toggle Mark as conversion. For form submissions specifically, don’t rely on Enhanced Measurement’s built-in form event — use your form plugin’s own GA4 integration or Google Tag Manager instead, for reasons covered below.
Why Event Tracking Matters More Than Page Views
Page view data tells you traffic volume — it doesn’t tell you whether visitors are engaging, converting, or bouncing immediately. Two posts can have identical traffic numbers while one drives ten times more contact form submissions than the other. Without event tracking, you can’t see that.
The practical use case for most WordPress sites is knowing which pages drive form submissions, which CTA buttons get clicked, and which content gets downloaded. After setting this up on sites I’ve built, it consistently reveals that visitor behaviour doesn’t match what the owner assumed — usually a page they thought was underperforming is generating more enquiries than the one they were promoting.
If you haven’t yet installed GA4 on your site, see how to set up Google Analytics 4 in WordPress first — events won’t be recorded until the tracking code is in place. Google’s documentation on GA4 events outlines the categories available: automatically collected, enhanced measurement, recommended, and custom.
Setting It Up, Step by Step
Step 1 — Enable Enhanced Measurement
In GA4, go to Admin → Data Streams → your website stream → Enhanced Measurement and make sure the toggle is enabled. Within that section, individual event types can each be toggled independently: scroll, outbound clicks, file downloads, site search, video engagement, and — more recently — form interactions.
Scroll events fire when a visitor reaches 90% of the page. Outbound click events fire on any link leaving your domain. File download events fire on links to PDFs and similar file types. These require zero code and start appearing in GA4 immediately after you enable them. Form interactions were added to Enhanced Measurement more recently and can, in principle, fire form_start and form_submit events without any setup — but treat this one with more caution than the others (see Step 3).
Step 2 — Mark Events as Conversions
A conversion in GA4 is simply an event you’ve decided matters. To mark one, go to Admin → Events, find the event name in the list, and toggle Mark as conversion to on. Alternatively, go to Admin → Conversions → New conversion event and type the event name directly — useful for events that haven’t fired yet and don’t appear in the list.
Common events worth marking as conversions: form_submit, file_download, and for WooCommerce sites, purchase. Once marked, conversions appear in Reports → Life cycle → Acquisition and show which channels and landing pages are driving meaningful actions — not just visits.
Step 3 — Track Form Submissions Properly
Form submissions are the most commonly tracked conversion on WordPress sites, and also the one place Enhanced Measurement’s automatic tracking is worth being sceptical of. GA4’s built-in form-event detection has a real reputation for being unreliable — it can misfire on multi-step forms, AJAX-submitted forms (which most WordPress form plugins use), or forms embedded via iframe, all of which are common on WordPress. Rather than trust it, use your form plugin’s own direct GA4 integration where one exists.
Most major plugins have this built in. In WPForms, go to Settings → Integrations → Google Analytics and enable the event trigger. Fluent Forms has a similar option under its integrations settings. When enabled, a form-specific event fires in GA4 each time a form is submitted successfully — this is more reliable than Enhanced Measurement’s generic form detection, since the plugin knows exactly when a real, valid submission has gone through.
If your plugin doesn’t have native GA4 integration, the most reliable method is Google Tag Manager — see how to add Google Tag Manager to WordPress for the setup, then configure a Tag that fires on the form submission event from your plugin. Either way, if Enhanced Measurement’s form event is also enabled, disable it or make sure you’re not accidentally counting the same submission twice under two different event names.
Step 4 — Create a Custom Event Without Code
GA4 has a built-in event editor that lets you create new events by cloning and filtering existing ones. Go to Admin → Events → Create event and click Create.
Give the event a name, then set conditions based on an existing event. For example: clone a click event, add a condition matching the URL of your pricing page, and name the result pricing_page_click. This new event fires only when a visitor clicks a link while on that specific page.
This no-code method works well for isolating events by page, by link destination, or by element. For more complex tracking — interactions with specific elements, scroll depth thresholds, or multi-step funnel events — Google Tag Manager gives you more control and is worth setting up if you need it regularly.
Step 5 — Verify Events Are Firing
Before relying on your event data, confirm events are actually being recorded. GA4’s DebugView (Admin → DebugView) shows events in real time from your browser along with their parameters. Open your site, trigger the action you’re tracking, and watch for it to appear in DebugView within a few seconds — this is exactly how to catch a form event misfiring or not firing at all before it quietly skews a month of conversion data.
The Realtime report (Reports → Realtime) also shows live events but with less detail. Both are reliable for quick checks. Note that standard GA4 reports update on a 24–48 hour delay — DebugView and Realtime are the exceptions. Once events are confirmed and flowing, see how to read GA4 reports in WordPress to understand where conversion data appears and how to filter it by source, channel, and landing page.
Practical Tips
- Keep event names consistent and lowercase. GA4 treats
Form_Submitandform_submitas different events. Pick one format and stick to it across all your tracking. - Don’t mark every event as a conversion. Too many conversions make reports noisy and harder to interpret. Pick the two or three actions that genuinely indicate success for your site.
- Set up conversion tracking before running any paid campaigns. You need baseline data to know whether a campaign is actually changing visitor behaviour, not just adding traffic.
- If your form plugin and a GTM tag — or Enhanced Measurement’s own form event — are all sending events for the same action, you’ll get double-counted data. Pick one source and disable the rest.
Common Mistakes
Trusting Enhanced Measurement’s form tracking without verifying it. It’s convenient because it requires no setup, but on WordPress specifically — where most forms submit via AJAX rather than a standard page reload — it’s a common source of missed or duplicated events. Verify in DebugView before you trust a single number from it.
Marking events as conversions before verifying they fire. If the underlying event isn’t tracking reliably — wrong trigger, plugin conflict, caching issue — your conversion reports will be incomplete or misleading. Always verify in DebugView first.
Expecting real-time data in standard reports. GA4’s main Events and Conversion reports update on a 24–48 hour delay. If you just set up a new event and want to confirm it’s working, use DebugView — not the Events report.
Not filtering out internal traffic. If you or your team visit the site regularly, your own activity will show up in events and skew conversion data. In GA4, go to Admin → Data Filters and set up an internal traffic filter based on your IP address.
Once GA4 is installed and collecting data, the practical next step is setting up conversion tracking for your WordPress website — so you can see not just who visits, but which pages and traffic sources drive real enquiries and sales.
Conclusion
Start with Enhanced Measurement — it gives you scroll, outbound click, and file download data straight away with no code. For form submissions specifically, route through your form plugin’s own GA4 integration or Google Tag Manager rather than the built-in form event, and verify everything in DebugView before trusting it. Then mark your two or three most important events as conversions so your reports show what’s actually driving results. If you’re building out the analytics setup for a new site from scratch, the step-by-step guide to building a WordPress website covers tracking alongside every other foundational task.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.