> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/beginners-guide/integrating-netmera.md). # Integrating Netmera The Netmera onboarding process covers needs assessment, a tailored plan, training and go-live support. ### Onboarding process Our dedicated Onboarding Teams ensure that customers integrate and adopt Netmera efficiently. The process includes: * **Initial Contact & Needs Assessment** → Understanding customer requirements and app objectives. * **Tailored Onboarding Plan** → Designing a customized plan to match business goals. * **Training & Education** → Delivering hands-on sessions to familiarize teams with Netmera’s platform. * **Technical Integration & Testing** → Supporting developers through SDK setup, API reviews, and integration checks. * **Ongoing Support & Optimization** → Providing continuous guidance and monitoring performance to maximize results. This collaborative approach ensures customers achieve successful adoption and improved app engagement. ### SDK integration resources Before starting technical integration, we encourage you to review [Developer Guide](https://user.netmera.com/developer-guide/), which contains step-by-step instructions for SDK setup, API usage, and best practices. --- # 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://user.netmera.com/netmera-user-guide/beginners-guide/integrating-netmera.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.