> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/analytics.md). # Analytics The Analytics section helps you track and understand your app’s performance, user engagement, and behavior. By analyzing real-time data and key performance metrics, you can make informed decisions to optimize your app experience and improve user retention. Here, you'll find: * Insights into user activity, including active users, session duration, and retention trends. * Performance tracking to monitor app load times, responsiveness, and crash reports. * Traffic analysis to understand where your users are coming from and how they interact with your app. * User demographics to identify audience segments based on location, device type, and operating system. * Conversion tracking to measure user actions such as purchases, sign-ups, and key interactions. {% embed url="" %} Explore this section to gain valuable insights and optimize your app's user experience based on real data. --- # 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://docs.appmysite.com/app/analytics.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.