Membership Integration Events
Rivo can send membership lifecycle events to your connected integrations so you can trigger lifecycle flows, dunning journeys, and retention automations outside of Rivo.
This guide covers:
Which membership events are available
Which integrations currently receive each event
What event data is included
Which membership profile properties are kept in sync
How to build reliable membership automations
Where to Enable Membership Events
In your Rivo admin, go to Integrations.
Open your connected integration (for example, Klaviyo, Attentive, or Braze).
Turn on the available membership events in the Custom Events Trigger area.
Save your changes.
Make sure the integration status is set to ON.
If you use webhooks, create membership webhook subscriptions for the membership events you want to receive.
Membership Events You Can Use
Rivo supports these membership lifecycle events:
Membership Signup
Membership Canceled
Membership Pending Cancellation
Membership Payment Failure
Membership Payment Success
Membership Renewal Notice
Membership Successful Rebill
Membership Paused
Membership Billing Skipped
What each event means
Event | When it fires |
Membership Signup | When a customer joins a membership tier |
Membership Canceled | When a membership is canceled immediately |
Membership Pending Cancellation | When cancellation is scheduled for the end of the billing period |
Membership Payment Failure | When a billing attempt fails |
Membership Payment Success | When a previously failed payment is recovered |
Membership Renewal Notice | Before the next billing date (pre-renewal reminder window) |
Membership Successful Rebill | When a billing attempt succeeds |
Membership Paused | When a membership is paused |
Membership Billing Skipped | When the current billing cycle is skipped and the next billing date is moved |
Event Availability by Integration
Not every integration currently receives all membership events.
Event | Klaviyo | Attentive | Braze | Postscript | Merchant Webhooks |
Membership Signup | Yes | Yes | Yes | Yes | No |
Membership Canceled | Yes | Yes | Yes | Yes | Yes |
Membership Pending Cancellation | Yes | Yes | Yes | Yes | Yes |
Membership Payment Failure | Yes | Yes | Yes | No | Yes |
Membership Payment Success | No | Yes | No | No | Yes |
Membership Renewal Notice | Yes | Yes | Yes | No | No |
Membership Successful Rebill | Yes | Yes | Yes | No | Yes |
Membership Paused | Yes | No | No | No | No |
Membership Billing Skipped | Yes | No | No | No | No |
Event Data Included
Membership events include useful context you can use in flow branches and message personalization.
Common membership fields
Most membership events include one or more of the following:
Membership tier name
Attempt number (for billing attempts)
Billing date fields (for renewal and rebill events)
Event timestamp fields (for signup, cancellation, failures, and successes)
Event-specific data highlights
Membership Payment Failure includes failure time and attempt number.
Membership Payment Success includes success time and attempt number.
Membership Renewal Notice includes next billing date and renewal date.
Membership Successful Rebill includes membership tier, billing interval, next billing date, and attempt number.
Membership Paused includes paused time.
Membership Billing Skipped includes skipped time and the new billing date.
Membership Profile Properties (Customer Attributes)
In addition to events, Rivo syncs membership profile properties to supported integrations so you can segment audiences and build always-on lifecycle logic.
Common membership profile properties include:
Rivo Membership Joined Date
Rivo Membership Last Joined Date
Rivo Membership Tier Name
Rivo Membership Status
Rivo Membership Pending Cancellation At
Rivo Membership Next Billing Date At
These are especially useful for:
Segmenting active members vs. canceled members
Building pre-renewal cohorts by upcoming billing date
Creating win-back journeys for recently canceled members
Recommended Membership Flows
1. New Member Welcome Flow
Trigger: Membership Signup
Suggested flow:
Welcome message
Benefits overview
Reminder to log in and use perks
2. Failed Payment Recovery Flow
Trigger: Membership Payment Failure
Suggested flow:
Immediate payment update reminder
Follow-up reminder before next retry
Escalation message before cancellation risk
3. Pre-Renewal Reminder Flow
Trigger: Membership Renewal Notice
Suggested flow:
Reminder that renewal is approaching
Benefit recap
Link to manage payment details
4. Save-the-Member Flow
Trigger: Membership Pending Cancellation
Suggested flow:
Cancellation acknowledgment
Value reminder
Rejoin or retention offer
5. Recovery Confirmation Flow
Trigger: Membership Payment Success or Membership Successful Rebill
Suggested flow:
Confirmation message
“You are still active” reassurance
Next billing date reminder
Best Practices
Turn off duplicate notifications if the same lifecycle email is already sent elsewhere.
Start with your highest-impact events first: signup, payment failure, renewal notice, and successful rebill.
Use profile properties for segmentation and event properties for moment-based messaging.
Test each flow with a real test customer before turning it fully live.
FAQ
Q: What is the difference between Membership Payment Success and Membership Successful Rebill?
Membership Payment Success is for recovered payments after earlier failures. Membership Successful Rebill is for successful billing attempts.
Q: Why do some events appear in one integration but not another?
Event support varies by integration. Use the availability table above as your source of truth.
Q: Can I build flows even if I do not use all events?
Yes. Most stores start with a small set of events and expand over time.
Q: Should I use events or profile properties for segmentation?
Use profile properties for ongoing audience segments and events for trigger-based automations.