What it does
When Stripe sends a subscription created, updated, cancelled, or payment-failed event, syncs the state to the user profile and account lifecycle stage, so segmentation, retention, and reporting always reflect actual billing reality.
You get
user and account lifecycle state kept in sync with real Stripe events
How it works
Hold the billing facts
create_attributeOn each person: subscription status of active, trialing, past due, cancelled or none, the plan tier, current monthly revenue, the start date, the next renewal date, and whether a payment has failed. All sourced from Stripe and refreshed on every webhook.
Apply every Stripe event
Create WorkflowOn each webhook it reads the event, matches the Stripe customer to a user and creates one where they checked out without signing up, updates every billing field, moves the lifecycle stage, with a new subscription making them a customer, a cancellation churned and a failed payment at risk, emits events under your own names so journeys do not depend on Stripe's, and marks the account churned when its last seat goes.
Prove the two agree
Build DashboardThe share of users whose status matches Stripe, which should be all of them, failed webhook deliveries, profiles that disagree with Stripe, which means a sync bug, and monthly revenue computed from profiles against Stripe's own figure, which should match within 1%.
Ready to run this recipe?
Tell Blu what you need. It builds the segment, content, journey, and dashboard in minutes.
Sign up free
