Negative signal capture

Description

The pattern that detects absence: customer disengagement, the pause before churn, the things that don't fire an event but should have. Models for retention, win-back, and predictive churn depend on negative signals more than positive ones, but most stacks are built around positive event firing and treat absence as a query problem rather than a capture problem.

Common failure modes

• 01Negative signals defined only by absolute thresholds (no purchase in N days) rather than relative to the customer's own baseline cadence
• 02Negative signal triggers fire too late to inform intervention, by which point the customer has already churned and the trigger is just retrospective measurement
• 03"No event" indistinguishable from "tracking broken," so dropouts in instrumentation present as customer disengagement
• 04Negative signals not consent-scoped, capturing behavioral patterns from customers who shouldn't be modeled at all

Tools for this pattern

The capability a stack needs to run this pattern, and the vendors that provide it, on Martech Stack Builder.

• NeedsChurn Prediction
• RelatedPredictive Scoring / Propensity

Recipes composing this pattern