Title
Create new category
Edit page index title
Edit category
Edit link
Attribution with Chargebee
This guide walks you through the steps required to attribute referrals if your payment gateway is Chargebee and includes:
1. Track conversions on your landing page
to your Home page by including the following script in the <head> tag to track attributions and show New user banner.
2. Track signups with Chargebee
When a signup finally happens, you need to make sure that a ucc code, identifying the referrer, is saved to the new user record and passed to Chargebee upon customer creation.
Access Ucc code during signup
Ucc is present in the URL of your Home page when a new user is redirected to it from the invite link and in the cookies, added by the Attribution library.
To access the ucc during signup, you can use the Attribution library JS method getUcc().
Here is how to do it:
Add the following javascript code before any of the calls to the library to avoid race conditions.
To make sure your referrers get rewarded when a new user signs up in the mobile app, follow this guide on Mobile attribution to track mobile app signups.
Now the next step depends on your flow!
4. Send signup and transaction events to Cello
Choose one of the 2 options depending on your scenario:
I create Chargebee customer at signup - Use only Chargebee Webhook integration if you create Stripe customer at the point of signup
I don't create Chargebee customer at signup - Use a combination of Cello API and Chargebee Webhook integration if you don't create Stripe customer at signup and only at purchase
Pick your scenario:
Use this option if you create Chargebee customer at the point of signup
Add metadata to Chargebee customer
Chargebee webhook supports custom fields (CF). You can choose to use metadata or custom fields to add referral data to the event. Learn more about custom fields in the Chargebee documentation
Next, at the point when you create a customer in Chargebee, make sure that you add the following metadata to the Chargebee customer:
cello_ucc - ucc, a referral code identifying the referrer
new_user_id - a unique user ID in your system, identifying the new user who just signed up. This should be the same ID (productUserId) you will use to boot the Referral component, when this user logs into your app
new_user_organization_id (optional) - add this, if your referrers can refer an organization rather then a single user and you want to reward based on that.
Below is an example for a NodeJS app, illustrating how to include during customer creation.
Add Chargebee Webhook
You will add a Webhook to your Chargebee configuration to connect Chargebee and Cello. This can be done in both sandbox and production environments separately.
💡 Switch environments in the Portal using a switch to configure Sandbox and Production separately.


To set up:
Log in to Cello Portal and go to Webhooks to get your endpoint URL and authentication details.
Log in to your Chargebee dashboard.
From the sidebar, select Settings > Configure Chargebee and click on Webhooks.
Click on "+ Add Webhook" and fill out the Endpoint URL provided based on the environment.
Select the events you want to send under "Events to Send." Select the events
Customer Created, Customer Changed, Customer Deleted
Payment Succeeded, Payment Refunded, Payment Failed
To secure the webhook, select Protect webhook URL with basic authentication and add the
usernameandsecretprovided in the Cello Portal.Be sure to select Exclude card Information from webhook call
Finally click Create to enable the webhook

Endpoint created 🎉
If you don't create Stripe customer at signup and only at purchase, then you will need to use Cello API to send signup and Chargbee Webhook to send transaction events
Use Cello API to send signup events
To send signup events, use Cello API /events endpoint.
Use the Domain base URL that corresponds with the environment.
Endpoint URL | Environment |
|---|---|
| Dev and Stage |
| Prod |
💡 Switch environments in the Portal using a switch to get the credentials

Authenticate
To use the Cello API, you need to authenticate the request using an accessToken which is passed in the Authorization request header.
To obtain them you will need accessKeyId & secretAccessKey which you can get from your product dashboard on Access Keys page.

Obtain accessToken & refreshToken
Refresh accessToken
Send signup events
new-signup - the new user signs up for your product
Add metadata to Chargebee customer
Chargebee webhook supports custom fields (CF). You can choose to use metadata or custom fields to add referral data to the event. Learn more about custom fields in the Chargebee documentation
Next, at the point when you create a customer in Chargebee, make sure that you add the following metadata to the Chargebee customer:
cello_ucc - ucc, a referral code identifying the referrer
new_user_id - a unique user ID in your system, identifying the new user who just signed up. This should be the same ID (productUserId) you will use to boot the Referral component, when this user logs into your app
new_user_organization_id (optional) - add this, if your referrers can refer an organization rather then a single user and you want to reward based on that.
Below is an example for a NodeJS app, illustrating how to include during customer creation.
Connect Chargebee Webhook
To set up:
Log in to Cello Portal and go to Webhooks to get your endpoint URL and authentication details.
Log in to your Chargebee dashboard.
From the sidebar, select Settings > Configure Chargebee and click on Webhooks.
Click on "+ Add Webhook" and fill out the Endpoint URL provided based on the environment.
Select the events you want to send under "Events to Send." Select the events
Customer Created, Customer Changed, Customer Deleted
Payment Succeeded, Payment Refunded, Payment Failed
To secure the webhook, select Protect webhook URL with basic authentication and add the
usernameandsecretprovided in the Cello Portal.Be sure to select Exclude card Information from webhook call
Finally click Create to enable the webhook
