Use a pre-purchase survey for lightweight research when the merchant does not plan to answer each response. Use conditional-demand capture when the shopper is stating a specific condition the merchant may qualify and resolve. Both should be brief, contextual, accessible, privacy-conscious, and non-blocking; required response contact, transactional updates, non-guarantee acknowledgment, and optional marketing consent must remain conceptually separate.
- Research feedback and an actionable commercial request are different objects.
- One contextual question usually produces cleaner evidence than a long generic form.
- Do not turn response contact into automatic marketing consent.
- Close the loop only when the merchant has ownership and evidence to respond.
Diagnose the revenue constraint before choosing a tactic
Write down the decision the response should change. A broad survey may help prioritize copy or merchandising, while an actionable request needs product and variant context, quantity, identity, expiry, consent, ownership, evidence, and a defined merchant outcome. Review when the prompt appears, who sees it, whether it interrupts buying, how anonymous and identified data are separated, and whether staff can actually respond within a reasonable service level.
Treat profitable sales as a system: qualified traffic multiplied by conversion, order value, repeat behavior, and contribution margin. A tactic that raises one number while damaging another is not durable growth. Segment the evidence by product, variant, device, market, new versus returning customer, and purchase stage before deciding what to change.
A practical merchant playbook
Keep the normal product path primary. Ask one high-information question using product context and a small number of relevant choices, with a focused Something else path. If the merchant may respond, show a clear review step and explain that the request is not a guarantee. Collect only necessary response contact, keep marketing optional, provide cancellation where applicable, and aggregate recurring conditions into storefront or operational improvements.
- Define whether the goal is research or fulfillment of a shopper-specific request.
- Trigger the shortest relevant prompt without blocking normal checkout.
- Bind actionable responses to exact product and variant context.
- Separate response contact, transactional updates, acknowledgment, and marketing consent.
- Assign owners and convert repeated evidence into systemic fixes.
Where BuyWhen fits—and where it does not
BuyWhen is designed for actionable buying conditions rather than generic survey responses. It preserves the merchant decision, safeguards, private terms, checkout validation, and outcome evidence. A merchant conducting broad brand research or post-purchase satisfaction measurement should use a dedicated research workflow instead.
BuyWhen is most relevant when a shopper has purchase intent but one explicit active condition is unresolved: price, stock or variant, delivery, assurance, service, payment or procurement, or a product question. Bundle and custom activation remain future-gated. It does not replace acquisition, storefront quality, checkout, customer service, or a sound product.
Measure the change without overstating the result
Track prompt eligibility, open and completion rates, response distribution, duplicate and low-quality responses, merchant response time, systemic fixes, checkout, paid orders, refunds, opt-outs, and complaints. Do not interpret respondents as a representative sample without accounting for selection and placement bias.
Record the full path from eligible shopper to request, qualification, merchant decision, offer, checkout, paid order, refund, and cancellation. Report potential demand, attributed paid sales, net sales, and experimentally estimated lift as separate measures. Document the window and exclusions so a useful signal never becomes an unsupported revenue claim.
Frequently asked questions
Is BuyWhen an exit-intent survey?
No. It is an actionable conditional-purchase workflow. It can collect the condition blocking a qualified shopper, but it is not intended as a generic survey shown to every visitor.
Should email be optional for a merchant response?
If email is required to deliver the response, explain that purpose directly rather than presenting it as optional marketing. Marketing consent must remain separate and unselected.
Can anonymous feedback still be useful?
Yes for aggregate research, but it cannot support a customer-bound private offer or response. Keep anonymous evidence separate from verified request identity.
Sources and further reading
Product guidance is grounded in BuyWhen's documented behavior. The broader commerce and search principles in this guide also reference these primary sources: