Signals Surveys is part of Compass, the AI-first customer intelligence platform. Explore Compass
Longer-form writing on survey design, question wording, placement, and turning declared preferences into segments, flows, and revenue.
If you read nothing else here, these four decisions account for most of the difference between a survey that changes your business and one that produces a chart.
Every question you cannot connect to a decision is a question that lowers your completion rate for nothing.
A response that lives only in a report is research. A response attached to a customer is intelligence.
The same question asked at the right moment outperforms a beautifully worded version asked at the wrong one.
Forcing a choice manufactures answers. "I do not remember" and "prefer not to say" make the rest of your data trustworthy.
These are written and edited but not yet published. Each one links to the template or product page that covers the same ground today — those are live now.
Skin type, concern, and routine stage make post-purchase questions unusually high-value in skincare — and unusually easy to get wrong. Covers question order, the sensitivity of "what are you treating", and how to avoid implying a diagnosis.
Post-purchase templateA full walkthrough: which Signals events reach Klaviyo, how profile properties land, how to build a flow trigger on a specific answer value, and the conditional-split patterns that keep one flow from becoming twelve.
Klaviyo integrationTwenty Sparks worth stealing, grouped by lifecycle moment, with the profile property each one fills and the reason it works in email specifically rather than on a landing page.
Meet SparksQuiz structure for a category where customers do not know the vocabulary. Covers goal-first questioning, mapping answer combinations to real SKUs, where to place the email step, and the compliance line you should not cross with health claims.
Product finder templateTaste preference is a genuinely hard survey problem — customers describe flavour inconsistently. This covers concrete-anchor questions, using occasion instead of flavour notes, and building a preference center customers actually revisit.
Preference templateWhy fixed-interval reorder reminders underperform, how to ask about remaining supply without sounding like a sales prompt, and which customers to suppress from replenishment entirely.
Replenishment templatePre-event interest capture, the two questions to ask within an hour of an event ending, and how to turn attendee feedback into a segment for the next one instead of a PDF nobody opens.
Event feedback use caseHow to build a complete customer profile from many small asks rather than one long form — including how to decide what to ask next, when to stop asking, and how to avoid re-asking something you already know.
Progressive profilingFive complete templates with recommended questions, answer choices, placement guidance, Klaviyo properties, and suggested audiences. Closest thing to a guide that already exists.
Browse templatesEleven business problems, each with the questions worth asking and what to do with the answers. Written for merchants deciding whether a survey is the right tool.
See use casesThe reference material behind the guides — concepts, setup, survey building, the data model, and how every integration behaves.
Read the docsWe prioritise guides by what merchants actually ask for. If there is a survey problem you are trying to solve and nothing here covers it, tell us — it is the fastest way to move something up the list.
Install Signals, start from a template, and have your first survey collecting responses before you finish the guide.