Manual Attribution

​

When to Manually Attribute Referrals

1. Technical Glitches: If you encounter technical issues or glitches that prevent automated attribution, manual attribution allows you to override these challenges.
2. User Disputes: In cases where users claim they referred someone but the system did not capture it correctly, manual attribution provides a resolution path.
3. Custom Scenarios: For unique situations or custom referral setups, manual attribution offers a tailored solution.

​

How to Manually Attribute Referrals

• Stripe webhook only
• Chargebee webhook only
• Cello API & Webhook
• Cello API only

1. Customer gets cello_ucc of referrer from the Cello Portal and retrieves cello_ucc of referrer and new_user_id (former product_user_id) new user from their own system. If data cannot be found, please reach out to Cello.
2. Customer adds cello_ucc of referrer and new_user_id (former product_user_id) ID of new user to the existing Stripe customer of new user in Stripe.
3. Cello receives a customer.updated event from Stripe for the customer.
4. If there were already paid invoices, please resend the past invoice.paid events of the new user to Cello. This can be done by:
   1. Go to the transaction
   2. Select the invoice.paid event in the feed at the bottom
   3. Click View event details
   4. Check webhook attempts and resend the event

1. Customer gets cello_ucc of referrer from the Cello Portal and retrieves cello_ucc of referrer and new_user_id (former product_user_id) ID of new user from their own system. If data cannot be found, please reach out to Cello.
2. In Chargebee, you add cello_ucc of referrer and new_user_id (former product_user_id) of new user to the metadata of the new user’s Chargebee customer.
3. We automatically receive a customer_changed event via the webhook.
4. 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 Chargebee manually.

1. Customer gets cello_ucc of referrer from the Cello Portal and retrieves new_user_id ID of new user from their own system. If data cannot be found, please reach out to Cello.
2. 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.
3. 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. The report templates will be provided by Cello Support team.

1. Customer gets cello_ucc of referrer from the Cello Portal and retrieves new_user_id ID of new user from their own system. If data cannot be found, please reach out to Cello.
2. 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.
3. 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. The report templates will be provided by Cello Support team.

​

Contact Support