> For the complete documentation index, see [llms.txt](https://docs.americanspend.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.americanspend.com/mcp-methods/place-and-audience.md). # Place and audience region\_summary, cohort\_overlap, cross\_shop, and wallet\_migration. ### region\_summary Spend growth by income tier for each metro or state, beside labor and income. `geo_level` is `cbsa` or `state`. `geo` limits which regions. `limit` and `order_by` rank them. `start_date` and `end_date` bound the window. ### cohort\_overlap How much two or more audiences overlap. Each audience is a numbered side, `brand_1` and `brand_2` up to ten, or `ids_1` when you already have merchant ids. `start_date` and `end_date` bound the window. This is an intersection of accounts that bought from those merchants. It is not a retention cohort, and it has no geography filter. ### cross\_shop The other merchants a cohort uses most. Name the cohort with `merchant_id` or `merchant`, and optionally `spender_state`. `limit` caps the list. `start_date` and `end_date` bound the window. ### wallet\_migration Where a cohort's spend went after it stopped at a merchant. `before_start` and `before_end` are the window when the cohort was buying there. `after_start` and `after_end` are the window after. Name the merchant with `merchant_id` or `merchant`. `limit` caps the destinations. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.americanspend.com/mcp-methods/place-and-audience.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.