Cello exports data on an automated basis to create your own reports or import into internal systems. These files can be downloaded in two ways:
  • From the cello Portal by clicking Download in the upper right hand corner
  • From the AWS S3 bucket
This page provides details on the data that is included in these files.

event_details_aggregates-all

The all aggregates files provides total event counts all time by product user for users who have activated (opened) Cello at least once.
ColumnDetails
productuseridThe user id of the referrer (provided by your product on boot)
R_ActiveTotal event count of user opening the Cello referral component
R_SharingTotal event count of user clicking a share button in the referral component
R_RewardTotal event count of referrer being rewarded
NU_ViewsTotal event count of new user views*
NU_Views_UniqueUnique new user views based on anonymized browser attributes*
NU_SignupsTotal event count of new user signups attributed to this referrer
NU_PurchasesTotal event count of new user signups attributed to this referrer

event_details_aggregates-daily

The all aggregates file provides total event counts aggregated by day and by product user for users who have activated (opened) Cello at least once.
ColumnDetails
productuseridThe user id of the referrer (provided by your product on boot)
R_ActiveTotal event count of user opening the Cello referral component
R_SharingTotal event count of user clicking a share button in the referral component
R_RewardTotal event count of referrer being rewarded
NU_ViewsTotal event count of new user views*
NU_Views_UniqueUnique new user views based on anonymized browser attributes*
NU_SignupsTotal event count of new user signups attributed to this referrer
NU_PurchasesTotal event count of new user purchases attributed to this referrer

conv_signups

The signup file contains all signups events based on attributed signups.
ColumnDetails
datetimeTimestamp of the signup, in ISO 8601 format with UTC designator
dateDay of the transaction, used for aggregation and trends
monthMonth of the transaction, used for aggregation and trends
weekWeek of the transaction, used for aggregation and trends, with Monday used as start of week
productuseridThe user id of the referrer (provided by your product)
campaign_uccThe referral code (ucc) of the referrer used for attribution
newuserproductuseridThe user id of the new user that was referred (provided by your product)
statusStatus of the signup, either Included or Excluded*

conv_transactions

The transactions file contains all attributed transaction events with additional fields that Cello has added based on reward calculations.
ColumnDetails
datetimeTimestamp of the transaction, in ISO 8601 format with UTC designator
dateDate of the transaction, used for aggregation and trends
monthMonth of the transaction, used for aggregation and trends
weekWeek of the transaction, used for aggregation and trends, with Monday used as start of week
productuseridThe user id of the referrer (provided by your product)
campaign_uccThe referral code (ucc) of the referrer used for attribution
newuserproductuseridThe user id of the new user that was referred (provided by your product)
amountAmount of the transaction
currencyCurrency of the transaction
intervalThe interval of the transaction e.g. Yearly, Monthly, One Time
statusStatus, for example whether the transaction was rewarded or invalid*
rewardCalculated reward amount for this transaction, based on your campaign*
reward_typeType of reward for this transaction e.g. Percentage, Fixed*
reward_calcPercentage or fixed amount used for rewarding, based on your campaign*

conv_rewards

The rewards file contains all reward events for referrers based on attributed transactions.
ColumnDetails
datetimeTimestamp of the reward, in ISO 8601 format with UTC designator
dateDate of the transaction, used for aggregation and trends
monthMonth of the transaction, used for aggregation and trends
weekWeek of the transaction, used for aggregation and trends, with Monday used as start of week
productuseridThe user id of the referrer (provided by your product)
campaign_uccThe referral code (ucc) of the referrer used for attribution
amountCalculated amount of the reward, based on campaign rules*
currencyOriginal currency of the reward
intervalInterval of the reward e.g. monthly, one_time
invoice_statusWhether on not these rewards were excluded from invoices*
amount_referrerCalculated amount for the referrer based in the referrer currency
currency_referrerCurrency of the referrer reward
xrate_referrerExchange rate used for conversion of referrer reward
amount_targetReward in target currency, used for invoicing depending on customer setup
xrate_targetExchange rate used to calculate target currency
amount_eurReward in EUR, used for invoicing depending on customer setup
xrate_eurExchange rate used to calculate EUR currency

ignore_list

The ignore list file lists all of the specific users who are ignored. Cello, by default, ignores internal users of your company and Cello test events across all exports and dashboards in the portal. This behavior can be configured on demand.
ColumnDetails
productuseridThe user id of the ignored user (provided by your product)
ignoreFlag, usually 1 to indicate this user is ignored

Notes on Specific Metrics

Views and Unique View Counts

Cello aggregates views using anonymized hashed browser attributes. Views are counted as total counts. Unique Views of new users are counted based on these anonymized attributes.

Reward Calculations

Rewards are calculated in Cello at the time of attribution. The reward calculation is is first done on the transaction based on the campaign configuration. Rewards are then created for referrers and tracked separately based on additional rules, for example in most cases a yearly transaction would be spaced out and rewarded on a monthly basis to the referrer.

Transaction Status

While in most cases transactions are reward be invalid for a number of reasons and are then marked as invalid and not rewarded. Transactions can also be in a review state, marked as In Review.

Signup Status

Upon transactions being rejected for specific referrers, all signups are excluded for the referrers. This includes ignoring retroactive history of these referrers to ensure dashboards do not show misleading spikes in the data.