> 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.md). # Market Studio **Market Studio** is where you configure how PeakCommerce sells in more than one currency. It answers, for every market you operate in, three questions: * **Where do customers arrive?** — which signup journeys and portals belong to this market. * **How do they pay?** — which hosted payment page serves each of those places, in this market's currency. * **Who gets what?** — which language, profile, and other experience settings apply, written as plain-language sentences. Open it from **Commerce → Market Studio**. {% embed url="" %} ## A market is a currency The core idea in Market Studio: **one market, one currency**. "Canada" is the market that sells in CAD; "United States" is the market that sells in USD. A visitor's currency decides their market, and their market decides everything else — the payment page they see, the language they read, the profile they get. Because a market *is* its currency, adding a currency to your business always means adding a market, and vice versa. There is never a question of "which config wins": the market the visitor resolved to is the single source of truth for their checkout. See [Adding a market or currency](/product/using-peakcommerce/market-studio/adding-a-market-or-currency.md) for the end-to-end setup. ## The Studio at a glance The left rail lists your **markets**. Select one and everything in the tabs is about that market only: | Tab | What it does | | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | [How they pay](/product/using-peakcommerce/market-studio/how-they-pay.md) | One payment page for each place a customer can arrive, in this market's currency — with live health. | | [Who gets what](/product/using-peakcommerce/market-studio/who-gets-what.md) | Ordered sentences that assign language, profile, and other facets. | | [Where they arrive](/product/using-peakcommerce/market-studio/where-they-arrive.md) | The journeys and portals that belong to this market. | | [Trace a customer](/product/using-peakcommerce/market-studio/trace-a-customer.md) | Follow one hypothetical visitor from arrival to payment page. | Below the market list, **Payment configurations** is a shared view of every payment page registration across markets — provider, currencies, and health in one place. ## The setup checklist A new market starts inactive, with a checklist showing exactly what it still needs before it can serve customers: * **Surface assigned** — at least one journey or portal points at this market. Without an entry point, no visitor can ever reach it. * **Payment pages** — every place has a payment page in this market's currency. * **Payment route** — the routing that connects arrivals to those pages exists. The **Activate** button stays disabled while gaps remain, so a half-configured market can never silently take live traffic. ## Health — trust what actually happened Every payment page in Market Studio carries a live health signal, driven by real traffic: each time a checkout requests that page, the outcome is recorded. **Healthy** means the last real request succeeded. **No traffic yet** means exactly that — nothing has exercised the page, so nothing is known; it is not an error, and it flips to healthy the first time a checkout (or a smoke test) touches the page. ## The market assistant The Studio includes an AI assistant, docked at the bottom of the screen, that can answer questions about your configuration and stage changes for your review. It works the same way as the assistant in the page and component editors: it proposes, you approve. ## Where configuration lives Payment-page selection has exactly one home: Market Studio. At checkout the platform resolves the visitor's market and serves the page your routing names for that place; if no market resolves (for example, a tenant that has not configured markets), the billing integration's default page is used. Individual pages and components do not carry their own payment-page settings — so what you see in Market Studio is always what a customer gets. --- # 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.md?ask=&goal= ``` `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.