Examples of custom events highlighted in AG4
Posted: Wed Jan 22, 2025 8:15 am
Most of these events work as expected, but some users have reported data issues with form interaction events. In the next section, we'll cover how to create a custom event to track a form submission so you can make sure you record this important interaction.
Recommended Events
Unlike automatically collected events and enhanced measurement events, recommended events require you to do the setup work.
For these events, Google recommends a specific event name job seekers data and parameters to use, and you do the rest.
E-commerce events such as add_to_cart, begin_checkout, and purchase are all recommended events.
Here's an example for the add_to_cart event from Google's documentation . Google recommends the specific event name (add_to_cart) and event parameters to use, but you'll have to worry about the implementation.
Parameters explained in Google's documentation for the "add_to_cart" event.
Custom Events
Custom events also require custom setup work. Unlike recommended events, Google does not provide recommended names for custom events.
The technical name for the second group is "custom events". These events will be relevant for some sites but not for others. The list of events below shows four custom events specific to this website.
The cookie_consent_visible event event is fired when a cookie consent banner is displayed.
The cookie_consent_accept event fires when the banner is accepted and not closed or dismissed.
The 10min_70scroll event fires when a visitor spends 10 minutes on a single page and scrolls at least 70% of the page length.
The youtube_any_click event fires on external links that lead to the associated YouTube channel.
Remember that while these interactions are essential for this particular website example, they may not be necessary for other sites - that's why they're "personalized."
Recommended Events
Unlike automatically collected events and enhanced measurement events, recommended events require you to do the setup work.
For these events, Google recommends a specific event name job seekers data and parameters to use, and you do the rest.
E-commerce events such as add_to_cart, begin_checkout, and purchase are all recommended events.
Here's an example for the add_to_cart event from Google's documentation . Google recommends the specific event name (add_to_cart) and event parameters to use, but you'll have to worry about the implementation.
Parameters explained in Google's documentation for the "add_to_cart" event.
Custom Events
Custom events also require custom setup work. Unlike recommended events, Google does not provide recommended names for custom events.
The technical name for the second group is "custom events". These events will be relevant for some sites but not for others. The list of events below shows four custom events specific to this website.
The cookie_consent_visible event event is fired when a cookie consent banner is displayed.
The cookie_consent_accept event fires when the banner is accepted and not closed or dismissed.
The 10min_70scroll event fires when a visitor spends 10 minutes on a single page and scrolls at least 70% of the page length.
The youtube_any_click event fires on external links that lead to the associated YouTube channel.
Remember that while these interactions are essential for this particular website example, they may not be necessary for other sites - that's why they're "personalized."