--- title: "How to Track Google Analytics 4 Events With WordPress?" url: https://nexterwp.com/docs/track-google-analytics-events-with-wordpress/ date: 2023-07-01 modified: 2026-09-28 lang: en author: "Aditya Sharma" description: "GA4 has a list of recommended event names — sign_up, login, purchase and the rest. Using them rather than inventing your own is what lets GA4's built-in reports understand your..." image: https://nexterwp.com/wp-content/uploads/2024/05/track-google-analytics-events-with-wordpress-1024x519.jpg word_count: 693 --- # How to Track Google Analytics 4 Events With WordPress? ## Key Takeaways - Nexter Blocks Event Tracking extension tracks GA4 events on WordPress websites for actions like button clicks, form submissions, and video plays. - Google Measurement id is added in Nexter → Extra Options → Settings by enabling Add Event Tracking ID and entering the ID in the GA4 ID field. - Nexter Blocks button blocks support Advanced > Event Tracking, where the Google Analytics toggle turns on Recommended or Custom event types. - Google Analytics 4 can take up to 24 hrs to show events, and Admin > DebugView shows events live with custom properties after using the Google Analytics Debugger Chrome extension. GA4 has a list of recommended event names — `sign_up`, `login`, `purchase` and the rest. Using them rather than inventing your own is what lets GA4's built-in reports understand your data. This block sends one of those events when someone interacts with it. *For every Event Tracking setting in one place, see the [event tracking guide](https://nexterwp.com/docs/add-event-tracking-in-wordpress/).* [LIVE BLOCK LINK](https://nexterwp.com/nexter-blocks/extras/wordpress-ga4-event-conversion-tracker/) ## Before You Start - **Edition:** **Pro** — event tracking needs Nexter Blocks Pro.- **Block to enable:** Event Tracking, switched on under **Nexter > Blocks** in your WordPress dashboard.- **A GA4 measurement ID** (it starts with `G-`), entered in Nexter's settings.- **Event tracking switched on** in those settings. > *Save the event tracking setting as enabled before configuring the block. Measured: with it never saved, the editor still offers the options but the published page carries no tracking markup.* ## Steps - Enter your **GA4 measurement ID** in Nexter's settings. ![Entering the GA4 measurement ID](https://nexterwp.com/wp-content/uploads/2023/07/google-measurement-id-1.webp) - Switch **event tracking** on. ![Enabling event tracking](https://nexterwp.com/wp-content/uploads/2023/07/google-measurement-id-2-1.webp) - Select your block and open the **Advanced** tab. ![The Advanced tab](https://nexterwp.com/wp-content/uploads/2023/07/google-measurement-id-3.webp) - Turn on **Google** and leave the event type on **recommended**. ![Choosing Google as the provider](https://nexterwp.com/wp-content/uploads/2023/07/google-measurement-id-4.webp) - Pick the recommended event that matches what the block does. ![Nexter Blocks editor, Advanced tab, Event Tracking panel with Google Analytics switched on, Event Type set to Recommended and Select Event set to Generate Lead](https://nexterwp.com/wp-content/uploads/2026/09/event-tracking-ga4-recommended-full.webp) - Add any custom properties you want sent with it. ![Event Tracking panel with Google Analytics on and a new row added under Event Properties](https://nexterwp.com/wp-content/uploads/2026/09/rs-ev-x-ga-property.webp) - Publish, then watch Google Analytics' realtime view while you click the block. ## How It Behaves - **Turn event tracking on in Nexter's settings first.** Measured: with the site-level setting unset, a block configured for both providers emitted **nothing** — no markup, no console message, no warning. With the setting enabled and nothing else changed, the same block immediately emitted its full tracking payload.- **The event name is sent exactly as chosen.** Read from the shipped script, a recommended event results in `gtag('event', , )`.- **The default event is `ad_impression`**, which is rarely what you want. Change it deliberately.- **Custom properties are merged into a single object** and passed with the event.- **A property with no name is dropped.** Measured: three properties with one unnamed produced two in the payload.- **The whole configuration is written onto the block.** Measured: the block gains a `tpgb-event-tracker` wrapper and an inner element carrying a `data-event-opt` attribute holding the providers, the event type and name, and any custom properties. You can confirm your setup reached the page by looking for that attribute.- **Only certain things inside the block fire an event.** Read from the shipped script, this is the complete list, all on click: any link, a video play button, and the submit button of Mailchimp, WPForms, Everest Forms or Contact Form 7. A block containing none of those is tracked in name only.- **Binding happens once, when the page loads.** Blocks added to the page later by AJAX are not picked up.- **Measured with Nexter Blocks Pro deactivated:** a fully configured block emits no tracking markup at all. Event tracking is Pro only and does not degrade. ## Limitations - **What this page verified, and what it did not.** The markup the block emits and the calls the script makes were measured. Whether an event *arrives* in your analytics account was not, and cannot be from the page source. Confirm arrival in the provider's own tools.- **Recommended event names are Google's, not this plugin's**, and Google changes the list independently. Check GA4's own documentation for what each one expects.- **Recommended events expect particular properties.** Sending `purchase` without the properties GA4 expects will record the event but not populate the reports that rely on it.- **Only links and a few form submit buttons fire it**, as listed above.- **Consent and ad-blocking tools stop gtag loading entirely**, in which case nothing is sent and the console says so.- **Pro only.** ## Troubleshooting ### Nothing appears in realtime Check the site-level event tracking setting first, then look in the browser console for `gtag is not defined`, which means the GA4 library never loaded. ### The event arrives but the report stays empty Recommended events only populate their reports when sent with the properties GA4 expects. Check Google's documentation for that specific event. ### I want a name that is not on the list Use a custom event instead. See [the custom Google events doc](https://nexterwp.com/docs/track-custom-google-analytics-events-in-wordpress/). ### Which block is the event coming from? Add a custom property naming the block or the section. Properties are sent with every Google event. ## Related Docs - [Track custom Google Analytics events](https://nexterwp.com/docs/track-custom-google-analytics-events-in-wordpress/)- [Add event tracking in WordPress](https://nexterwp.com/docs/add-event-tracking-in-wordpress/)- [Track Facebook pixel events](https://nexterwp.com/docs/track-facebook-pixel-events-in-wordpress/)- [Track custom Facebook events](https://nexterwp.com/docs/track-custom-facebook-events-in-wordpress/)- [Advanced tab settings](https://nexterwp.com/docs/use-advanced-tab-in-nexter-blocks/) ## Frequently Asked Questions **Q: Why isn’t GA4 showing my event in realtime after I publish the page?** A: The first thing to check is the site-level event tracking setting in Nexter, because the block sends nothing if that setting is not enabled and saved. The page also notes that a browser console message like gtag is not defined means the GA4 library never loaded. In practice, that points to a setup problem before the block itself, not a bad event choice. **Q: What do I need before I can track Google Analytics 4 events with WordPress?** A: Nexter Blocks Pro is required, along with a GA4 measurement ID that starts with G- and event tracking enabled in Nexter’s settings. The block-level options only work after the site-level setting is saved, which matters because the editor can still show options even when the published page carries no tracking markup. That saved setting is what makes the tracking payload reach the page. **Q: Which WordPress blocks can actually fire a GA4 event?** A: Only a few things inside the block trigger an event on click: any link, a video play button, and the submit button of Mailchimp, WPForms, Everest Forms, or Contact Form 7. That means a block can be configured correctly but still never fire if it contains none of those elements. Nexter Blocks writes the tracking data onto the block, but interaction still depends on one of those supported targets. **Q: What’s the best way to choose a GA4 recommended event for a WordPress block?** A: Pick the recommended event that matches what the block actually does, because GA4’s built-in reports depend on using Google’s own event names and expected properties. The default event is ad_impression, which is rarely useful for most sites, so changing it deliberately matters. Nexter sends the chosen name exactly as selected, so the report logic in GA4 depends on that choice being accurate. **Q: Why does my GA4 event arrive but the report stays empty?** A: Recommended events only populate their reports when they are sent with the properties GA4 expects. The page uses purchase as the example: if you send purchase without its required properties, GA4 can record the event but still leave report sections empty. That usually means the event name is right but the payload is incomplete for Google’s reporting rules. **Q: How do I tell which block or section sent a GA4 event?** A: Add a custom property that names the block or section, because properties are sent with every Google event. Nexter merges custom properties into one object and passes them with the event, so this is the cleanest way to identify where an interaction came from later in analytics. It also helps when several blocks on one page use similar recommended events.