Skip to main content

Change Log and Incident Response

Objective​

Reduce mean time to diagnose by maintaining clean change history.

Change Log Minimum Fields​

Date/time:
Operator:
Asset changed:
Reason:
Expected impact:
Rollback plan:
Review date:

Incident Severity Levels​

  • SEV1: conversion tracking or billing outage
  • SEV2: major campaign traffic or conversion drop
  • SEV3: isolated ad or asset issue

Incident SOP​

  1. Classify severity and assign incident owner.
  2. Stabilize account (pause risky changes).
  3. Diagnose likely cause using timeline and logs.
  4. Implement fix and validate against baseline.
  5. Run postmortem with prevention actions.

Next Step​

Return to the module overview and continue with the next lesson in sequence.