Skip to content
Sample storeStart free

Nothing here can be changed. TraceLog generates the events, which arrive each hour at five past, except overnight. Last event 1 h ago

And on your site?

Start free

On Free you see the last 30 days. With Pro, also each campaign and longer periods.

Demo data

view_product stopped arriving on Monday, September 28.

checkout_started was still arriving on September 28: not all of this path had stopped.

Arrived again on Oct 4, 2026, 9:42 PM, then stopped arriving again: a newer alert replaced this one. Open the newer alert

Last seen before the stop: Sep 27, 2026, 9:52 PM · Missing days: Sep 28 –⁠ Oct 3, 2026

view_product arrivals

  • Step 1 of 2 · view_product
  • Step 2 of 2 · checkout_started
  • Did not arrive

Step 1 of 2 on the path of the purchase (purchase_completed).Nobody was notified: this is a demonstration project

Purchases (purchase_completed) and their rate are unaffected. The path is incomplete on those days: do not compare periods that include them.

Where to check

Check what changed where view_product is sent. TraceLog had no other customer's site to compare this stop with, so it cannot say whether the fault was TraceLog's.

What to look for on your site

What TraceLog received

Events per day, Sep 15 –⁠ Sep 28, 2026, in the project's time zone, as they stood when the alert fired.

See the daily numbers
Events
Dayview_productcheckout_started
Sep 15, 202600
Sep 16, 202600
Sep 17, 202600
Sep 18, 202600
Sep 19, 202600
Sep 20, 202600
Sep 21, 202610112
Sep 22, 202610212
Sep 23, 202610112
Sep 24, 202610112
Sep 25, 202610312
Sep 26, 202610412
Sep 27, 202611013
Sep 28, 2026012

What happened, in order

TraceLog does not know whether one of these caused another.

  1. TraceLog detected this

    Sep 29, 2026, 2:00 AM

  2. The event arrived again

    Oct 4, 2026, 9:42 PM

And on your site?

Start free

On Free you see the last 30 days. With Pro, also each campaign and longer periods.