How alerts work

TraceLog checks every declared conversion path once a day, in the project's time zone. An alert is the result of that check: a fact about the events TraceLog received, never an estimate.

When an alert comes

A declared step or conversion is watched once it arrives steadily: present on five of the last seven days. From then on, an alert comes:

• the morning after a full day without it, or
• after seven days in a row without it, for an element that arrives fewer than ten times a day.

A new install's first week is therefore quiet: an element that has not yet arrived steadily has nothing to stop.

What an alert says

Each alert names the step or conversion that stopped and the day it stopped. It says which of TraceLog's figures that leaves incomplete: a figure is shown only over days that received the whole path it counts, and the missing days stand in its place. It never says why it stopped or what to change; what you change is your decision.

When the fault is TraceLog's own, the alert says so instead of sending you to search your site. When the same element stops for several unrelated organizations on one day, TraceLog holds the alert and investigates it: see TraceLog service issue.

Where it arrives

Alerts reach the people ticked for Alerts under the project's Settings → Notifications, by email, and appear under Alerts in the project. Open the alert shows What TraceLog received: the daily counts as they were when it fired.

When it comes back

The alert's page states when the element arrived again, on every plan. No second email is sent: the return is read on the page.

Under What you did about it you can record what you changed. TraceLog puts what it observed afterwards beside it in time; the order alone establishes no cause.

Alerts on paid plans

On a free project, an alert names the question a paid plan would answer about it — whether what stopped came back in every channel, device and campaign — and never the answer.

From Pro, two more kinds of alert:

• A tag the page stops requesting. Where TraceLog's code runs in the page, it watches the GA4, Meta or Google Ads tags you confirmed and alerts when the page stops requesting one. It says the page stopped asking, never that the platform lost data, and never why. Shopify is not covered.
• A conversion, step or segment that fell. Where the data supports the comparison, TraceLog names which one fell against the period before, never the cause. It needs a thousand sessions in the week it compares and five whole weeks of data; a single segment needs more of its own. Below that, TraceLog says nothing rather than guess.

Over the session ceiling, alerts pause while capture continues without sampling; see plans and billing.

The Monday digest

Every Monday morning, in the project's time zone, the digest says which declared steps arrived on which days — even when nothing went wrong. Tick Digest for whoever should receive it. An organization with more than one project receives the weekly portfolio message instead; see agencies.