Skip to content

Pixel presence

Connecting a destination and turning on its pixel tells Máximo what it should be doing. Pixel presence tells you when it isn’t: when a destination’s tracking isn’t loading for real shoppers on your storefront, or when fewer events than usual are reaching the platform.

Each destination is either healthy or has a line telling you what needs attention, marked as a warning or as critical. A healthy destination shows nothing at all, so no line means nothing needs your attention. You never see a percentage or a count, just the line and a link to the settings page where you fix it.

The status draws on two things Máximo already watches:

  • Real storefront visits. Máximo samples real shopper visits, respecting each shopper’s consent choice, and checks whether each destination’s tag actually loaded. This isn’t a configuration check: a destination can be set up perfectly in Máximo and still show a problem here if something on your storefront, such as a blocked script, a theme conflict, or another app, stops the tag from running.
  • Tracking monitoring. When tracking monitoring has an open alert for events reaching a destination, or for storefront events reaching Máximo, the affected destinations show it too.
LineWhat it means
Not detected on your storefrontThe destination’s tag didn’t load on the visits Máximo sampled.
Máximo app embed is offThe Máximo Pixels app embed is switched off in your published theme. This affects your whole store, so every destination shows it.
Storefront tracking is darkPaid online-store orders are reaching Máximo without a matching purchase event far more often than usual for your store. This affects your whole store, so every destination shows it.
LineWhat it means
Not loading on every visitThe tag loads on some visits but is missing on too many of them.
A different Meta pixel ID is firingA tag loaded with an ID that doesn’t match the one saved in Máximo. The line names that destination’s ID, for example A different TikTok pixel ID is firing or A different Google tag ID is firing.
Fewer events reaching Meta than usual or More events reaching Meta than usualTracking monitoring has an open alert for events Máximo sends to that destination. The line names the destination, for example Fewer events reaching Google than usual.
Fewer storefront events reaching Máximo than usualTracking monitoring has an open alert for storefront events reaching Máximo. This affects your whole store, so every destination shows it.

If tracking monitoring has also seen a change in how many shoppers allow tracking, a line about fewer events ends with , likely from a consent change, for example Fewer events reaching Meta than usual, likely from a consent change.

A critical line always takes priority over a warning. When a destination has more than one problem at the same level, one line is shown and the rest are summed up as and one more issue or and more issues.

Each place shows the line only when a destination needs attention:

  • Connection tab for Meta, TikTok, and Google: a status line on the connection card.
  • Pixel + Events tab for Meta and TikTok: the tab’s status reads Live · {line}, for example Live · Not loading on every visit. The full line also appears on the Pixel ID card (Meta) or Pixel code card (TikTok), under Active on storefront.
  • Ads tab for Google: the tab’s status reads Live · {line}.
  • Google tag tab: one line under the Google tag card title.
  • Dashboard: under Channel health, each destination’s card shows its line and links to that destination’s settings. In the row of tracking facts below the cards, Storefront pixel shows the most serious one, for example Meta: Not loading on every visit. On a card’s 30-day strip, a day’s tooltip reads pixel not loading on some visits when a tag was missing that day.

Pixel presence only ever changes a tab’s status from Live. If a destination is disconnected or its token has expired, the tab says so, and pixel presence never makes it look healthier than that.

Ask Máximo and AI tools connected over MCP read the same status through get_signal_quality, so they report the same lines you see in the app.

Pixel presence speaks up only once there’s enough real traffic and history to judge. A newly enabled pixel, or one on a store with little traffic, shows nothing until then.

A destination that isn’t set up, or whose pixel you’ve turned off, shows nothing either: an intentionally off pixel isn’t a tracking problem. An alert you’ve marked as expected on the Tracking monitoring page doesn’t count toward any destination’s status.

What you seeWhat to do
Not detected on your storefrontConfirm the Máximo Pixels app embed is on: see Enable tracking. If it is, check for a consent banner, another app, or a theme change that stops the tag from loading.
Máximo app embed is offTurn the embed back on: see Enable tracking. It’s often switched off when a new theme is published.
Storefront tracking is darkOn Settings → Storefront events, check that the conversion pixel shows Registered. See Troubleshooting.
Not loading on every visitCheck whether a recent theme change, another app, or a consent banner setup stops the tag on some pages. Ad blockers and browser tracking prevention also stop tags on some visits.
A different … ID is firingAnother copy of that platform’s tag is running on your storefront outside Máximo, usually left over from a previous integration. Remove it so only Máximo’s tag reports for that destination.
Fewer or More events reaching … than usualOpen the alert on the Tracking monitoring page to see what changed. If the change was planned, such as a sale ending, mark it as expected.
  • Tracking monitoring: how Máximo watches your event volume and consent, and how to tune or mute alerts.
  • Enable tracking: turn on the conversion pixel and the app embed.
  • Delivery monitor: check whether events that do arrive are being sent successfully.