ReferralCandy sends out reward notification emails for pending, successful, and ineligible rewards. If you want to send the reward emails via Klaviyo, you can use ReferralCandy events and custom properties to set up your own reward notification flows.

Before you begin setting up flows, we recommend you first read the Klaviyo integration overview and ReferralCandy custom properties articles.

To learn more about flows, read Getting started with flows on the Klaviyo help center.

The flows below cover a referred purchase being detected, a reward being earned, and a referred purchase becoming ineligible. Purchase detection alone does not mean the purchase is approved or a reward is earned. Use RC - Reward pending if you want to notify the advocate specifically that a qualifying referral is in review. It includes reward details and the initial review deadline, but that deadline can change and its coupon code can be None. Choose either a detection notice or a pending-reward notice for this stage to avoid sending both. See the event reference for the fields.

For each flow: select the metric listed below, then add a Campaign name trigger filter with equals and your intended campaign name (type Text). Events can come from different campaigns, including loyalty campaigns for reward-earned events, so do not leave the referral flow unfiltered. After renaming a campaign, check and update its Klaviyo Campaign name filters to match.

Check Re-entry criteria: choose Allow re-entry if the advocate should receive a notification for each matching event. No re-entry limits a profile to one entry in that flow. Preview with a matching event and profile, check all links and reward details, and test the email before making it live.

For buttons, use the campaign's Portal link property and open the rendered URL in preview. If it is missing, resolve it before sending. click here is button text, not a valid URL fallback.

This recipe uses RC - Purchase referred by profile detected to acknowledge a referred purchase. It is not a confirmation of reward eligibility. Adapt the wording to your review period and reward conditions.

To send an email notification to an advocate when they earn a reward, replicate the following setup and make tweaks as needed. RC - Reward earned can also fire for a no-reward tier with only Campaign name. That event has no reward details to include in this email. Check the event data before sending: the coupon message below needs Reward type equal to coupon and a usable Coupon code, not a missing value or the text None. Keep events without the required reward data out of the reward-email step.

Note: Event variables vary depending on which reward type is currently selected for your referral program. Preview using an event for the reward type you intend to send. The sample below matches the image: a 20% coupon reward. Replace the sample percentage with the actual discount for the campaign and reward tier receiving this email. Do not use this percentage wording for a fixed-amount coupon. Coupon code and expiry fields do not apply to every reward type. For cash, store credit or custom rewards, write a matching message using the fields available on that event. Date earned and a populated Coupon expiry date are Unix timestamps. Format them before displaying them in an email. The sample below includes the expiry sentence and hides it when the expiry is missing or None. Preview the rendered date and compare it with the coupon's actual expiry, including its time zone. A coupon without expiry can send the literal text None; a blank-value fallback does not remove that text. Reward issuance can happen after purchase approval, so trigger this email from RC - Reward earned rather than promising a coupon as soon as a purchase is approved.

To send an email notification to an advocate when their referred purchase is ineligible, replicate the following setup and make tweaks as needed.

If a custom property renders blank in your email, see Why is my Klaviyo email sending a blank referral link (or any blank ReferralCandy custom property)? in the property reference for the diagnostic flow.