Implementation Testbook

Use this testbook to ensure a smooth transition when taking your integration live.

​

Test the Referrer Experience

​

1. Check the Referral component in your app

Sign into your website and look for the Cello referral component:

• Expected sharing options are visible in the Referral component Invite tab
• Referral component not interfering with the UI/UX of your app?

​

2. Check the notification badge

Copy the referral link and paste it on a new tab/browser.

• A notification badge appears on the Cello launcher (example below) after the invite link has been shared and opened

​

3. Check the copy in the Referral component

Review the text in the Referral component to make sure its accurate.

• The offer on the Invite tab is accurate
• Information on the how-it-works page, including the offer, is accurate

​

4. Check the available payout methods

Click on Rewards tab and click “Add payment details”.

• The payout methods match what you intend your referrers to use.

​

5. Check logout of your app and Referral component shutdown

Logout of your application

• Referral component should no longer be showing if the referrer is logged out of your application

​

Test the New User Experience

​

1. Check Landing page and New user banner

Copy the referral link from your referrer account and paste into an Incognito Browser.

• User is redirected to the correct landing page
• The new user banner is shown (if applicable)
• After clicking on the CTA in the banner, user is redirected to the correct signup page

​

2. Check if Personalization is set up properly

If you have added personalization, then open an invite link and navigate to your landing page.

• The first name of the referrer is shown on the landing page or new user banner

​

3. Check that the correct discount is applied at signup

If you are offering a discount for the new user, without doing an actual transaction or signup, check if you are able to navigate to your check-out page.

• The discount is reflected at the time of checkout

​

4. Check that Attribution library is correctly installed on your landing pages

Check that the Cello Attribution library is installed on your landing page for new users. Open dev tools with → right click on landing page → inspect → open Elements tab → search for Cello.

• We expect to see this for prod: https://assets.cello.so/attribution/latest/cello-attribution.js
• We expect to see this for sandbox: https://assets.sandbox.cello.so/attribution/latest/cello-attribution.js
• The script tag for attribution library should containtype=module

​

Test Sign-up and Transactions

​

1. Check Payment Integrations

Payment Gateway Integrations have been set-up, and are using proper secrets and credentials.

• You are using the correct Webhook URL for the right environment
• You are using the correct Webhook Secret for the right environment

​

2. Check that direct and indirect signup is working properly

There are different flows that result with a new user signup that can be attributed to the referrer. Direct signup: Referrer shares an invite link → New user opens the link and goes directly to sign up Indirect signup: Referrer shares an invite link → New user opens the link → New user starts navigating around the website → New user goes to sign up Check both flows and determine if:

• New user signup is attributed to the referrer after a direct signup
• New user signup is attributed to the referrer after an indirect signup
• New user signup is attributed to the referrer after returning new user signs up
• The appropriate notification or reward (if applicable) is displayed correctly for the referrer in the Referral component

Based on your payment gateway you should check:

• Stripe/Chargbee: customer.created and customer.updated event is sent to Cello and metadata was added to the customer object in the payment platform
• Other (using Cello API): Event is sent to Cello and ucc along with the other information is stored in your database

​

3. Check that the New user discount is applied correctly

Once new user is created and is in the website, navigate to check-out page, Subscriptions or Upgrade Plan.

• The discount is reflected at the time of checkout
• The discount is applied correctly if the new user ends on a monthly vs an annual subscription

​

4. Check that New user can move to / subscribe to a paid plan and its properly attributed and passed to Cello

Buy a paid plan / subscription with the New user and check if it has been passed through to payment gateway and further to Cello. Depending on the integration you have chosen, perform the following checks: Stripe / Chargebee payment gateway

• New user is moved to paid plan after buying a subscription and the correct discount is applied
• In the metadata of the customer, the cello_ucc and product_user_id should be added. The product_user_id is your internal identifier of the new user.
• Stripe/Chargebee events showing successful / delivered logs when inspected
• The appropriate reward is displayed correctly for the referrer in the Referral component

Other payment gateway (Cello API)

• Transactions are sent to Cello as outlined in this guide

Report automation

• New user is moved to paid plan after buying a subscription and the correct discount is applied
• Generate a report that you will be sending to Cello. The report should contain cello_ucc and product_user_id should be added. The product_user_id is your internal identifier of the new user.
• The appropriate reward is displayed correctly for the referrer in the Referral component

​

Test mobile signup attribution

If your users can signup directly in the app, you need to make sure that these signups are attributed to referrers. Usual flow would be: Referrer send and invite link → New user opens the link in mobile → New user downloads the mobile app → New user signs up in the app. Check this flow and determine if:

• If applicable, New user sees the dedicated referral landing page on mobile with either a discount and personalization.
• New user signup is attributed to the referrer after a direct signup
• Based on your payment gateway you should check:
  • Stripe/Chargbee: customer.created and customer.updated event is sent to Cello and metadata was added to the customer object in the payment platform
  • Other (using Cello API): Event is sent to Cello and ucc along with the other information is stored in your database
• Check that New user can move to subscribe to a paid plan and its properly attributed and passed to Cello. See same section for Web for more details.

​

Test mobile app implementation

Check the Referral component in your app:

• Referral component opens and loads after clicking on the dedicated button or link in your app
• All copy and reward information in the referral component is correct.
• Referral component closes properly