Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Marketing Incident

A live error in marketing work, data or systems that reaches customers, spend or reports, such as a wrong price, a wrong segment or a broken purchase tag.
StrategyconceptUpdated

Definition

A marketing incident is a live error in marketing work, data or systems that has reached customers, spend or the numbers the business decides with. The work is anything marketing publishes or sends; the data is a tag, an event, a feed or a report; the systems are the accounts and tools behind them. What the cases share is exposure: the error is no longer a draft someone can quietly put right, because somebody has seen it, paid for it or acted on it.

Exposure does not have to mean customers. The tutorial on correcting a number after a report has gone out states the threshold plainly: once a wrong figure has gone out it is an incident rather than a typo, because its readers may have moved budget or set a target from it.

AI-assisted work sits inside the same definition. The guide to handling an AI mistake treats it as an AI incident whenever something an AI tool wrote or influenced went wrongly to customers or changed their records in error, even when a person signed off the draft.

What makes an error an incident, and when it becomes a crisis instead

Reach is the test, not severity. A slip spotted before anything is published or sent is feedback for the process that made it. The same slip in a sent email has reached people, although the tutorial on fixing a mistake in a sent email shows that the response is proportionate: a typo usually needs nothing beyond a fixed template, while a wrong date, price or code may need a brief correction sent only to its original recipients. Calling something an incident decides who leads and what is recorded, not whether customers hear about it.

At the other end, an incident is not a crisis. The marketing incident management playbook keeps routine errors in their own procedures and hands over to the crisis plan only when the routine cannot cope, or when the trouble lies in the business rather than in marketing, because escalating ordinary errors wears out the route real crises need.

In practice: the lead, the procedure and the review

The incident is normally led by whoever owns the channel or asset involved, because that person can pause, revert and correct it. From the first hour there is a single named lead and a single error log entry for the whole incident. Customer service hears what to say before customers ask, and anything touching personal data goes to whoever owns data protection, who decides what follows.

Each kind of incident then runs through the page that owns it. In measurement, the measurement governance playbook has the measurement owner declare the incident, leaves channel leads to protect automated bidding, and closes it with a dated entry in the change log. In paid media, the SOP for pausing underperforming ads stops the weekly review when tracking looks broken and raises a tracking incident instead of pausing anything.

Once the error is contained and corrected, it is checked against triggers written in advance: customers saw it, money or data was touched, an existing check failed to stop it, or it repeats an earlier error. Meeting any trigger earns a full review using the tutorial on reviewing a marketing error; meeting none earns a single log line before the incident is closed.

Illustrative example — not a real result

A pet insurer's renewal email reaches lapsed customers

Ravvoel Pet Cover, an invented pet insurer, sent the first batch of its monthly renewal reminder to 6,300 people at 09:00. A segment rule had pulled in 2,100 customers whose policies had lapsed, and the email offered a 10% loyalty discount that had expired the month before. A service adviser flagged the first puzzled call at 09:40. At 09:45 the email owner was named incident lead and paused the second batch of 3,800. By 10:30 customer service had a three-line script: the discount had ended, lapsed customers could still get a quote, and the 41 who had already called would receive it as goodwill, as the commercial owner decided. The error entered the log that afternoon, naming the segment rule and the proof check that never compared the offer with its end date, and it was booked for review.

A Crisis Plan is what an incident hands over to when the routine is outrun, with its own triggers and its own decision-maker. A Holding Statement is the prepared first public response, owned by the communications lead, for an incident that may become public. An Escalation Route tells front-line staff whom to call, and how quickly, once a problem outgrows them, and belongs on the incident contact sheet. The Error Log is the one list where every incident ends, so that patterns across channels become visible. A Change Freeze holds back hard-to-reverse changes during the periods when an incident would cost most.

Common confusions

  • Every incident is a crisis. Most are routine errors with a known procedure. The crisis plan is for situations that procedure cannot absorb.
  • An incident always means a public apology. The response follows what the error would make people do. Many sent mistakes need no second message at all.
  • Internal errors do not count. A stopped purchase tag or a wrong figure in a sent report has reached spend and decisions.
  • It is over when the source is fixed. The incident closes only once the correction has been checked in every place the error appeared, the numbers it touched are repaired and the log entry says so.

More terms to look up

Where this term is used

Related