Persona assignments in Klaviyo

Why use predictions for persona assignments?

Ah personalization, the holy grail of growth teams everywhere. Too bad it’s so difficult to do well.

The best way to personalize email is the simplest: organize your customers into personas, then produce straightforward variations of your email content for each persona. This way, you can have both copy and creative perfectly aligned with the interests of each persona so that your customers feel like you get them.

Faraday makes discovering your brand's bespoke personas intuitive & easy, and delivering them to any channel in your stack a breeze.

With persona assignment predictions in Klaviyo, you'll give your team the ability to personalize engagement to perfection through insights from AI-generated personas.

Follow the steps below to get your persona assignments predictions into your Klaviyo account.


In this guide, we'll show you how to:

  • Organize your customer data into cohorts
  • Describe prediction models for personas with persona sets
  • Deploy persona assignments predictions to Klaviyo using Pipelines

Getting started with persona assignments in Klaviyo

Make sure you have a Faraday account (signup is free!) and that it's not in test mode.

Requirements for this persona assignments recipe

You'll need the following cohorts available in your Faraday account:

Screenshot of the cohorts listing that includes Customers

Building predictions for persona assignments in Klaviyo

Now you'll create the prediction objective(s) necessary to complete this use case with Faraday.

Getting started with Klaviyo personalization

Persona sets use machine learning to organize people into unique, coherent subgroups (called personas) that you can use to personalize your outreach.

Creating a persona set for your Customers

Let's make a persona set that organizes your customers into personas.

  • In the navigation sidebar, choose Persona sets. Screenshot of the persona sets list
  • Click the New persona set button.
  • Fill out the form:
    • For Choose a cohort, pick the cohort that best represents your customers.
    • Leave the advanced settings at their defaults.
    • Enter a memorable name, like "Customers". Screenshot of the new persona set form, filled out
  • Click the Save persona set button.

Faraday will do some magic in the background, so you can proceed with the rest of the instructions. When your persona set is done building, you'll get an email, and you can review your personas.

Screenshot of the persona sets listing that includes Customers

Using Pipelines to deploy predictions to your stack

Now you'll configure the pipeline that deploys your predictions to klaviyo.

Create your pipeline for persona assignments in Klaviyo

  • In the navigation sidebar, choose Pipelines. Screenshot of the pipelines list
  • Click the New Pipeline button.
  • Fill out the form:
    • For Payload, choose the following:
      • Persona set: Customers
    • For Population to include, choose the following:
      • A cohort representing your customers
    • Enter a memorable name, like "Persona assignments in Klaviyo". Screenshot of the new pipeline form, filled out
  • Click the Save pipeline button.

Your pipeline will start building in the background. You can proceed immediately with the next set of instructions.

Deploying your pipeline to Klaviyo

CSV

  • In the Deployment area, find the CSV module and click Add. Screenshot of the ready pipeline with no targets yet
  • Fill out the popup:
    • Choose the Identified option.

    • Choose Human friendly column headers.

  • Click the Next button. Screenshot of the new target form, filled out
  • Expand the Structure section of Advanced Settings
    • From the dropdown, select the klaviyo preset. Screenshot of the second page of the new target form, filled out
  • Click the Finish button.
  • Click the Test deployment button and confirm the results meet your expectations. Screenshot of a target after hitting its test button the first time Faraday will finish building your pipeline in the background. When it's done, you'll get an email—return to the pipeline and click the Enable pipeline button to activate it.

How to use your persona assignments predictions in Klaviyo

With your pipeline deployed, it's time to plug your personas into Klaviyo. Follow the steps below to see each Klaviyo contact enriched with their unique persona.

Importing your personas CSV into Klaviyo

  1. In your Faraday pipeline, click the Download CSV button under the deployment to download your personas as a CSV.
  2. Navigate to Klaviyo's Lists & Segments, and click create a list/segment in the upper right.
  3. Select list, as you'll need to create a list with these contacts and create the persona property during upload.
  4. Give your list a unique name and, optionally, a tag. Click create list.
  5. Select upload contacts.

Image of Klaviyo create list selection

  1. You'll be taken to the field mapping screen, where you can map any fields that didn't automatically map.

Image of Klaviyo import mapping

Under the "Klaviyo field" column, key rows to map to are email and the persona row outlined in step 7. Rows like the raw persona ID, which is generally the row before the score in step 7, can be skipped.

  1. In the final row, "fdy_persona_set_persona_name", click unmapped, and type in a unique name for this field, such as "Persona." Then, click create option.

Image of new Klaviyo property creation

  1. In the final column for your new personas property, "type," ensure the option is string, as personas will be several characters of text. This will enable you to create segments of contacts whose persona is a specific name.
  2. Click import review in the upper right to see the final report of columns being imported, properties being created, and columns skipped. Click start import to wrap up, and you can now begin to plan a personalized campaign to target the contacts in this list. Contacts that already exist will have their persona appended to their contact card.

🔒 It's a best practice to permanently delete any file that contains personally identifiable information (PII) after use. Any deployment from Faraday that is unhashed contains PII, and should be deleted after uploading it to your destination for security purposes.