Klaviyo Integration

Klaviyo provides a powerful tool called Flows which can help you do things like:

• Email a customer automatically after they've attended more than 5 events with the same instructor
• Started a cancellation on their subscription (so you can maybe encourage them to come back)
• It's been a certain number of days since they attended their last booking (as a way to encouarge someone to visit again or ask why they haven't come back)

The key to flows that differentiate it to the Automator inside CodexFit and Mailchimp are:

1. The Automator is great for what we call "time in place" actions. These actions happen when a specific event happens, i.e. a customer made a booking, attended an event, or just registered and you want to do an action immediately. If you want to do something a certain number of days after someone registered, you'd need to do that in Mailchimp or Klaviyo. Or if you wanted to send an email after something else happened a relative number of days in the future, that's where Klaviyo shines. 
2. We pump in bigger picture data to Mailchimp, for instance the total number of bookings a customer made. What we can't do with Mailchimp is send them an event when a customer attends an event. In Klaviyo we can which means you can tell a Klaviyo Flow to do something after a certain number of conditions are met. For instance, send an email after a customer attended at least 5 boxing events with Joe. That level of granularity you won't be able to get in Mailchimp or the Automator and it's where Klaviyo is helpful. 

We send the following events to Klaviyo (including the payload that is sent each time):

• Customer registered including:
  • id
  • full name
  • email
  • dob
  • phone
  • post code
  • utm source details
• Purchased a bundle including:
  • bundle name
  • bundle handle
  • credit type and quantity
  • cost (to be deprecated, do not use and instead use value)
  • value
• Purchased a plan/subscription:
  • subscription id
  • plan name
  • plan handle
  • plan status
  • number of trial days or trial end date
  • cost (to be deprecated, do not use and instead use value)
  • value
• Subscription status changed:
  • subscription id
  • plan name
  • plan handle
  • previous status
  • new status
  • end date (if included)
    • The goal of this event is to allow clients to see when a trial ends or when a subscription is marked to cancel to retarget them.
• Subscription cancellation initiated:
  
  • subscription id
  • plan name
  • plan handle
  • end date
  • status
• Attended an event:
  • event type
  • event type group
  • instructor
  • location
• Booking created
  • event type
  • event type group
  • instructor
  • location
• Booking cancelled
  • event type
  • event type group
  • instructor
  • location
• Viewed a video:
  • video name
  • event type
  • event type group
  • instructor
  • duration viewed

If you're interested in enabling our Klaviyo integration, please email support@codexfit.com. You can also share access with your Klaviyo account to systems@twotwentyseven.com so we can get that rolling.