An ad incident log template for tracking and account problems

When tracking breaks at night, memory is the first thing to fail. A log started at the first sign keeps the timeline honest.

Operations · 4 min read · Updated 2026-10-07

The fields

  • Incident ID, and the date and time it was first seen, in the client's time zone.
  • Seen by, and the account, store or tag affected.
  • What happened: one or two sentences with facts only.
  • Impact: spend, orders or results affected, and how that was measured, or 'not measured'.
  • First action, and the time it was taken.
  • Cause: what we know, and what we only suspect, marked as such.
  • Fix applied, with the approval reference and the read-back result.
  • Client told: when, by whom and in which channel.
  • Prevention: the one check that would have caught it earlier.
Made-up scenario: on a Tuesday at 09:10 the purchase count in one store's report fell to zero. The first action at 09:25 compared store orders with the report, and the gap confirmed the problem. Suspected cause: a tag change. Fix approved at 11:00 and read back the next morning.

Rules

  • Start the log when the problem is first seen, not after the fix.
  • Keep the timeline in order, and mark every guess as a guess.

Tick it off

Your ticks stay in this browser only.

Built for shop owners, creators and agencies. Stock photos, not customers.

Run the next client review from one screen.

We open one agency at a time, with your own accounts connected read-only first.

Request access

How we plan to price it