At Cello, we understand that there may be instances where automated referral attribution doesn't work as expected. In such cases, our platform provides the flexibility to manually attribute referrals to ensure that your users receive the proper rewards for their efforts. This guide will walk you through the steps of manually attributing referrals within the Cello platform.
When to Manually Attribute Referrals
Technical Glitches: If you encounter technical issues or glitches that prevent automated attribution, manual attribution allows you to override these challenges.
User Disputes: In cases where users claim they referred someone but the system did not capture it correctly, manual attribution provides a resolution path.
Custom Scenarios: For unique situations or custom referral setups, manual attribution offers a tailored solution.
How to Manually Attribute Referrals
Customer gets
cello_uccof referrer from the Cello portal and retrievescello_uccof referrer andnew_user_id(former product_user _id) new user from his own system. If data can not be found, please reach out to Cello.Customer adds
cello_uccof referrer andnew_user_id(former product_user_id) id of new user to the already existing Stripe customer of new user in StripeCello receives a customer.updated event from the Stripe of the customer
If there were already paid invoices, please re-send the past invoice.paid events of the new user to Cello. This can be done by:
Go to the transaction
Select the invoice.paid event in the feed at the bottom
Click view
event detailsCheck on webhook attempts and resend the event
Customer gets
cello_uccof referrer from the Cello portal and retrievescello_uccof referrer andnew_user_id(former product_user_id) id of new user from own system. If data can not be found, please reach out to Cello.In Chargebee, you add
cello_uccof referrer andnew_user_id(former product_user_id) of new user to the metadata of the new user's Chargebee customerWe automatically receive a customer_changed event via the webhook
If there were already payments from the new user, you need to resend the past payment_succeeded events via the webhook. You can trigger this inside the Chargebee manually.
Customer gets
cello_uccof referrer from the Cello portal and retrievesnew_user_idid of new user from own system. If data can not be found, please reach out to Cello.Customer resends the signup event manually via the Cello API. Fields are filled as in the automated Cello API events. The detailed documentation can be found in the Example Requests.
To add the parameters to the metadata in your payment gateway and resend past transactions, follow step 2-4 from the tab applicable for your payment gateway.
In case Cello API events can not be resend via API, manual reports can be provided to Cello. The reports need to contain equivalent information as the specific event. Exemplary reports can be found in Sample Data and Reports
Customer gets
cello_uccof referrer from the Cello portal and retrievesnew_user_idid of new user from own system. If data can not be found, please reach out to Cello.Customer resends the signup event manually via the Cello API. Fields are filled as in the automated Cello API events. The detailed documentation can be found in the Example Requests.
Customer resends past transaction events manually via the Cello API. Fields are filled as in the automated Cello API events. The detailed documentation can be found in the Example Requests.
In case Cello API events can not be resend via API, manual reports can be provided to Cello. The reports need to contain equivalent information as the specific event. Exemplary reports can be found in Sample Data and Reports
Contact Support
If you encounter challenges or have questions during the manual attribution process, our support team is here to assist you. Reach out to us via support@cello.so with detailed information about the referral in question, and we'll promptly assist you in resolving the matter.