> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/releases-and-announcements/releases/2022-july-18.md). # 2022 - July 18 Didomi continually releases updates to our platform to improve our capabilities and resolve issues. Please refer to the sections below for our latest releases: * [Analytics](#analytics) *** ### Analytics #### Weekly data is now **Daily** data We previously had two databases/tables feeding the analytics dashboard. One with hourly data (Exploration, AB testing and Custom report dashboards) and one with weekly data (Domains & Apps, Web Pageviews, App Sessions, Countries, Tech). We have the following: * **Time aggregation**: daily, weekly, monthly aggregation available for all standard reports (Domains & Apps, App Sessions, Tech., Countries, Web Pageviews, Custom Report). * **Data history**: one full year of data history at the aggregation level of your choice (for all the reports except the Exploration report, for which it’s two weeks). * **Data Centralization:** there is only one table where all the data is centralized. One export (instead of two) with all the data for the Analytics Export. * **Filters:** Country and GDPR filters are now available in the Exploration and Custom Report dashboards. A new filter “Add date to the main table” has been added to most of the dashboards. --- # 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.didomi.io/releases-and-announcements/releases/2022-july-18.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.