Skip to main content

Refer & Earn

Available

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.

See it end to end first

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​

OutcomeMechanism
Acquisition at known costThe reward is only paid after the referee's account is activated
Two-sided incentiveReferrer and referee both earn, so the invite is easy to send and easy to accept
Attribution you can proveThe referral code travels with the signup and is settled server-side
No app release to change the economicsReward values and eligibility are campaign configuration at Cheggout
Works without an appThe 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 RegisterEvent after 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 pointSurfaceAuthenticationNeeds an SDK?
Mobile appCheggout SDK, launched by deep linkSSO from your app sessionYes — Android or iOS
MicrositeHosted web referral centreMobile number + OTP, via your webhookNo
CRM campaignLink sent by WhatsApp, SMS or emailToken in the link, or OTP on arrivalNo

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​

StepWhat it involvesReference
1. Carry the codeAccept referralCode on your signup or apply flow and persist it against the applicationYour systems
2. Open the referral centreDeep link into the SDK, or link to the micrositeEntry points
3. Report activationFire RegisterEvent with eventType: "Referral" when the referee's account goes liveEvent integration
4. Host the OTP webhookOnly for the microsite path — sendSMS, so Cheggout can authenticate a web visitorsendSMS webhook
5. Pull codes for CRMOnly for the CRM pathgetReferralCodeForUser

Steps 4 and 5 are conditional. A publisher doing SDK-only referral needs steps 1–3.

Module surface​

CapabilityStatus
Registering a referral eventAvailable RegisterEvent
Referral code issuance for CRMAvailable getReferralCodeForUser
Microsite OTP authenticationAvailable Publisher-hosted sendSMS webhook
SDK launch by deep linkAvailable Entry points
Referral status and history viewAvailable Rendered inside the Cheggout referral centre
Eligibility and reward valuesTBD Campaign configuration — agreed with Cheggout at onboarding, not self-serve
Referral reporting APITBD No publisher-facing analytics endpoint is published
Reward values are configuration, not code

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​