Written by Matthew Niederberger for Martech Therapy
Use cases arranged by outcome rather than by tool, each written out in the same seven boxes: the problem, the outcome, the data, the equipment, the people, the technique and the ways it goes wrong.
Free to read and openly licensed. No form.
What are you trying to fix?
Or scan the corpus at once: landscape arranges recipes by outcome, atlas draws them as a radial map.
Each recipe names the orchestration patterns underneath it. Many recipes share patterns; that's the editorial point. Browsing by pattern is how you find every recipe that uses the logic you already have.
Browse all patterns →Cross-platform suppression with consent propagation
The version most brands shipped first works on Meta. The version that actually delivers the outcome works across every retargeting channel, propagates consent state through GDPR jurisdictions, and re-introduces customers at the right point in the post-purchase cycle. The gap between the two is why this is a Workshop conversation.
Audit the personalization models for systematic bias in who they exclude, accelerate, or under-serve, so the model's behavior is defensible per protected category and per business-sensitive segment
Pick an attribution model, lock it, document why, and reconcile its outputs against incrementality, so the channel report becomes one rule the team can defend rather than a debate per meeting
Run identity resolution behind one service rather than each downstream system maintaining its own join logic, so a single resolution rule survives the next stack change
Surface the items the customer is most likely to want next, with explicit handling of the cold-start visitor, the privacy-restricted slice, and the rule that prevents the recommendations from collapsing to whatever everyone clicks
Patterns are the orchestration logic the recipes compose: forty-two patterns in seven groups. Most martech failures are failures of a pattern, not of a tool.
The seven boxes of any recipe, condensed to a one-page sheet for the meeting where the use case gets decided. This tier asks for a business email and it feeds the Workshop; that is what it is for. Everything else here stays open.
Sign up with business email →When you want to work out which of these matter for your own stack, that is the Workshop: ninety minutes with the people who own the decision, ending in one next move. About the Workshop →