انتقل إلى المحتوى

لم تُترجم هذه الصفحة بعد، لذلك تظهر بالإنجليزية.

GA4 alerts for an online store

Last updated November 10, 2026

An online store needs three GA4 alerts: one for silence, when the site stops getting visitors at a time it normally has them; one for revenue falling against the previous period; and one for key events, such as purchases, falling. The first catches a broken tag or an outage, the others catch a checkout or payment problem that traffic alone hides. SilenceRadar provides all three for every GA4 property you watch.

Set up the three alerts

  1. 1

    Connect the store's property

    Connect the Google account that can see the store's GA4 property. Silence watch then covers it with no further setup, and you can change the threshold per site.

  2. 2

    Add a revenue alert

    On the Alerts page, add a rule with the metric Revenue, a percentage change against the previous period of the same length, and a drop you would act on.

  3. 3

    Add a key event alert

    Add a second rule on the metric Key events, so a checkout that stops converting is flagged even while traffic looks normal. Revenue and key events only report what your GA4 setup records, so check purchases appear in GA4 first.

  4. 4

    Choose where alerts go

    Alerts go to your account email. Add more addresses, a Slack channel or a signed webhook so someone is reached outside office hours. See GA4 alerts in Slack.

What each alert catches

AlertCatchesDoes not catch
SilenceOutage, removed tag, consent change, wrong measurement IDA site that has traffic but can't take payments
Revenue dropPayment provider or checkout failure, a broken price or promotionA slow decline within normal swings
Key event dropA broken purchase or sign-up event, a form that no longer submitsProblems before the funnel

Avoid noisy alerts

  • Percentage drops on a small store jump around; use a larger window or a bigger drop so a quiet day isn't an alert.
  • Sales have weekly rhythm. A daily anomaly check compares a day with the same weekday in earlier weeks, which suits a store better than a flat threshold.
  • Keep silence thresholds at their default unless the store is busy enough to notice a gap sooner.

Before a sale or a launch

Run the GA4 tag checker on the store's key pages, and make a test purchase to confirm it shows in GA4. Then check the Radar during the sale: a site that falls silent stands out among the others.

Questions

Can GA4 alert me about sales on its own?

GA4 custom insights can email you when a metric changes, one property at a time. They don't check whether the site is up or whether the tag has stopped sending data.

Which GA4 metrics can SilenceRadar alert on?

Active users, sessions, page views, key events, revenue, bounce rate and engagement rate, among others, above or below a value or as a percentage change.

Will I be alerted about a payment provider outage?

Only through its effect: a revenue or key event drop rule fires if purchases stop being recorded. SilenceRadar doesn't monitor your payment provider directly.

Do store alerts cost extra?

No. They are part of the one plan, $9 a month or $90 a year after a 7-day free trial without a card.