How to Get Alerted When Shopify Conversion Tracking Breaks

TL;DR

There is no single alarm for Shopify conversion tracking, and this app does not email you when delivery stops. Three surfaces come close and each is blind somewhere: GA4 custom insights fire on GA4 arrivals only, hourly at best and only for web data [1]. Meta's Ads Data Advisor is a browser extension, so a server-side outage is invisible to it [2], and the Meta surface that does see coverage collapse is an API you call yourself [3]. Shopify's app pixel activity log records data-access changes from June 3, 2026 onward, and Shopify's documentation does not say it notifies you [4]. Wire all three, then keep one number that catches what the three cannot see.

Key Takeaways

• Build the GA4 custom insight first. It is the only surface here with email notification, evaluation can run hourly, and hourly is available only for web data [1].
• Meta's Ads Data Advisor is documented as a "free Google Chrome extension" that can "alert you when issues are detected" [2], which also means it only sees what a browser sees.
• The Meta number that actually collapses during a server-side outage is event coverage percentage, in the Dataset Quality API [3], which has no email and no dashboard alert.
• Shopify can pause an app pixel's data access on its own, and its documentation describes no merchant notification when that happens [4]. The activity log holds the record, and you have to go and read it.
• GA4's automated anomaly detection is slower than the custom insight you build yourself: segment anomalies are analysed weekly, with training periods of 2 weeks for hourly data and 90 days for daily [5].
• No alarm in the set notices an order webhook that never arrived. A tracking accuracy figure that counts untracked orders as failures does.
• Worst case, a silent break sits for days, which is the argument for ten minutes on the GA4 insight rather than promising yourself you will check the dashboards.

Nothing alerts you by default, including the app

Start with the uncomfortable part, because it changes what you go and build.

Shopify does not notify you when a pixel stops firing. Ad platforms do not push you a message when a conversions API integration goes quiet, and their dashboards are surfaces you visit rather than services that page you. WeltPixel Conversion Tracking has no outbound alerting at all: no email, no Slack message, no webhook out, no scheduled anomaly detector. It measures delivery and shows the result when you open it. The platforms are where the alarms live.

That is a deliberate split rather than a gap. An app that kept its own copy of every merchant's event stream in order to watch it would be storing data it has no reason to hold. It computes a delivery accuracy figure on read instead, and that figure catches the one failure the platform alarms all miss.

If what you actually want is a one-time check rather than a standing alarm, stop here and use the pixel audit walkthrough, or the ten-point post-install checklist if the install is new. This article is about the standing alarm.

Which alarm can you build in ten minutes?

The GA4 custom insight, and it is the only one on the list that will email you.

Google's documentation is explicit that "you can create your own sets of rules to generate insights", that you "choose how often data is evaluated per the condition you create: Hourly, Daily, Weekly, Monthly", and that for each custom insight "you can turn email notification on or off for property users" [1]. Two constraints matter for tracking work: "Hourly evaluation is available only for web data", and "you can create up to 50 custom insights per property" [1].

Build these three:

1. In GA4, on the Insights card click View all insights, then Create, then under Start from scratch click Create new.
2. Condition one: purchase event count, evaluation frequency Hourly, condition "is less than" a floor you pick from your own quietest hour of the week. Set it below your real trough so it does not cry wolf overnight.
3. Condition two: begin_checkout count on the same hourly frequency. A purchase drop with begin-checkout healthy points at the checkout or the webhook. Both dropping together points at the pixel or the store.
4. Condition three: sessions, evaluated Daily. This is the control. If sessions dropped too, the problem is traffic rather than tracking, and that distinction saves an afternoon.
5. On each insight, turn on email notification and enter the address of whoever actually reads email at 7am; nothing is emailed until an address is entered [1].

Google's separate automated anomaly detection is not a substitute. It uses "a Bayesian state-space time series model" with training periods of two weeks for hourly data, 90 days for daily and 32 weeks for weekly, and segment anomalies are analysed weekly [5]. Useful for slow drift, too slow for a break.

The blind spot to write on a sticky note: a GA4 insight fires on GA4 data. If Meta's conversions API stops and GA4 keeps receiving purchases, every one of those three insights stays quiet.

Does Meta tell you when server-side events stop?

Not through the tool that does the alerting, no. Meta has two relevant surfaces and their blind spots are opposite.

Ads Data Advisor, formerly Meta Pixel Helper, is documented as "a free Google Chrome extension" that helps you "monitor your setup for issues". It can "alert you when issues are detected", flagging "broken events and missing parameters (for example, content_ids, value, and currency)" [2]. On a store whose purchase and funnel events are delivered server-side, a browser extension is watching the wrong pipe. It can be perfectly green while your conversions API has been silent for two days.

The surface that can see it is the Dataset Quality API, which Meta describes as "consolidating dataset quality metrics programmatically at scale" [3]. It returns Event Match Quality "calculated in real time", Additional Conversions Reported, event coverage as a 7-day average percentage of pixel events covered by the conversions API, dedup-key feedback across browser and server, and data freshness, which the page defines as the delay between the time the event occurred and when Meta received it [3]. Event coverage is the number that collapses when a server-side integration dies, and it is the only Meta number that does.

The catch is access. It needs a valid access token, a dataset ID and the "Partial access -> Use events dataset" permission [3], which is a developer job rather than a merchant click path, and it pushes nothing to you. If you have someone technical, a daily cron that reads event coverage into Slack is the highest-value fifteen lines of code here.

While you are in Events Manager, match quality is worth reading in the same visit: how to get Meta event match quality to 8 or higher covers what moves that number.

Shopify's activity log is a log, not an alarm

Shopify can pause an app pixel's data access on its own, and the record of it lives in the app pixel activity log [4].

Nothing is pushed to you when that happens. Shopify's documentation states no merchant notification for an automated pause [4], and I could not verify that one exists. So this surface tells you what happened, accurately, whenever you go and look. Put it on a calendar reminder if you want it to function as an alarm.

Both halves of this have owners already, and I am not restating them here: what the app pixel activity log records and Shopify can pause your pixel: the optimized data sharing default.

The break none of the three alarms sees

An order webhook that never arrives.

Think about what each alarm watches. GA4 fires on events GA4 received. Meta's coverage percentage compares server events against browser events it received. Shopify's log records access decisions it made. If an order comes into your store and nothing anywhere produces a tracking outcome for it, every one of those surfaces sees a slightly smaller number and none of them sees a failure. The event is absent rather than wrong, and absence is what alarms are worst at.

A delivery accuracy figure computed as sent divided by attempted catches it, provided untracked orders count in the denominator. That is how WeltPixel Conversion Tracking's Conversion tracking card computes it: orders the shop received that produced no tracking outcome at all are counted as failures, not skipped. The card shows Platform, Sent, Skipped, Accuracy and Trend per channel over a rolling window, with a per-day breakdown on expand, and Google Ads skips carry their own explanation because some of them are structural rather than breakage.

Two honest limits. It recomputes when someone opens the app, so nobody is watching it for you. And the recent events stream next to it lists successes only, across GA4, Meta, TikTok, Reddit, Klaviyo, Snapchat, OpenAI Ads and Pinterest, never Google Ads. A total failure renders there as an empty list, which looks identical to a quiet afternoon.

One genuinely break-detecting thing does exist in the app's own UI: on the channels that have a status banner, the banner reports configuration state, and one state is tracking active but the pixel not embedded. That is what a theme change looks like when it drops the app embed. On the delivery layer itself, why server-side retries double count purchases.

How long can a break hide?

Longer than most merchants assume, and the differences between surfaces are large enough to plan around.

Read that column of "nobody" and the priority is obvious. Build the GA4 insight, because it is the one line in the table that reaches a human. Everything else is a place you go, and places you go get visited on the days you already suspect something.

FAQ

Can WeltPixel Conversion Tracking email me when tracking breaks?

No. The app has no outbound alerting of any kind: no email, no Slack, no webhook out, no scheduled anomaly check. It computes delivery accuracy per platform and shows it when you open the app, and the alarms have to be built in GA4 and the ad platforms.

What is the single best alarm to set up first?

A GA4 custom insight on hourly purchase count with email notification on [1]. Ten minutes, no developer, and it covers the failure mode that costs the most money.

Will Shopify tell me if it pauses my app pixel?

Shopify's documentation does not say that it notifies you, and I could not verify that a notification exists. What it does say is that the activity log records the pause with a reason, and that it captures changes made from June 3, 2026 onward [4]. Check it yourself after any drop.

Why does Meta's pixel tool show everything healthy while conversions are down?

Because Ads Data Advisor is a Chrome extension watching browser events [2]. In a server-side setup the purchase does not travel through the browser, so the extension has nothing to notice. Event coverage and data freshness in the Dataset Quality API are the fields that move [3].

Is there a way to catch a missing order webhook?

Only by comparing orders received against orders delivered. A delivery accuracy figure that counts untracked orders as failures shows the gap as an accuracy drop rather than as silence, which is why that one number is worth reading even though nothing pushes it to you.

Wire the alarms, then keep one number to check them against

Alarms tell you when a platform noticed. A per-platform delivery figure tells you what left your store, including the orders no platform ever heard about. WeltPixel Conversion Tracking's Conversion tracking card shows Sent, Skipped, Accuracy and Trend for every channel you have enabled, over a rolling window, with untracked orders counted as failures rather than ignored, so a lost webhook reads as a number instead of as silence. Install it from the Shopify App Store listing [6], then build the GA4 insight, because the app will not call you.

Do the GA4 insight today. It is the only item here that will ever interrupt you.

Sources

1. Google Analytics Help, "Custom insights" (evaluation Hourly, Daily, Weekly, Monthly; hourly for web data only; email notification per insight; up to 50 per property), support.google.com/analytics/answer/9443595, accessed September 10, 2026
2. Meta for Developers, "Meta Ads Data Advisor" (a free Google Chrome extension; alerts when issues are detected; flags broken events and missing parameters), developers.facebook.com/documentation/meta-pixel/support/meta-ads-data-advisor, accessed September 10, 2026
3. Meta Marketing API, "Dataset Quality API" (Event Match Quality in real time; Additional Conversions Reported; 7-day average event coverage; dedup-key feedback; data freshness; requires an access token, dataset ID and events-dataset permission), developers.facebook.com/docs/marketing-api/conversions-api/dataset-quality-api/, last updated May 28, 2025, accessed September 10, 2026
4. Shopify Help Center, "App pixels" (historical view of app pixel data access changes, captured from June 3, 2026 onward; Data access granted / paused with an automated or manual reason), help.shopify.com/en/manual/promoting-marketing/pixels/app-pixels, accessed September 10, 2026
5. Google Analytics Help, "Anomaly detection" (Bayesian state-space time series model; training 2 weeks hourly, 90 days daily, 32 weeks weekly; segment anomalies analysed weekly, 0.05% of users minimum), support.google.com/analytics/answer/9517187, accessed September 10, 2026
6. WeltPixel Conversion Tracking, Shopify App Store listing, apps.shopify.com/weltpixel-conversion-tracking, accessed September 10, 2026