Product recommendations shoppers actually want

Can recommendations work without marketing consent?

Updated September 20, 2026

Yes. Use current-page and catalog context for useful defaults, and apply customer-level or marketing signals only when the relevant processing is allowed. A declined purpose should not break shopping.

Define the decision first

Write down what the system changes, which signal supports that decision, and how long the signal stays useful. Do not collect a field merely because it may be useful later.

Respect the allowed processing state

Shopify’s Customer Privacy API separates preferences, analytics, marketing, and data-sale processing. Optional processing should follow the relevant state, and consent should result from a visitor action rather than being assumed.

Keep a complete fallback

When permission is absent or withdrawn, preserve product information, navigation, search, cart, and checkout. Use transparent catalog and page context instead of a blank experience.

Source

Shopify Customer Privacy API, accessed September 20, 2026.

Frequently asked questions

Can product recommendations run without marketing consent?

Yes, in many cases recommendations based on the current session and the product being viewed rely on a different legal basis than marketing tracking. The key is using only the data needed to serve the recommendation and honoring the consent state the visitor chose.

What recommendation data is safest to use without consent?

Contextual signals from the current visit: the product page being viewed, items added to the cart in this session, and aggregate popularity. These do not require building a persistent profile of the visitor.

What should the rail show when consent is declined?

A complete, useful fallback: bestsellers and products related to the current item, ranked by aggregate data. Declining consent should change how the rail is powered, not leave the shopper with an empty or broken page.