The SUBSCRIBED notification fires when a customer subscribes to an auto-renewable subscription for the first time, or re-subscribes after their subscription has expired. This is the starting point of the subscription lifecycle.
When does it fire?
This notification triggers in two scenarios:
- Initial subscription — a customer purchases an auto-renewable subscription for the first time
- Resubscription — a customer whose subscription has expired subscribes again (distinct from a renewal)
The notification includes a subtype that differentiates between INITIAL_BUY and RESUBSCRIBE.
Payload highlights
The signed transaction info includes the product ID, the subscription group ID, the purchase date, the expiration date, the offer type (if any), and the storefront (country). The signed renewal info shows the auto-renew status and the expected next renewal date.
How Yeethook helps
Yeethook parses the signed JWT payloads (JWS transactions) and formats them into readable Slack messages. Instead of decoding Base64-encoded JWTs, you see the product name, price, country, and subscription period clearly in Slack.
Common use cases
- Track new subscriber acquisition in real-time
- Monitor re-subscription rates for win-back campaign effectiveness
- Alert your revenue team when high-value subscriptions are purchased
- Segment new vs. returning subscribers for analytics