Native Klaviyo Integration

Send Survey Responses to Klaviyo

With zenloop’s native Klaviyo integration, every new zenSurvey response is sent to Klaviyo in real time — no CSV exports, no Zapier, no custom API work.

Your feedback data lands directly on the Klaviyo profile as custom properties, ready for segmentation and automated flows.

🚀 Why connect zenloop and Klaviyo?

🎯 Act on feedback where you run your campaigns. NPS, CSAT, and individual survey answers become part of the Klaviyo profile.
🧩 Segment by feedback. Build segments such as “all detractors from the last 30 days” or “promoters who mentioned delivery”.
⚡ Trigger flows automatically. Start a detractor-recovery flow after a low score, or ask happy customers for a review or referral.
🪄 Real time, plug & play. Set up entirely in the zenloop UI in about 5 minutes. Responses appear in Klaviyo seconds after submission.

⚙️ How it works

The integration is part of Workflows and is configured per survey. Whenever a response comes in, zenloop sends the data you selected to Klaviyo. The profile is matched via the respondent’s email address; the values are written as custom properties on that profile.

🛠️ Setting it up

🔑 Prerequisite: a Klaviyo private API key with write access to profiles (in Klaviyo: Settings → Account → API keys).

In zenloop, open Workflows and create a new workflow with the action Klaviyo.
Select the survey the workflow should run for.
Paste your Klaviyo private API key.
Configure the mapping (see below) — this defines exactly which data is sent and under which name it appears in Klaviyo.
Choose when the workflow fires: on completed responses only (default) or on all responses, including partial ones.
Save and activate the workflow. Done — every new response is now synced automatically. ✅

🗺️ The mapping explained

The mapping mask is the heart of the integration. It has two sections, and both work the same way: each row maps one piece of zenloop data (left) to one Klaviyo property name (right).

1️⃣ Question answer mappings

Decide which survey answers are sent. Click + Add question mapping, pick a survey question on the left, and type the Klaviyo property name it should be stored under on the right — e.g. your NPS question → nps_score.

2️⃣ Response property mappings

Response properties are the data you attach to a survey yourself when distributing it — for example URL parameters or email placeholders like customer_id or order_id. Click + Add property, enter the exact source property name on the left and the Klaviyo property name on the right. The optional description field is just an internal note for your team — it is never sent to Klaviyo.

🔀 Forwarding mode

By default, only the rows you mapped are sent (“Mapped only”). Each section also offers three modes that forward everything automatically:

Mode	What is sent	Example
Mapped only (default)	Only the rows you explicitly mapped. Full control, nothing unexpected on your profiles.	nps_score
All (flat)	Everything is forwarded under its original name. Mapped rows act as renames.	customer_id
All (prefixed)	Everything is forwarded with a prefix you define — avoids name collisions with existing Klaviyo properties.	zenloop_customer_id
All (bundled)	Everything is bundled into one nested property you name. Keeps the profile tidy, but harder to use in segments.	zenloop_response

💡 Good to know: explicitly mapped rows always win if names collide, and empty values are skipped — the integration never overwrites or deletes existing Klaviyo properties with empty data.

🏷️ Property naming rules

Property names can be up to 64 characters and contain letters, numbers, and underscores. Invalid names are flagged directly in the form and cannot be saved.

⚠️ Heads-up: to write into a Klaviyo built-in property, use its $-name (e.g. $email, $first_name). Typing email without the $ creates a separate custom property instead — zenloop shows a hint in this case.

👀 How it looks in Klaviyo

Open any profile in Klaviyo and check the Custom properties section: your mapped values appear there exactly under the names you defined, e.g. nps_score: 9. From there, use them like any other profile property — in segment definitions (e.g. nps_score is at least 9) and as triggers or conditions in your flows.

💡 Good to know

🔄 The sync is real-time and one-way (zenloop → Klaviyo). Past responses are not backfilled — syncing starts when you activate the workflow.

📋 One workflow per survey: you can use different mappings (and different Klaviyo accounts) for different surveys.

💬 Questions? Reach out to us — we are happy to help you set up your first feedback-driven flow.

Get inspired by these two use cases

🛟 Win back unhappy customers:

Build a Klaviyo segment for all profiles with a csat_score below 3 (or an nps_score below 7) and automatically trigger a recovery flow — e.g. a personal apology from support, a voucher, or a callback offer. You reach unhappy customers within minutes instead of weeks — exactly when churn can still be prevented. Every customer you save is directly measurable revenue.

→ Pro tip — differentiate by customer value: If you pass properties like customer value to zenloop (e.g. customer_value or lifetime_value), you can scale your response accordingly: for low-value customers, run the win-back fully automated via a Klaviyo email — cost-efficient and scalable.

For your top customers, go personal instead: use a workflow to create a ticket in your ticketing tool or notify your support team so they pick up the phone. That way, every piece of feedback gets the response it’s worth.

⭐ Activate your promoters:

Customers with an nps_score of 9 or 10 are your best salespeople. Automatically trigger a flow asking them for a referral with a personal code — at the moment of peak satisfaction. More reviews lower your acquisition costs, and referrals convert far better than any paid campaign.

Support Centre