Subscriber insight status changed

A reader crossed a boundary in the newsletter's engagement ladder: reader to superfan, or engaged to dormant. This is the moment a CRM or a re-engagement automation has something to do; the scores themselves are on GET /newsletters/{newsletter}/insights.

Fired by a scheduled scoring pass, once per reader whose status actually differs from the one already stored, so a pass that changes only the scores is silent.

occurred_at is when the crossing was computed, not when the reader acted. data.last_action_at is the reader's own clock and sits earlier by up to a full scoring interval. Read that field to react while the moment is still warm.

Status is a rank inside this newsletter, not an absolute score, so a reader who did nothing can be demoted because the audience around them got busier. Two events that look like opposite movements can arrive from one pass without either reader having changed their behaviour.

Only readers with a Commune account are scored, so a subscriber the newsletter knows only as an address never produces this event.

Not the same as subscriber.unsubscribed, which reports the subscription ending. dormant is a reader who went quiet, not one who left.

Delivered as a single HTTPS POST to the consumer's registered endpoint, with the message as the JSON request body. Respond 2xx to acknowledge. Anything else, or a timeout, is retried with backoff, so acknowledge fast and do the work afterwards.