> For the complete documentation index, see [llms.txt](https://documentation.bonsaidata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.bonsaidata.io/resources/getting-started/overview.md). # Overview The Resources section provides educational documentation to help customers understand Bonsai’s data requirements, integrations, and technical standards. This content is designed to guide clients through onboarding, integrations, data preparation, activation, and troubleshooting with clarity and confidence. *** ### What you’ll find here * FAQs * Example data schemas for Ads, Analytics, and Business Data * Integration requirements and specifications * Connect Card walkthroughs and setup guides * Data formatting expectations * Technical documentation to support onboarding These materials are intended to help customers prepare their systems correctly and accelerate time to implementation and activation. *** ### Purpose The Resources section exists to: * Provide transparency into our data requirements * Reduce friction during onboarding * Empower customers to prepare clean, structured data * Support successful activation If you are preparing data for onboarding, configuring an integration, or launch activation, start here. --- # 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://documentation.bonsaidata.io/resources/getting-started/overview.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.