Skip to main content
This guide provides a migration plan for transitioning from referral program platforms such as PartnerStack, Aklamio, Rewardful, and FirstPromoter to Cello. It covers both user referral systems and partner program management.

​
STEP 1: Implement the standard Cello onboarding process

Before user referrals and partners can be migrated, the Cello setup needs to be done following our standard onboarding process. This allows link creation and correct attribution of referrals for users and partners in the future. The steps are:
  1. Integration of the referral component into the customer’s system
  2. Configuration of referrer and new user experience, including rewards structure, emails and announcement notifications
  3. Connecting attribution - including new user landing page, payment gateway integrations and events testing
  4. For Partner Campaign: Cello’s set-up of the additional affiliate campaign
  5. Testing
👉 See our Quickstart for reference.

​
STEP 2: Enablement of exiting users and partners for Cello

​
For User referrals

By bring Cello live in your production environment, referral links for user will be automatically created as soon as your users boot Cello for the first time. The first boot happens on the first login after the Go-Live of Cello inside your product.

​
For Partner enablement

Two options exist to create links for your partners. In both cases your partners will receive an invite email including a signup link. Following this link, partners can choose to sign up via email or Google SSO.
  1. Self-serve enablement: You can simply add all partners via the Partner users page from inside the Cello portal. Partners can be added one-by-one and assigned to pre-created campaigns.
  2. Cello supported upload: If you want to run a bulk creation of partner links, please reach out to Cello with a report following the below structure. The Cello team will upload and create the partner links accordingly. Partners will receive automated invite emails.

​
STEP 3: Data Migration of referrals

  1. Retrieving data following the process of the previous vendor.
  2. [Optional]: Past referrals where referrer received the full reward As no additional rewards need to be processed, migrating this data is optional and only for displaying the history of the referral program in the Cello analytics portal.
    1. Option 1: Cello API - All past signups and transaction events can be shared in fully automated manner with Cello leveraging the Cello API. Details on enabling the API transfer and the required format can be found in the documentation from Generic Events API
    2. Option 2: Manual upload via attribution reports - Extract past signups and transaction events from current platform. Fill and share the data via attribution reports.
  3. Ongoing referrals where referrers should receive rewards due to renewals Cello can take over rewarding for renewals if it is applicable in your current reward structure:
    1. Option 1: Automated attribution with Cello Recommended - using Generic Event API to retrieve and attach the tracking parameters
    2. Option 2: Continuous manual attribution - using manual attribution via reports
  4. Future referrals:
    1. Referral via previous links: Simply follow outlined steps for Ongoing referrals
    2. Referral via Cello links: If referrals come in via Cello referral links, the attribution and rewarding process will be completely automated as to your setup of Cello

​
Migration options

​
Option 1: Automated attribution with Cello

For ongoing referrals, the referred user is already marked as referral in your system according to the attribution process of the previous vendor. To enable automated rewarding by Cello, you need to ensure that the required Cello tracking parameters are attached to the referred user. The attachment of the tracking parameters automatically triggers new events to be transferred to Cello. The following tracking parameters need to be attached:
  • cello-ucc: You can retrieve the Cello referral code (ucc) for any user via our Referral Codes API or reach out Cello for a manual mapping report.
  • productUserId of the referred user: This is your internal product user id of the referred user with which the new user would also boot Cello.
Where to add the tracking parameters depends on your setup of Cello:

​
Option 2: Continuous manual attribution

Follow weekly the process for manual attribution or share reports regularly with Cello.