Feature: Post Purchase Event for Klaviyo

Important Note: This feature is completely separate and independent from the Feature: Klaviyo list sync invite feature.


Using this feature you can integrate ReferralCandy seamlessly with new or existing post-purchase customer flows within Klaivyo, or build out a new flow to incorporate referrals.


1. Once you’ve integrated with Klaviyo by providing your API key, you simply need to select the ‘Activate Post Purchase Events’ button as seen below.

Warning: Once you Activate Post Purchase Events for this feature, ReferralCandy will automatically disable its native Post Purchase Emails on this page. This is because the expectation is that a merchant moving forward would intend to build out and centralize referral outreach through Klaviyo. If you've had success with ReferralCandy's native Post Purchase Emails and would like to continue with that instead, you can reactivate those emails at your own discretion here.

2. You’ll see this new section open up, where we provide a breakdown of the custom properties you can utilize on your email templates (used in your flows).

Important Notes

  • Once this feature is activated, control of sending post-purchase emails is switched over from ReferralCandy to Klaviyo.
  • ReferralCandy will stop sending post-purchase emails. You may opt to re-enable the ReferralCandy post-purchase referral emails here.
  • Upon activating this feature, referral emails will not yet be sent to your customers right away, you must first incorporate our ReferralCandy Custom Properties into your Klaviyo post-purchase email flows. Activating this feature simply initiates an event to be triggered that allows ReferralCandy to pass referral information to Klaviyo after each purchase from your store.

Confirming Activation:

You’ll want to make sure that this feature has been activated successfully. Every time a purchase takes place, it triggers a Klaviyo ‘event’ that pushes referral information to Klaviyo in the form of ‘properties’ which you can utilize in the email templates of your flows.

Follow the steps below to confirm if Custom Properties are being successfully generated:

1. On your Klaviyo dashboard, head to the ‘Profiles’ section or use this link.

2. If the integration was successful, you should see a profile that was automatically created under the email address: ‘’

3. Opening up that profile you’ll see the ReferralCandy ‘event’ “Enrolled in ReferralCandy through a purchase”. Future customer purchases will have that same ‘event’ triggered.

4. On the bottom right you’ll also see information about the custom properties that ReferralCandy has relayed to Klaviyo. Any customer that has the ‘event’ “Enrolled in ReferralCandy through purchase” should ALSO have these custom properties generated or updated when the event is sent.

Note: These properties are updated every time a purchase takes place.


You may now incorporate the referral program custom properties into your existing flows. Check out our Sample Implementation for an idea of how to get started.


It’s very important to test that everything is working correctly. I recommend that after integrating and adding your chosen ReferralCandy Custom Properties into your desired email templates, you also make a test purchase to check that they are being shown as you intended.

Take note that the ReferralCandy Custom Properties will only be created for new customers AFTER integrating the post-purchase event feature, AND AFTER a new purchase has come through for that customer. Otherwise, the Custom Properties for that customer will be empty and appear as blanks if triggered for that customer.

Best Practices:

Setting Delays & Conditions

  • There can be a short delay between when a purchase is made in your store, and when ReferralCandy can create and send that information (from the event) to Klaviyo. This can be mitigated by setting a delay between when a purchase is made and when the first email in your post-purchase flow is sent.

  • Missing referral links can also happen because of the above-mentioned delays. You can prevent this by setting a condition to only show the block that contains the referral program elements IF those Custom Properties are available. You may use the condition: person|lookup:'Referral Link - ReferralCandy' as seen in the screenshot below:

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.