Skip to main content
To complete the conversion tracking and reward referrers, you will need to send Cello purchase events. A purchase event is sent when a user pays for a subscription or a product.
After sending purchase events, check Integration Status to confirm Purchases tracking is Connected. For per-event detail and to troubleshoot any field validation errors, open the Event Feed in the Cello Portal.

Prerequisites

Before you can send Cello purchase events, make sure you are already:
Attribution based on organization levelIf the buying persona is the organization and you want to attribute purchases at the organization level, always provide the ID of the organization in the parameter payload.newUserId
If you are providing discounts to new users, they need to be applied at the point of creating a subscription in your subscription platform

Track purchase events with Webhooks

Depending on which payment gateway you’re using, we offer webhooks for the following:

Stripe Webhook

Send events using Stripe Webhook

Chargebee Webhook

Send events using Chargebee Webhook

Track purchase events with Cello API

If you’re not using any of the gateways listed above, you can also send purchase events using Cello API POST /events API endpoint. Here are the 2 events you will need to send:

invoice-paid

This event is sent every time a transaction based on the provided subscription is successful or a new user buys a one-time plan, a license or something similar.
Here are the properties you can include when sending a invoice-paid event: Full API referrence for POST /events API endpoint can be found here.

charge-refunded

This event is sent if the payment of the new user was refunded. When Cello receives this event, it automatically cancels any pending reward for that transaction.
Here are the properties you can include when sending a charge-refunded event: Full API referrence for POST /events API endpoint can be found here.