Skip to content

Google event delivery

Settings → Google → Events shows the health of everything you configured on the Ads and GA4 tabs: how many events are sending, how many are failing, and why.

What’s on this tab

Section titled “What’s on this tab”
  • KPI strip: total events sent and failed to Google Ads and GA4 combined, over your selected time window.
  • Event delivery table: a breakdown by event name and outcome, so you can see which events (Purchase, Add to Cart, and so on) are actually moving and which aren’t.
  • Recent failures: the latest failed sends, plus the most common failure reasons over the window, for both destinations together.

This tab is a read-only view of delivery health. To change which events send or how, use the Ads and GA4 tabs.

Per-event configuration

Section titled “Per-event configuration”

Which events send, and how, is configured per destination:

  • Google Ads: turn individual conversions on or off from the Ads tab’s conversion tables, see the full event list.
  • GA4: choose off, browser, server, or (Purchase only) both, per event, from the GA4 tab’s Events table.

Client vs. server-side sending, and deduplication

Section titled “Client vs. server-side sending, and deduplication”
  • Google Ads conversions are sent automatically once you turn an event on, there’s no separate client/server choice to make for Ads.
  • GA4 events give you an explicit choice per event: sent from the browser (the storefront tag), from Máximo’s servers, or (for Purchase only) both. GA4 deduplicates Purchase by transaction_id, so sending it both ways doesn’t double-count it. No other GA4 event can safely be sent both ways, since GA4 has no deduplication for anything else.

Verifying events are arriving

Section titled “Verifying events are arriving”

To confirm events are actually reaching Google:

  1. Check the event delivery table on this tab for the event you expect, a growing count under “Sent” means it’s arriving.
  2. If an event shows failures, open Delivery monitor and filter to Google Ads or GA4 for the full failure detail, including the request and response Google returned.
  3. Check Pixel presence to confirm the Google tag is actually loading on your storefront, a missing or blocked tag is a common reason browser-side events stop arriving even though nothing on this tab shows an error.

Next steps

Section titled “Next steps”
  • Delivery monitor: full failure detail across every destination.
  • Pixel presence: whether the Google tag is actually loading and firing on your storefront.