NimbleTailor
Landing pages that tailor themselves to every click

Use campaign context before customer-level tracking

Updated September 20, 2026

A landing page can reflect its campaign, query, geography setting, or current request without building a long-lived customer profile. Start with contextual relevance, then add permitted signals only when they change the decision.

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.