- Minimum Information Needed
- Relevance Index Calculation and Usage
- Custom Metadata Sent with Events
- Database Schema in Exports
- User Visit
- Difference Between a Dashboard and an Explorer
- No Search Statistics/No Matching Results Error Messages
- Events Not Instantly Available in Reports
- Query Count Difference
- Visit Count Difference
- InterfaceLoad Definition and Search Exclusion
- Visitor ID and Visit ID Definition and Usage
- Maximum Number of Custom Dimensions
- Graph Dates Not Matching Export Dates
- Is Your Use of UA GDPR Compliant?
Is Your Use of Coveo Usage Analytics GDPR Compliant?
Coveo clients and partners are responsible, as data controller, to protect the privacy and rights of their European users. With the General Data Protection Regulation (GDPR), users must give consent before being tracked. You are responsible for collecting that consent (see How the GDPR Affects Cookie Policies). Coveo has no legal obligations, meaning that you must control how the usage analytics data is used and processed within Coveo products.
Clients and partners choosing to not track their users must thus ensure that users are anonymous when the usage analytics data is sent to the Coveo Cloud platform.
To anonymize your users, depending on your search page:
When using the Usage Analytics Write API directly, see the anonymous Request Body Property
Coveo does not keep IP addresses in usage analytics (see Does Coveo Keep IP Addresses in Usage Analytics?).