Webhooks: adding benefits to referrals

Webhooks let Reditus tell your own systems the moment something happens in your program. Most customers use them for their in-app referral program: when a referred person comes in, the webhook tells you which user recommended which other user, so you can apply the benefit your program promises, such as a discount or an extra trial, in your own product. Webhooks are included on every plan.

The webhook events

Reditus sends five events:

• In-app referral program: advocate.created, lead.created and reward.created.
• Affiliate program: partnership.accepted and referral.created.

What each event sends, and how to set up your endpoint, is in the developer documentation.

Grant a benefit when a lead comes in

1. Decide what you give, and to whom: a discount, an extra trial period, credits or anything else your in-app referral program promises, for the person who was referred, for the user who referred them, or for both.
2. Set up an endpoint in your backend that receives the webhooks from Reditus.
3. On lead.created, look up the users involved and apply the benefit in your own product or billing system.
4. Test it with a test referral before you tell your users about the program.

Send affiliate data to your own systems

The other common use: when a new partnership is accepted (partnership.accepted), receive the affiliate's data and start your own onboarding emails from your own email tool, instead of the Reditus onboarding emails. New referrals (referral.created) can go to your other systems the same way, for example your CRM.

No code: Zapier or Make

There is no native Zapier or Make integration, but Zapier and Make can receive webhooks. Send the Reditus webhooks to Zapier or Make, and from there push the data to any tool you use. See Reditus with Zapier and Reditus with Make.

Related

• The Reditus API: send data in or pull it out.
• Setting up the in-app referral program
• All Reditus integrations