The DID_CHANGE_RENEWAL_STATUS notification fires when a customer changes their auto-renew preference — either turning it off (signaling intent to cancel) or turning it back on (re-enabling auto-renewal).
When does it fire?
This notification triggers in two scenarios:
- Auto-renew disabled (subtype
AUTO_RENEW_DISABLED) — the customer turned off auto-renewal, meaning the subscription will expire at the end of the current period - Auto-renew enabled — the customer re-enabled auto-renewal before the subscription expires
Payload highlights
The signed renewal info shows the new auto-renew status, the current product ID, and the expiration date. This lets you know exactly when the subscription will end if auto-renew stays off.
How Yeethook helps
This is an early warning signal for churn. When a customer disables auto-renew, you have a window before expiration to take action. Yeethook delivers this notification to Slack immediately, giving your retention team time to respond.
Common use cases
- Detect churn risk early when subscribers disable auto-renew
- Trigger win-back campaigns before subscriptions expire
- Track the ratio of disabled vs. re-enabled auto-renewals
- Monitor the effectiveness of retention efforts