> 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/where-they-arrive.md). # Where They Arrive **Where they arrive** lists the **surfaces** that belong to the selected market — the entry points through which a customer can reach it: * **Journeys** — your public signup/checkout journeys, listed by name. * **Portals** — the Customer, CSR, Sales, and Partner portals. A market with no surfaces has no entry point: no visitor can ever land in it, which is why **Surface assigned** is the first item on the [setup checklist](/product/using-peakcommerce/market-studio.md#the-setup-checklist). ## Acquisition vs. post-purchase Surfaces come in two kinds, and the platform treats them differently: * **Acquisition** (signup journeys): the market is chosen from the *visitor* — the currency they arrived with, or their locale. This is the moment a customer's market is decided. * **Post-purchase** (portals): the market comes from the *account*. A customer who signed up in CAD is a CAD customer; when they — or a CSR working on their behalf — add a payment method later, the account's market decides the page, regardless of who is clicking or where they are sitting. This is what lets one CSR serve customers in every market: the CSR portal is assigned to all markets, and each customer account brings its own market to the interaction. ## The default market One market is the **default** — where a visitor lands when nothing identifies a market for them (no currency in the link, no matching locale). Choose the market that covers the majority of your traffic. The default is a real, fully-configured market, not a fallback bucket: its checklist has to be green like any other. --- # 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/where-they-arrive.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.