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.
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.
- Switch event tracking on.
- Select your block and open the Advanced tab.
- Turn on Google and leave the event type on recommended.
- Pick the recommended event that matches what the block does.
- Add any custom properties you want sent with it.
- 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', <your event>, <properties>). - 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-trackerwrapper and an inner element carrying adata-event-optattribute 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
purchasewithout 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.
Which block is the event coming from?
Add a custom property naming the block or the section. Properties are sent with every Google event.
