Delivery monitor
Settings → Delivery monitor is the one place to check event-delivery health across every destination at once, Google Ads, GA4, Meta, TikTok, and Pinterest.
Overview
Section titled “Overview”The page shows, for the window you’re looking at:
- A health strip with one card per destination.
- An overall KPI row of events sent, failed, and skipped, for both the last 24 hours and the last 7 days.
- Failure groups: failures bucketed by destination, reason, and HTTP status, so repeated problems show up as one row instead of dozens.
- Skip reasons: a breakdown of events that were deliberately not sent, and why.
- A filterable, paginated failure list, with a detail view for any individual failure.
Per-destination health
Section titled “Per-destination health”Each destination’s card shows:
- A health badge, Healthy (95%+ of events sent successfully over the last 7 days), Degraded (80–95%), Critical (below 80%), or No data (nothing sent in the window).
- Its 7-day success rate.
- How many events are currently in flight, if any.
- When it last had a failure.
Failures grouped by reason
Section titled “Failures grouped by reason”The failure groups table collapses repeated failures into one row per unique combination of destination, failure reason, and HTTP status, with a count, and when it was first and last seen. Selecting a group filters the failure list below to just those events.
The failure list itself can be filtered by destination, failure reason, HTTP status, or by searching an event ID or order ID, and supports pagination for larger result sets.
Payload detail
Section titled “Payload detail”Selecting a failure opens a detail view with three tabs:
- Source event: the event Máximo captured, before it was sent anywhere.
- Destination request: what Máximo sent to the platform.
- Destination response: what the platform sent back.
All three are sanitized before display, access tokens, API secrets, and authorization headers are redacted.
Retention
Section titled “Retention”- Failure detail (the request/response payloads above) is kept for 30 days, then deleted.
- Success and skip counts are kept indefinitely as hourly totals, they don’t carry payload detail, so there’s nothing sensitive to expire.
A failure that’s aged out of the 30-day window still shows up in a link (for example, from an events tab) but its detail view will say it’s no longer available.
No self-service replay
Section titled “No self-service replay”This page is for diagnosis, not action, there’s no button to resend a failed event. Once the underlying cause is fixed (reconnecting an account, fixing an expired token, and so on), new events flow normally; a permanently failed one isn’t retried automatically after that point.
Acting on common failure reasons
Section titled “Acting on common failure reasons”| What you see | What it usually means | What to do |
|---|---|---|
| Failures with HTTP 401 on Google Ads | Your Google Ads authorization expired or was revoked | Reconnect Google Ads from Connect Google |
A destination shows failures with its own error code (for example, prefixed META_, TIKTOK_, or GOOGLE_) | The platform rejected the request for a reason specific to it | Check the failure’s error summary in the detail view: it includes the platform’s own message |
| Lots of skipped events for a destination, no failures | Máximo deliberately didn’t send them: check the skip-reason breakdown | If the skip reason relates to a missing connection or a tag not loading, fix the underlying setup on that destination’s settings tab |
| A destination shows No data | Nothing has been sent to it yet in this window | Confirm the destination is connected and has events turned on |
If a destination’s connection needs attention, its settings page is the place to fix it: Google connect, Meta connect, TikTok connect, or Pinterest connect.
Next steps
Section titled “Next steps”- Pixel presence: check whether the underlying storefront tags are loading at all.
- Google event delivery: a Google-specific view of the same delivery data.