The alert
A date, an asset, and the spend since
Not a dashboard tile that says fatigue is elevated. A message naming the asset, the day it broke, the metric that broke first, and what the blended account number did over the same window, which is nothing.
- 1.Cap frequency on hook-a-summer-v3 or rotate it out; it has been past its useful life since Aug 10.
- 2.Move its budget to carousel-offer-v4, whose click-through has held flat at 1.5% across the whole 60-day window.
- 3.Re-cut the hook rather than the offer. Engagement broke before conversion, which points at the first three seconds, not the landing page.
- 1.Cap frequency on hook-a-summer-v3 or rotate it out; it has been past its useful life since Aug 10.
- 2.Move its budget to carousel-offer-v4, whose click-through has held flat at 1.5% across the whole 60-day window.
- 3.Re-cut the hook rather than the offer. Engagement broke before conversion, which points at the first three seconds, not the landing page.
The engine dated the engagement break at 2026-08-10 and the conversion break at 2026-08-17, 7 days later. A kill rule written on conversion or CPA cannot fire before the second date, so at $2,180 a day this asset spends $15,260 inside the lag. Both numbers on this page are read off the detection run, not typed in.
Statistics decide whether the asset changed. The model only writes up something that already cleared that bar. Asking a model to look at a chart and judge whether a creative is tired is how these products end up killing your best performer on a slow Tuesday.