> For the complete documentation index, see [llms.txt](https://docs-en.shoppy.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.shoppy.is/shoppy-dashboard/integrations.md). # Integrations In this section you can manage third-party integrations for your Shoppy app. The integration services are divided into the following categories: * **Optimization**: integrations that optimize the User Experience of users on your app. * **Analytics**: integrations that allow you to set up loyalty programs for the users that use your app the most. * **Customer Success**: integrations that enable you to better interact with your customers. * **Rewards e Loyalty**: integrations that allow you to set up loyalty programs for users who visit your app the most. * **Marketing**: these integrations allow you to use and monitor marketing services to advertise your brand's app. * **Ratings and Reviews**: these integrations allow you to add social proof features to your app such as adding the possibility for your customers and fans to review products. * **Payments**: integrations with alternative paymenet services. With the *Enable* button you can enable the integrations of your preference. {% embed url="" %} --- # 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-en.shoppy.is/shoppy-dashboard/integrations.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.