Trace a Customer

Trace a customer answers "what would actually happen?" without needing a real checkout. Pick a place (a journey or portal) and a currency, and the trace draws the whole resolution as a connected path:

Visitor → Market → Route → Payment configuration → Page

Each step shows why it resolved the way it did — which market claimed the currency, which route matched the place, and which page the configuration serves — using the same server-side resolution the live checkout uses. The trace is not a simulation of the rules; it is the rules.

What to look for

• The path completes. Every hop is connected, ending at a real page. A path that stops early names the missing link — usually a route or a payment configuration gap for that place.

• The right market claimed the currency. Exactly one market should serve each currency. If two markets claim the same currency, the configuration is ambiguous and the Studio flags it — resolve it before activating.

• Unserviceable currencies are reported, not swapped. Trace a currency no market serves and you'll see the coverage-gap outcome: the visitor is shown the currencies you do offer and asked to choose. If a trace shows a silent substitution instead, something is misconfigured.

When to trace

• After any change on How they pay or Where they arrive — confirm the path end to end.

• Before activating a new market — trace every place in the new currency.

• When a customer reports the wrong currency or a payment form that won't load — trace their place + currency and the failing hop is usually immediately visible.

For verification with real traffic, pair the trace with the health badges on How they pay: the trace proves the configuration, health proves the live outcome.