> 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-january-15.md).
# 2022 - January 15
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
#### **All reports**
**Filters**
* **Domain(s)/App(s) (exclude):** a wider match is now available. The text is also case insensitive.\
\
* **Domain view:** all the reports at domain level are adjusted accordingly. The Domain view by default is by subdomain.\
\
**Metrics description**
* The metrics description is now a formula that gives a better overview and understanding of the parameter:\
\
**New metrics**
* Two brand new metrics are now available: **Purposes View Rate** and **Vendors View Rate**.
๐**Purposes View Rate:** Total shown purposes/Total notices
๐**Vendors View Rate:** Total shown vendors/Total notices
#### **Domains and App(s)**
**Bounce rate and positive consent rate relation**
* You can hover the point to see the details of the domain position. This offers you a better overview of the domain position regarding the **bounce rate** and the **consent rate**.
* The bounce rate and the consent rate are now **displayed in %**, and you can see **one color per SDK type.**
#### **Domains**
* If you have multiple domains, you have now the possibility of seeing the top 10 domains for positive consent share. It gives you more information about the consent following the domain name.\
\
#### **Countries**
* You can now add positive consent share per top 10 countries. This gives a great overview of the consent share following your usersโ location. \
#### **Tech**
**Consent rate per technology**
* You now have access to the consent rate following the technology used by the user, such as: **iOs**, **Android**, **Web**, etc.
#### **Web Pageviews and App sessions**
**Device**
* The color code is now harmonised between the two figures, to offer a more intuitive reading. The left figure is now showing consent share by platform/device/OS and the right one is showing consent rate over time.
#### **Custom report**
You can generate your own report on a daily/hourly/weekly/monthly basis, on the following information:
* Domain inclusion
* Domain exclusion
* Platform
* Device type
* Device OS
You can add up to 5000 rows to your report. Please note that you can exclude a column and that there is no volume filter.
---
# 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-january-15.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.