ReferralCandy's Klaviyo integration lets you push information about your referral, affiliate or loyalty campaigns and contacts from ReferralCandy to your Klaviyo account. Use ReferralCandy custom properties (profile fields) and events (metrics) to build your Klaviyo flows.

Campaign short code (the campaign "ID")

To find or edit your campaign short code:

Below is a list of ReferralCandy custom properties you can use in Klaviyo. These properties appear on a Klaviyo profile and can be inserted into your email/SMS content using Personalization.

Important: Don't copy/paste the example property names below. Use Klaviyo Personalization to insert the correct one for the specific campaign you're using.

Profile custom properties

RC [Short code] - Name
The contact's name.
Example: "Alice"

RC [Short code] - Portal link
The contact's advocate portal link.
Example: https://yourstore.referralcandy.com/DXTMKK4

RC [Short code] - Referral link
The contact's referral link.
Example: https://yourstore.refr.cc/campaign/u/alice

RC [Short code] - Referred purchase accumulated
Total number of approved, rewardable referred purchases accumulated by the contact. A purchase can increase this count even when its reward tier gives no incentive.

Important clarification about what "approved" means:

Example:
If a contact has 3 referred purchases detected, but 2 are still Pending (in review), and only 1 is approved/rewardable, then:
RC [Short code] - Referred purchase accumulated = 1

RC [Short code] - Referred purchase needed for next reward
​

Total number of approved referred purchases needed for the contact to qualify for the next reward.

Notes:

FlexiTiers example:
Tier 1 | 1–2 | 10% off
Tier 2 | 5+ | 50% off
​

If a contact made 2 referrals, the property returns 3 (they need 3 more approved referred purchases to reach Tier 2).

RC [Short code] - Next reward description
The description of the reward the contact will receive upon qualifying for their next referral reward.

Sharing the friend offer
Use the campaign's Referral link property when asking advocates to invite friends. The Coupon code variable on an RC - Reward earned event is the advocate's reward coupon, not the referred friend's offer code.

Loyalty store-credit properties

For contacts enrolled in a loyalty campaign, look for these properties under that campaign's short code:

These are formatted amounts from the ReferralCandy loyalty campaign's records, not the customer's total Shopify store-credit balance. Use the loyalty campaign's Portal link to direct the customer to their rewards. Loyalty campaigns do not provide a referral link or next-referral-reward properties. Check the actual values on the profile before using them in an email.

These properties show timestamp information based on actions done to a profile. They're intended for debugging/admin purposes. Values are in Unix format (example: "1660724560").

If you're running multiple campaigns, use your campaign short codes to confirm and identify the property belongs to the correct campaign.

The list below covers the events used in our referral and affiliate flow guides. Your Klaviyo account may show additional ReferralCandy metrics. Event variables describe the activity that triggered the flow; custom properties are values stored on the profile. ReferralCandy activity can update campaign-specific profile properties. A sample event used to check the integration does not prove those properties are populated for a contact. Check the relevant event and profile when previewing your email.

RC - Enrolled
Event variables: Campaign name; First time enrollment (True or False)
Triggered when a contact meets the campaign's segment criteria and becomes enrolled in your referral or affiliate campaign.

RC - Unenrolled
Event variables: Campaign name
Triggered when a previously enrolled advocate/affiliate no longer meets segment criteria and becomes unenrolled.

RC - Signup form submitted
Event variables: Campaign name; Form type
Triggered when a contact who was never enrolled in the campaign signs up via a form.
Form types include: Post-purchase popup (if signups are enabled), Referral extension (if signups are enabled), Referral widget, Join page, Embedded signup form.

RC - Waitlisted
Event variables: Campaign name; Form type
Triggered when a contact who was never enrolled doesn't meet the segment criteria after signup.

RC - Purchase referred by profile detected
Event variables: Campaign name; Currency; Purchase amount
Triggered when ReferralCandy attributes a purchase to the advocate. Attribution can come from a referral link, a friend offer code or a referral you assign manually; this event does not identify which method was used.
Note: This detection can happen before the referred purchase is approved (it may still be Pending during the review period).

RC - Purchase referred by profile made ineligible
Event variables: Campaign name; Reason
Triggered when a referred purchase is flagged as ineligible.

RC - Reward pending
Event variables: Campaign name; Pending date; Review deadline; Reward type; Reward amount; Reward currency; Coupon code
Triggered when a qualifying referral enters a finite review period and a reward is lined up. It does not mean the reward has been earned. A coupon that has not been generated yet can have the literal text None as its Coupon code.

Pending date and Review deadline are Unix timestamps. The deadline records the state when that event was sent; a later review extension can change the deadline in ReferralCandy without changing the earlier event. Do not promise delivery on that date or send a pending coupon as an earned reward. A referral that was frozen can send another RC - Reward pending event when its review period resumes, so allow for a repeated pending notification in your flow.

RC - Reward earned
Event variable: Campaign name
Reward variables, when an incentive is issued: Date earned; Reward type; Reward amount; Reward currency
Additional variables depend on the reward type:

Triggered when an advocate earns a referral reward. A no-reward tier can also trigger this event with only Campaign name, without a reward type, amount, code or earned date. Do not treat every occurrence as an incentive earned. See Using segments in ReferralCandy and Klaviyo for filtering reward events. This event is also sent for store-credit grants in loyalty campaigns. Filter referral flows by Campaign name so they use the intended campaign. A coupon without an expiry date can have the literal text None as its Coupon expiry date; omit expiry text in that case. Date earned and a populated Coupon expiry date are Unix timestamps; format them as dates before displaying them in an email. Check Reward type and the reward fields your message needs before sending it. For a coupon email, require a coupon reward and a usable Coupon code; keep events with missing reward data out of that email step.

RC - Subscribed to campaign emails
Event variables: Campaign name
Triggered when a contact is subscribed to campaign emails.

RC - Unsubscribed from campaign emails
Event variables: Campaign name
Triggered when a contact unsubscribes from campaign emails.

RC - Banned from ReferralCandy
Triggered when you ban a contact.

RC - Removed from ReferralCandy
Triggered when you delete a contact from your ReferralCandy account.