FeedPurchase intent data guide
Use Shopify purchase intent data without confusing interest with revenue
Purchase intent becomes useful when its source, product context, shopper condition, readiness, and outcome are preserved. BuyWhen uses an explicit truth ladder so teams can act on demand without overstating what the data proves.
No income is guaranteed. Commission is paid only for eligible paid months.
The BuyWhen truth ladder
Inferred friction is behavioral evidence with disclosed coverage and missing inputs. Verified demand is a shopper-declared, identity-checked, product-bound condition. Executed means a merchant-approved response reached checkout. Proven means the attributed outcome passed the configured retained-outcome review with refund evidence.
Potential, paid, and proven values are displayed separately. Modeled opportunity is never silently relabeled as earned or incremental revenue.
What a useful request contains
A BuyWhen request can include the exact product or cart, variant, quantity, market, condition type, structured requirements, acceptable fallbacks, readiness, deadline, consent evidence, and the merchant's later decision. Unknown fields remain unknown and can block a binding response.
What merchants can learn
Aggregated demand can show whether delivery, availability, fit, questions, service, procurement, or price repeatedly blocks purchases. Outcome-linked evidence then shows which merchant responses were used, which reached checkout, and which remained paid after refunds and the observation window.
Frequently asked questions
What is Shopify purchase intent data?
It is evidence that a shopper is considering a purchase. Stronger intent data connects the shopper's explicit condition to a product, quantity, readiness, deadline, and later outcome rather than relying only on page views or cart events.
Does a purchase request count as revenue?
No. A request is potential demand. BuyWhen reports requests, checkout-ready responses, paid orders, and proven retained outcomes as distinct states.
Reviewed by the FeedIQo product team. Last updated August 23, 2026.