ReferralCandy’s Klaviyo integration lets you push information about your referral or affiliate campaigns and contacts from ReferralCandy to your Klaviyo account. Use ReferralCandy custom properties (profile fields) and events (metrics) to build your Klaviyo flows.
Before you start (important notes)
The default campaign short code FREN is used as an example in this article. Your campaign may use a different short code, depending on what you set.
Important: The examples below are placeholders only to show where your campaign short code appears. Do not copy/paste “FREN” into Klaviyo. Instead, Instead, insert the custom property using Klaviyo’s Personalization button (merge tag picker) so the correct campaign property is selected.
Each ReferralCandy campaign has its own unique short code, so there isn’t a single custom property that works across all campaigns.
Reminder: Always select the property from Klaviyo’s Personalization picker (instead of typing RC FREN - … manually), especially if you have multiple campaigns.
Where to find (and edit) your campaign short code
Your campaign short code is the campaign identifier used in integrations (for example, it appears in Klaviyo custom property names like “RC FREN - …”).
You can update the short code while your campaign is still in setup, but you can’t edit it after the campaign has been activated. Before activating your campaign, double-check that you’re happy with the short code you’ve chosen.
Shopify merchants (ReferralCandy in Shopify admin)
In Shopify admin, go to Apps → ReferralCandy.
Go to Referral campaigns and select the campaign you want to edit.
Under Get started, click Campaign details.
Find Campaign short code, make your changes, then save.
Non-Shopify merchants (ReferralCandy dashboard)
In the ReferralCandy dashboard, go to Campaigns.
Select the campaign you want to edit.
Go to Campaign Settings.
Find Campaign short code, make your changes, then save.
Custom properties (Klaviyo profile properties)
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 provided upon self-signup.
Example: “Alice”
RC [Short code] - Portal link
The contact’s sharing page (portal).
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.
Important clarification about what “approved” means:
A referred purchase is included in this count only once it becomes approved/rewardable.
This happens when either:
The referred purchase has passed the review period (review deadline), or
The referral has been manually approved (if manual approval is available in your account/platform).
Pending referrals (still within the review period) are not included in this count.
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:
For campaigns using multiple reward tiers, this returns the number of referred purchases needed to qualify for the subsequent tier.
When the contact reaches the last tier, it depends on the tier setting you selected:
Keep giving last tier reward for each referral after completing final tier → value is 1
Stop rewards after the final tier → value is 0
Loop tiers → value is determined by the minimum number of referral(s) set for the 1st tier
Single reward → value is 1
Pending referrals (still in review) do not reduce this number until they become approved.
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.
The property returns the reward and description of the subsequent tier.
If there are no subsequent tiers, the property doesn’t return a value.
Example: “a 10% discount”
Referral code vs friend offer code (important limitation)
ReferralCandy doesn’t support a Klaviyo custom property for the referral code or the friend offer code — only the referral link. When clicked, the referral link redirects users to the friend offer landing page, which contains the friend offer code.
Timestamp custom properties (debug/admin)
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”).
RC [Short code] - Banned at
RC [Short code] - Deleted at
RC [Short code] - Enrolled at
RC [Short code] - Unenrolled at
RC [Short code] - Unsubscribed at
RC [Short code] - Updated at
Inserting a custom property in Klaviyo
In Klaviyo’s editor, click Personalization for text blocks (or Add personalization in other text fields).
Click the All types dropdown and select Custom.
Select the ReferralCandy custom property you want to insert.
If you’re running multiple campaigns, use your campaign short codes to confirm and identify the property belongs to the correct campaign.
Events and triggers (Klaviyo metrics)
These are events you can use to trigger Klaviyo flows. When any of these events are triggered, ReferralCandy custom properties are updated for the customer profile.
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 a referred purchase is detected through the advocate’s referral link.
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 earned
Event variables: Campaign name; Date earned; Reward type; Reward amount; Reward currency
Additional variables:
Coupon: Coupon code; Coupon expiry date
Cash: Reward percentage; Portal login link
Triggered when an advocate successfully earns a reward from a referral.
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.
Klaviyo events and custom properties FAQ
Why can’t I see post-purchase, signup form, and invitation enrollment events in Klaviyo?
If you integrated Klaviyo with ReferralCandy before March 5, 2024, the following events are deprecated and no longer supported:
RC - Enrolled via post purchase
RC - Enrolled via signup form
RC - Enrolled via invitation
Enrolled in ReferralCandy through purchase
Use the RC - Enrolled event instead when setting up your Klaviyo triggers and flows.
Why is RC [Short code] - Referred purchase accumulated lower than the number of referrals I expect?
Most commonly, some referred purchases are still Pending (in the review period). Pending referrals aren’t included until they become approved/rewardable (for example, after they pass the review deadline, or after manual approval if that’s available in your setup).