Series
Most of what I know about marketing systems I learned from something that broke. A promotion that died quietly on four country shops. A tag that disappeared from the page while the dashboard looked fine. A routine that told me a draft was ready when no draft existed.
I write these up the way I'd want to read them: what happened, how I found it, and what I changed so it can't happen the same way again. Client names stay out. The mechanics stay in, because that's the part you can use.
23 post-mortems · newest first · Follow the series (RSS)
Lesson: Fix the generator, not the page, and lock rebuilt pages against it.
Lesson: An agent must verify the claims it carries in its own state.
Lesson: Ad disapprovals are stored state. Somebody has to ask for the re-review.
Lesson: A conversion with a made-up value is worse than no tracking at all.
Lesson: Declare a price once and audit the whole chain daily. The price guard itself can be the bug.
Lesson: Closing an account means revoking every sign-in grant behind it.
Lesson: A promotion is a set of artefacts, not a date. End every one of them.
Lesson: Open the client's shop before you call a keyword set off-product.
Lesson: When a conversion drops to zero, check the page source before the container, and tell Smart Bidding its data was wrong.
Lesson: Compare equal windows, measured with the same ruler as the target.
Lesson: An agent has to know what its environment can do, and every lesson needs an owner.
Lesson: Ad spend lives per advertising channel, revenue per sales channel. Filter both or neither.
Lesson: Namespace what you add, and treat your own change as the first suspect.
Lesson: Check a directory against the commercial register before it sends anyone a lead.
Lesson: Somebody has to own the landing page of every ad.
Lesson: When a ratio jumps, check the denominator and the definition before you celebrate.
Lesson: Schedule a check where its tools exist, and let it report "nothing" honestly.
Lesson: A fix that never reaches the build engine gets rebuilt away.
Lesson: Silent failures are the expensive ones. Make the systems shout.
Lesson: Ask what happens when it runs twice, and make the automation idempotent.
Lesson: Every promise a form makes is a send you have to test end to end.
Lesson: Pin the day boundary to one timezone, and never show an estimate as a booked fact.
Lesson: Plausible wrong data survives longest. Check what a figure actually measures.