> For the complete documentation index, see [llms.txt](https://because.gitbook.io/because/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://because.gitbook.io/because/case-studies.md). # CASE STUDIES - [Southern Scholar Boosts CVR by +34%](https://because.gitbook.io/because/case-studies/southern-scholar-boosts-cvr-by-+34.md): Learn how high end sock brand Southern Scholar leveraged Because to maximize landing page personalization for higher conversions. - [Ethique Leverages Zero-Party Data to Boost CVR by 26%](https://because.gitbook.io/because/case-studies/ethique-leverages-zero-party-data-to-boost-cvr-by-26.md): Learn how Ethique leveraged zero party quiz data to 5x their conversion rate with Because. --- # 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://because.gitbook.io/because/case-studies.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.