How to Use Reditus to Launch an In-App Referral Program

The short answer: if your B2B SaaS makes less than $60K of ARR through referrals and affiliates combined, a full in-app referral program fits on Reditus Growth at $149 a month, or $99 a month on an annual contract, and Reditus puts the tracking install at under 30 minutes, with the widget on top (checked on 26 October 2026 on the pricing page). The steps: install the tracking script, fire the signup snippet, connect Stripe, set both sides' rewards, load the widget with a token signed on your server, link to it from your emails, grant the friend's benefit by webhook, and settle the cookie question before launch.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

Satisfied users recommend you in conversations you never see; an in-app referral program gives them a link and a reason, and gives you a record. Reditus runs it on the same script and cookie as its affiliate program, with one referral program per company, per its referral setup guide. What the product is and costs overall is in the Reditus glossary entry.

Price the reward before anyone writes code:

1. Compare it with what you already pay for a customer. Reditus's setup guide cites a customer paying €150 per new paid client referred. For example, against an affiliate paid 20% for 12 months on a €200 a month plan, 0.2 x €200 x 12 = €480, so the €150 referral reward costs under a third as much. Paid in cash through Reditus by card, it becomes €150 x 1.05 = €157.50 with the payout fee.
2. Reuse the channels you already send. Lifecycle emails, in-app messages and invoice emails can all carry a deep link that opens the widget, so the program does not need a new channel to be seen.
3. Write down the baseline. New paid accounts per month for the last three months. The referral program is judged against that figure, not against its own share of signups.

What you need

• A developer with access to your backend: the widget needs a token generated there.
• Stripe, or a developer to send payments through the Payments API, which Reditus estimates at about four hours, per its getting started guide.
• A Reditus account: the 14-day Growth trial needs no card, and keeping the program after it needs a paid plan, per the pricing FAQ.

Step 1: Install the tracking script

Put it in the header of your main domain and of every subdomain in the funnel, including the app subdomain where people sign up; Google Tag Manager works, per the getting started guide. It records that a visitor arrived through a referral link. If you already run a Reditus affiliate program, Steps 1 to 3 are done.

Step 2: Fire the signup snippet

Add the snippet to your code so it runs once, right after a successful signup, on every signup method you offer: email form, Google sign-in, invitation. The guide's most common setup mistake is covering only one route, such as a Calendly booking, so signups through the form are never credited.

Step 3: Connect payments

In the installation tab, click Connect Stripe and approve it. Check that your checkout passes the customer's email to Stripe, because that is how Reditus matches a payment to the referral. The tab shows pending installation until all three steps work, and its test link checks the script.

Step 4: Set the rewards and the terms

In the referral program configuration, set what the advocate earns, what the referred user gets and the rules. The setup guide recommends rewarding both sides and keeping the terms to one visible sentence inside the widget. Credits, discounts and a longer trial work as rewards; cash is paid like affiliate payouts.

Step 5: Load the widget with a signed token

Your backend signs a JWT with the Reditus product secret, which must never reach the browser, per the authentication doc. The frontend then calls gr("loadReferralWidget", ...) with the product ID, that token, the user's details and an optional language: English, French, Spanish, German, Portuguese, Italian or Polish, per the loading doc. If the referral flow must look native, the Referral Program API lets you build your own interface instead.

Step 6: Put it where users already look

Attach window.referralWidget.show() to a button in the top navigation, the settings menu or a referrals page. Then use the deep link: adding ?reditus-show-referral=program to any app URL opens the widget, and referrals or rewards opens those tabs, per the modal doc. Put that link in the email after a user's first real result, after a milestone and at renewal, which are the moments the setup guide recommends.

Step 7: Give the friend something too

Reditus does not apply the referred user's benefit inside your product; the rewards doc says that logic is yours. Subscribe a webhook to lead.created, whose documented uses include generating a Stripe discount for the new user, and check the X-Signature header on each request, per the webhooks doc.

The cookie question, for EU sites

Reditus says its referral cookie typically needs no consent because it only records whether a signup came through a link and builds no visitor profile, an opinion it bases on Dutch law and a Dutch lawyer, adding that it may not hold in every country, Germany included, per its cookie article. The rule underneath is Article 5(3) of the ePrivacy Directive: storing information on a user's device needs consent unless it is strictly necessary for a service the user explicitly requested; the Dutch Telecommunicatiewet adds an exemption, in Article 11.7a, for measuring a service with little or no privacy impact. Decide with counsel which applies to you. One consequence is mechanical: if your banner holds the script back until consent, visitors who decline cannot be credited to an advocate.

An agent step: a weekly lead review

The fraud checks on same IP and same email apply to the affiliate program, not to in-app referrals, per Reditus's fraud article. An agent can fill that gap. Once a week it reads new leads through the Referral Program API's List Leads endpoint and flags any whose email domain matches the advocate's company or a disposable provider. A person reviews each flag; only then does the agent call Reject Lead, which requires a reject reason and also rejects pending rewards from that lead.

What the docs warn about

• Late payout overviews. Reditus creates payouts on the 1st and pays advocates and affiliates only after you pay its overview; an unpaid overview turns overdue the following month, per the payouts article.
• Expecting a second program. Each company gets one in-app referral program, per the setup guide.

When referrals start to pay

Reditus counts referral ARR toward the same cap as affiliate ARR, and its billing help says crossing the threshold moves you to the next plan: past $60K, that is Scale Up at $399 a month on a 12-month contract, so a referral program that succeeds takes the software line from $1,188 to $4,788 a year (checked on 26 October 2026).

Test it for free before that matters. Send the deep-link email to half of the users who reached their first result last month and not to the other half, then compare new paid accounts referred by each half after 60 days. If the halves match, the widget is collecting credit for word of mouth that was already happening; if advocates share but few friends sign up, the setup guide's advice is to look at the welcome offer first.

FAQ

Which Reditus plan includes the in-app referral program?

Every paid plan from Growth, with unlimited advocates and no referral feature held back for a higher plan, per the setup guide. You can build it during the free trial.

Can the referral program run beside an affiliate program?

Yes, and Reditus recommends launching both: users go into the referral program, agencies and consultants into the affiliate program. Both share one script and one cookie, so the last link clicked before signup takes the credit, and after signup the referral is never reassigned, per the fraud article.

Does the widget speak the user's language?

Yes, in seven languages set by the lang parameter, per the loading doc. The Reditus dashboard itself is in English only.