> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/customers.md). # Customers Part of our Data Activation module, Customers is the heart of our CDP (Customer Data Platform) offer. From multiple sources (online and offline), it allows reconciling and aggregating data around user profiles, to create accurate audience segments. By crossing any kind of data (CRM, online behavior on Web & Mobile, offline behavior in shops...), you can create highly accurate segments. More precise segments are, better is the personalization: these segments could be then sent to destinations, and, as a result, you can send a personalized message to a small audience who share same characteristics (in the same segment). Send the right message to the right audience is the key to improve the ROAS (Return On Ad Spent). --- # 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://doc.commandersact.com/features/customers.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.