Send every useful signal where your marketing already happens.
Signals publishes survey activity and customer properties to Klaviyo so you can build segments, personalize messages, and trigger flows from what customers explicitly reveal.
Signals complements Klaviyo
Klaviyo is very good at knowing what your customers did — what they opened, clicked, browsed, and bought. What it cannot know is what they meant: the goal, the routine, the reason, the timing. Signals collects that directly from the customer and hands it to Klaviyo in the shapes Klaviyo already understands — events and profile properties. Your messaging platform does not change. Its inputs get better.
Events and properties, in Klaviyo’s own vocabulary.
Nothing new to learn. Signals activity appears in Klaviyo as metrics you can trigger on and properties you can segment on.
Events sent to Klaviyo
- Completed Survey
- A customer finished a survey you published.
- Answered Spark
- A customer answered a one-question Spark.
- Started Product Finder
- A customer began a guided product-finding experience.
- Abandoned Survey
- A customer started but did not finish.
- Selected Customer Goal
- A customer declared what they are trying to achieve.
- Requested Follow-Up
- A customer asked to hear more.
Profile properties synced
- Primary Goal
- What the customer says they are trying to achieve.
- Product Interest
- The category or product they told you they care about.
- Experience Level
- Whether they are new to the category or experienced.
- Preferred Routine
- How the product fits into their day.
- Purchase Motivation
- Why they bought — for themselves, as a gift, or on a recommendation.
- Replenishment Timing
- When they expect to need more.
Property names are examples of what a Signals survey can create. You decide which answers become properties and what they are called.
Start a flow from something a customer said.
Every Signals event can act as a Klaviyo flow trigger, so a declared preference can start a message the same way a purchase or a browse does.
Explore segments and activation- Start an onboarding flow when a customer selects their goal.
- Send a product-match follow-up after a Product Finder is completed.
- Recover an abandoned survey with a single-question Spark instead of a full re-ask.
- Trigger a replenishment reminder timed to what the customer told you.
- Route a follow-up request to the right team or the right message.
- Branch an existing flow on a declared preference instead of a guess.
Segments behavior alone can’t build
Each of these is a Klaviyo segment defined on a property a customer explicitly gave you.
Goal-based segments
Everyone whose Primary Goal is “Focus” — regardless of what they have purchased so far.
Experience-level segments
Customers new to the category get education; experienced customers get depth.
Replenishment windows
Customers whose Replenishment Timing indicates they are due in the next two weeks.
Gift versus self-purchase
Separate the person who bought a gift from the person who actually uses the product.
Declared attribution
Group customers by how they say they found you, not only by last-click data.
Profile completeness
Find profiles missing a key property and send a Spark to fill exactly that gap.
Turn a send into a conversation.
A Spark embedded in a Klaviyo email is answered in one tap. No landing page, no form, no drop-off between the question and the answer.
- Embed a Spark directly in a Klaviyo campaign or flow email.
- The customer answers with a single tap, without leaving the message.
- The answer is attached to the Shopify customer and synced back as a profile property.
- Subsequent messages in the flow can branch on what they just told you.
- Use Sparks to enrich profiles that engagement data alone cannot explain.
Your Klaviyo flow email
Which benefit matters most to you?
Answered Spark event sent · Primary Goal property set
How the data actually moves
Predictable behavior matters more than speed claims. Here is what happens, every time.
Near real-time
Survey and Spark activity is sent to Klaviyo as it happens, so a flow can trigger on the answer immediately.
Profile matching
Activity is matched to the Klaviyo profile by identifier, so it lands on the customer record you already market to.
Latest value wins
Profile properties reflect the customer’s most recent answer, so segments stay current as preferences change.
Consent respected
Signals does not change a customer’s Klaviyo subscription status. Consent stays under your control in Klaviyo.
A bad minute shouldn’t cost you a response.
Networks fail and APIs rate-limit. Signals is built so that neither of those becomes your problem.
Read the integration architecture- Deliveries that fail for transient reasons are automatically retried with backoff.
- Events carry a stable identifier so a retry does not create a duplicate.
- Persistent failures are surfaced in Signals rather than failing silently.
- A Klaviyo outage does not lose responses — they are stored in Signals and delivered when the connection recovers.
- Disconnecting Klaviyo stops outbound delivery without affecting your response history.
One answer, all the way through to a better send.
-
1. Ask
A post-purchase Spark asks “Which benefit matters most to you?”
-
2. Sync
Signals sends an Answered Spark event and sets the Primary Goal property on the Klaviyo profile.
-
3. Segment
Your Klaviyo segment for goal-based onboarding picks the customer up automatically.
-
4. Send
The onboarding flow branches to the version written for that goal.
-
5. Learn
Signals analytics compare engagement and reorder rates across goals to inform the next campaign.
Klaviyo integration questions
What does Signals send to Klaviyo?
Signals sends survey and Spark events — including Completed Survey, Answered Spark, Started Product Finder, Abandoned Survey, Selected Customer Goal, and Requested Follow-Up — and syncs profile properties such as Primary Goal, Product Interest, Experience Level, Preferred Routine, Purchase Motivation, and Replenishment Timing.
Does Signals replace Klaviyo?
No. Signals complements Klaviyo. Klaviyo stays your messaging platform; Signals supplies the customer-declared data that makes segments, flows, and personalization more accurate.
Can customers answer a Spark inside a Klaviyo email?
Yes. A Spark can be embedded in a campaign or flow email so the customer answers with a single tap. The answer syncs back as a profile property and can branch the rest of the flow.
How quickly does data reach Klaviyo?
Survey and Spark activity is sent in near real time, so a flow can trigger on an answer as it is given. Profile properties reflect the customer’s most recent response.
What happens if Klaviyo is unavailable?
Responses are stored in Signals regardless. Failed deliveries are retried with backoff and carry a stable identifier so retries do not create duplicates. Persistent failures are surfaced in Signals rather than failing silently.
Give Klaviyo something it can’t collect on its own.
Install Signals, connect Klaviyo, and start segmenting on what customers actually told you.