Refer & Earn
Refer & Earn turns your existing customers into an acquisition channel. A customer shares a referral code; a friend signs up or completes a qualifying action with that code attached; both sides earn a reward once the referee's account is activated.
The module runs independently of every other Cheggout module. You can integrate referral without the marketplace, scratch cards or advertisement.
Interactive journey walks both sides of a real referral — referrer, share, signup, activation, reward — in nine steps. It is the fastest way to understand what you are building before reading the contracts.
Why it works
| Outcome | Mechanism |
|---|---|
| Acquisition at known cost | The reward is only paid after the referee's account is activated |
| Two-sided incentive | Referrer and referee both earn, so the invite is easy to send and easy to accept |
| Attribution you can prove | The referral code travels with the signup and is settled server-side |
| No app release to change the economics | Reward values and eligibility are campaign configuration at Cheggout |
| Works without an app | The microsite and CRM paths need no SDK at all |
The lifecycle
Two things are worth pinning down before you design anything:
- You own activation. Cheggout does not know when an account becomes real. The referral only
converts when your backend fires
RegisterEventafter activation succeeds. - The code travels on your funnel. Cheggout issues the code, but it is your signup flow that has to carry it from the share link through to activation.
The three entry points
A customer can reach the referral experience three ways. They are not alternatives to choose between once — most publishers run more than one.
| Entry point | Surface | Authentication | Needs an SDK? |
|---|---|---|---|
| Mobile app | Cheggout SDK, launched by deep link | SSO from your app session | Yes — Android or iOS |
| Microsite | Hosted web referral centre | Mobile number + OTP, via your webhook | No |
| CRM campaign | Link sent by WhatsApp, SMS or email | Token in the link, or OTP on arrival | No |
Each is specified on Entry points. In short:
For the CRM path you need each customer's referral code up front, so you can bake it into the
campaign message. That is what
getReferralCodeForUser is for.
What you build
| Step | What it involves | Reference |
|---|---|---|
| 1. Carry the code | Accept referralCode on your signup or apply flow and persist it against the application | Your systems |
| 2. Open the referral centre | Deep link into the SDK, or link to the microsite | Entry points |
| 3. Report activation | Fire RegisterEvent with eventType: "Referral" when the referee's account goes live | Event integration |
| 4. Host the OTP webhook | Only for the microsite path — sendSMS, so Cheggout can authenticate a web visitor | sendSMS webhook |
| 5. Pull codes for CRM | Only for the CRM path | getReferralCodeForUser |
Steps 4 and 5 are conditional. A publisher doing SDK-only referral needs steps 1–3.
Module surface
| Capability | Status |
|---|---|
| Registering a referral event | Available RegisterEvent |
| Referral code issuance for CRM | Available getReferralCodeForUser |
| Microsite OTP authentication | Available Publisher-hosted sendSMS webhook |
| SDK launch by deep link | Available Entry points |
| Referral status and history view | Available Rendered inside the Cheggout referral centre |
| Eligibility and reward values | TBD Campaign configuration — agreed with Cheggout at onboarding, not self-serve |
| Referral reporting API | TBD No publisher-facing analytics endpoint is published |
How much the referrer and referee earn, how many referrals one customer may claim, and any minimum qualifying behaviour are all set on the Cheggout campaign for your channel. Agree them during onboarding — they are not parameters you send on the API.
Next
- Interactive journey — both sides of a referral, step by step
- Entry points — SDK, microsite and CRM
- Event integration — reporting the conversion
getReferralCodeForUsersendSMSwebhook