> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/market-studio/trace-a-customer.md).

# 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](/product/using-peakcommerce/market-studio/how-they-pay.md) or [Where they arrive](/product/using-peakcommerce/market-studio/where-they-arrive.md) — 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](/product/using-peakcommerce/market-studio/how-they-pay.md): the trace proves the configuration, health proves the live outcome.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/using-peakcommerce/market-studio/trace-a-customer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.