Report Automation

Even though Cello is typically implemented in a fully automated fashion, it does provide the flexibility for you to upload table-based reports confirming purchases or any custom events. These reports can be submitted regularly and in a format of your choosing, as long as all the necessary data is included.

Safe Data Transfer

Cello enables secure data uploads via an Amazon S3 bucket, allowing you and your team to upload data routinely for processing. For specifics on setting up and accessing this feature, kindly contact Cello directly.

Data Requirements

Cello uses these reports to establish a connection between the referrer, who originally shared a referral code, and the referred account. In order to compute rewards and pricing, Cello requires the following data points for each referred account:

• Referred account ID: Facilitates the connection of the Attribution & Event report with the Purchases report.

• Cello Referral Code (UCC): Creates a link between the Referred Account and the Referrer. This referral code can be found in your CRM as a parameter.

• Custom Events: Custom Events depend on the events in customer journey that should trigger rewards & notifications to the referrer. This is often a deal stage like "Demo Done" that is tracked in a CRM.

• Transaction Details: Amount, Currency and further transaction details of referred accounts used to compute rewards and pricing.

This data can be provided via the reports in different approaches depending mainly on your existing signup and purchase processes.

Standard approachTransactions only approachBI based approach

In the standard approach, two reports are provided to Cello.

1. The Attribution & Event report allows Cello to associate the referrer with the referred account via Cello's referral code, and to inform and reward referrers on specific events, e.g., "demo done".

2. The Purchases report allows Cello to reward referrers and calculate Cello's pricing on a regular basis.

Only a Purchases report can be provided to Cello if

• no notifications or rewards on custom events like "Demo done" should be sent to the referrer.

• you are able to attach Cello's referral code directly to the transactions in the Purchases report.

In the case that you have all required data in a central data storage, you can provide a combined report with all data on custom events, transactions also including Cello's referral code to Cello.

For instructions on how to integrate Cello's referral code into your backend using Cello's attribution library, please refer to Attaching referral code to forms.

Sample Data and Reports

A variety of reports can provide event details that will be used for attribution. Below, we have provided two key examples from the standard approach.

Example Data: Event Attribution and Linking

Reports such as this are typically generated from your CRM or BI tool. They enable Cello to associate referred accounts via the referral code with the referrer and potentially attribute certain events within the referee's customer journey.

Example Data: Transactions Attribution

This type of report is usually a standard report provided by your payment tool (like Stripe) or your BI tool. It provides Cello with the transaction details needed to calculate rewards and pricing.

Here's an example of an accepted report. It's worth noting that Cello also accepts standard payment reports exported from Stripe.

Additional information:

• amount: always provide the amount in cents (e.g. Dollar Cents, Euro Cents, ...)