Loyalty Profile Updated Webhook
The Loyalty Profile Updated webhook lets you keep another system in sync when a customer’s loyalty profile changes in Rivo.
Use this guide to understand which updates trigger the webhook, how point and credit adjustments behave, and what to expect when you use single, batch, or CSV-based updates.
When the Webhook Fires
Rivo sends the Loyalty Profile Updated webhook for an individual customer when one of these loyalty profile values changes:
Points balance
Credits balance
Loyalty status, such as member, guest, or excluded
Date of birth
The webhook is sent per customer. If 10 customers are updated through a path that triggers the webhook, you should expect one webhook per updated customer.
Point and Credit Updates
Point and credit updates can affect this webhook, but the behavior depends on how the update is made.
Single Point-Event Requests
When you create a point event for one customer through the single point-event endpoint, Rivo updates that customer’s balance and sends Loyalty Profile Updated for that customer.
If you call the single endpoint repeatedly in a loop, each successful request is handled separately. For example, 50 successful single requests for 50 customers can send 50 Loyalty Profile Updated webhooks.
Batch Point-Event Requests
When you create point events through the batch point-event endpoint, Rivo creates the valid point events and refreshes balances for the affected customers in bulk.
The batch endpoint is optimized for bulk updates and does not send Loyalty Profile Updated once for every event in the request.
Use the batch endpoint when your priority is efficient bulk balance updates. Use single point-event requests when your integration depends on per-customer Loyalty Profile Updated webhooks for each adjustment.
CSV Point or Credit Imports
CSV imports also update customer balances in bulk. Like batch point-event requests, they are designed for large updates and should not be used when another system needs a Loyalty Profile Updated webhook for every imported row.
Customer Profile Updates
Updating a customer’s date of birth or loyalty status can send Loyalty Profile Updated for that customer.
Changes to profile details such as name or email are not part of the Loyalty Profile Updated trigger conditions. If your integration needs to react to those kinds of customer profile changes, use the customer update events that match that workflow instead.
Choosing the Right Update Method
Use this quick guide when deciding how to update customer loyalty data:
Use single point-event requests when each successful customer adjustment should send a Loyalty Profile Updated webhook.
Use batch point-event requests when you need to update multiple customer balances efficiently and do not need this webhook per event.
Use CSV imports for large operational imports where webhook delivery per row is not required.
FAQ
Does the webhook fire once per customer or once per request?
For paths that trigger the webhook, it is sent per updated customer. A single request for one customer sends one webhook for that customer.
Will a loop of single point-event requests send multiple webhooks?
Yes. Each successful single point-event request updates one customer’s balance and can send that customer’s Loyalty Profile Updated webhook.
Will the batch point-event endpoint send one webhook per event in the batch?
No. The batch endpoint refreshes balances in bulk and does not send Loyalty Profile Updated once for every event in the request.
Will a CSV import send this webhook for every imported row?
No. CSV imports are bulk updates and should not be used when your integration requires this webhook for each row.
Do name or email changes trigger this webhook?
No. Loyalty Profile Updated is for loyalty profile changes such as balances, loyalty status, and date of birth.
Where can I test a webhook endpoint?
You can send a test webhook from Settings > Webhooks in Rivo. For setup and troubleshooting steps, see Test Your Webhook Endpoint.