Tracking monitoring

Máximo checks your tracking every hour against your store’s own history. When the number of events it receives, or sends to a destination, moves further than your store’s normal ups and downs, or the share of shoppers allowing tracking shifts, it opens an alert. You see the alert on your dashboard and on the Tracking monitoring page, and your team can be emailed about it.

To open the page, go to Settings and select Tracking monitoring in the Notifications section. The row shows how many alerts are open. On the page you can see what’s being watched, change how sensitive alerts are, mute alerts, and review past alerts.

What Máximo watches

What	What’s counted
Events received	Storefront events reaching Máximo, as a total and for each event: Purchase, Checkout, Payment info, Shipping info, Add to cart, Cart view, Product view, Collection view, and Page view. If your store sends custom events, they’re watched as one group of their own.
Events sent to each destination	Events Máximo successfully delivered to each connected destination, as a total and for each event.
Marketing consent and Analytics consent	The share of sampled storefront visits where the shopper’s consent choice allows marketing tracking (ad platforms and Klaviyo) or analytics tracking (GA4).
Máximo app embed	Whether the Máximo Pixels app embed is switched on in your published theme. Not checked on a Hydrogen storefront, which has no theme embed.

Counts are only ever event counts. Tracking monitoring never compares revenue.

How a change is detected

Each hour, once the previous hour has fully closed, Máximo compares your latest counts with the same hours of the week in each of the four weeks before. The middle value of those four weeks is the usual level.

A count opens an alert only when both of these are true:

The change is big enough to matter. It moved by at least your alert threshold, 20% by default (see Sensitivity).
The change is bigger than normal noise for your store. Máximo learns how much each count naturally varies from week to week, so a store with two orders an hour missing one order doesn’t trigger an alert, while a large store dropping by the same share does.

A few rules keep alerts about tracking, not about your sales:

Windows. Each count is judged over the last hour, 6 hours, 24 hours, or 3 days, using the shortest window that has enough events to tell a real change from noise. Busy stores are checked hour by hour; quieter stores over longer stretches.
Orders. Over 24 hours and 3 days, the usual level is adjusted for how your Shopify orders moved in the same period, so a slow day for the business isn’t read as broken tracking. A move over 1 or 6 hours that your orders also made over the last 24 hours doesn’t open an alert.
Sale days. A day when orders ran well above normal is left out of the usual level, so a sale doesn’t become next week’s bar.
Two checks in a row. A change has to show up on two consecutive hourly checks before it becomes an alert. Until then it isn’t on your dashboard, in your history, or in an email.
Closing. An open alert closes once the affected counts are back within half of the threshold, for example back within 10% of usual with the default 20% threshold, on every window that was affected.
Problems on Máximo’s side. If Máximo’s own event pipeline has a problem affecting many stores, drops during that time aren’t held against your store.

When events sent to a destination fall because events received fell, the received alert is the one that opens. The destination shows Follows events received rather than a second alert.

Consent is checked as a share over the last 24 hours against the usual share, and needs enough sampled visits in both periods before it’s judged.

Coverage

The first section, What we watch, shows how closely Máximo can watch your store right now, and when it last checked.

Coverage	What it means
Full monitoring	Every count is checked each hour against the same hours in previous weeks.
Limited monitoring (daily checks)	Your store has low event volume, so whole days are compared instead of single hours. A change can take up to a day to show.
Limited monitoring (too few events)	There are too few events to check reliably yet. Checks start on their own once your store has more.
Learning your usual levels	Máximo needs about three weeks of history to know what’s usual for your store. No alert opens until then. Checks start on their own.
Not monitored (no events yet)	Máximo hasn’t received any storefront events yet.

Below that, a table lists each count with its status and how the last 24 hours compare with a usual day, for example 1,240 vs about 1,300, or 61% vs about 82% for consent. The statuses you’ll see most often:

Status	Meaning
OK	Within the usual range.
Lower than usual / Higher than usual	Moved past your threshold. An alert is open or about to be confirmed.
Near usual / Too close to call	Moved, but not clearly enough to call it a change.
Learning / No usual level yet	Not enough history for this count yet.
Too few events	Too little volume to judge, even over 3 days.
Moved with orders	The change matches how your orders moved, so it isn’t treated as a tracking problem.
Sale day, not judged	Orders were far above normal, so this period isn’t judged.
Follows events received	Explained by a change in events received, which has its own alert.
Paused by you	You turned this event off for that destination.
Turned off by you	You turned custom events off.
Muted	Covered by an active mute.
Paused on our side	Máximo’s own pipeline had a problem during this window, so drops aren’t judged.

Sensitivity

Alert when volume changes by sets how big a change has to be before Máximo alerts you. It applies to every count, including consent, unless you add an override. Enter a whole number from 5% to 90%, then select Save. A lower number alerts on smaller changes.

Also alert on spikes controls email for increases. Drops always email your team; spikes always show on your dashboard and on this page, but only email when this is on. It’s off by default.

Overrides

Add an override when one event or destination needs a different threshold, for example a destination whose volume swings more than the rest.

Under Add an override, choose a Destination, an Event, or one of each. Leave either on Any destination or Any event to cover all of them.
Enter Alert at as a percentage.
Select Add override.

Each override is listed by what it covers, such as Purchase events sent to Meta, Purchase events (received and sent), or Everything sent to Meta. Remove returns that scope to the store-wide setting. Custom events are only ever received, so they can’t be paired with a destination.

An override can also switch spike emails on or off for just its scope when it’s set from an AI tool. The list then shows Also alerts on spikes or Spike alerts off under it.

Mutes

Mute alerts for a sale, a planned change, or maintenance.

Under Mute alerts, choose an Event and a Destination. Leave both on Every event and Every destination to mute all alerts.
Under For, choose 24 hours, 7 days, or 30 days.
Select Mute.

Active mutes lists each mute with when it ends and the time left. Select Unmute to end one early.

While a scope is muted, no new alert opens for it and its counts show Muted. If you mute everything an open alert covers, that alert closes at the next hourly check and no all-clear email is sent.

Past alerts

Past alerts lists alerts from the last 90 days, newest first, with when each opened and its state: Open, Resolved, or Marked expected. Each title says what moved and in which direction, with the size of the change underneath, for example 38% lower than usual:

Fewer events received, or More events received for a spike
Fewer events sent to Meta
Fewer visitors allowing marketing tracking
Máximo app embed is off

In alert emails, the title also names the event when one or two account for the change, for example Fewer purchase events sent to Meta.

Select Details on an alert to see:

A one- or two-sentence summary, for example: “Máximo received 38% fewer purchase events than usual in the 6 hours to 2:00 PM (412 vs about 660). Marketing consent fell from 82% to 61% over the last 24 hours.”
What changed: each affected count, the window it was judged over, Seen vs usual, and the Change.
What else changed: anything that happened around the same time, such as a new theme being published, the app embed being switched off, a destination’s event mapping changing, a consent shift, or orders moving.
Recent checks: the latest hourly checks for this alert.

Times are shown in your store’s time zone.

On your dashboard

While an alert is open, your dashboard shows it as a Heads up card, for example Fewer events reaching Meta than usual with “This is lower than Máximo usually sees at this time.” Select Review alert to open that alert on the Tracking monitoring page with its details showing. For the app embed, the card reads Máximo app embed is off and its button is Turn on the app embed.

The affected destination’s card under channel health shows the same line, such as Fewer events reaching Meta than usual, and links to that destination’s settings.
Spikes show as cards too, but they don’t count as issues to act on.
Select ✕ to dismiss a card. For editors and admins this hides it for your whole team; for viewers, it hides it just for your current session. If the same change happens again later, it’s a new alert and a new card.

This was expected

If a change was planned, such as a sale ending, a theme change, or turning off a destination, select This was expected on an open alert in Past alerts, then Mark as expected. This:

Hides the alert on your dashboard.
Stops any alert email that hasn’t gone out yet, and skips the all-clear email.
Leaves the alert in Past alerts as Marked expected. It still closes on its own when volume recovers.

You can only mark an alert as expected while it’s open.

When the app embed is off

The Máximo app embed is off alert opens when the Máximo Pixels app embed is switched off in your published theme, often after a new theme is published. While it’s off, Meta, TikTok and Google browser tags don’t load and ad click IDs aren’t saved to orders. Server-side events keep flowing, so event counts may not move at all.

To fix it, turn the embed back on: see Enable tracking. The alert closes once Máximo sees the embed on again.

Who can change what

Action	Viewer	Editor	Admin	Owner
View coverage, settings, and past alerts	✓	✓	✓	✓
Mark an alert as expected		✓	✓	✓
Change sensitivity, overrides, and mutes			✓	✓

See Team access & roles.

From an AI tool

An AI tool connected to Máximo over MCP can read the same information and make the same changes: get_volume_health and list_monitoring_incidents read status and alerts, get_monitoring_thresholds and set_monitoring_thresholds read and change sensitivity and mutes, and mark_monitoring_incident_expected marks an alert as expected. The same roles apply: changing thresholds needs Admin, marking an alert as expected needs Editor. See the MCP tools reference.

Next steps

Alert emails: who gets emailed, and what to do about each alert.
Pixel presence: whether each destination’s pixel is loading for real shoppers.
Delivery monitor: why individual events failed to reach a destination.