- 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?
Why Are the Visit Counts from Usage Analytics Cards and the Visit Browser Different?
The difference is due to events, mainly searches and clicks, that should belong to the same visit but for the following main reasons do not:
User browser blocks cookies, and thus the visit is lost between each action.
User leaves the browser open for more than 30 minutes, then resumes interactions with search results.
Implementation does not properly set visit tracking cookie in some cases.
In all three scenarios above, the Visit ID is different for a search and a click even though the click and the search have the same Search ID.
The Visit Browser (and visit metric card) visit count only takes into account the Visit ID when linking events.
The Visit Browser can thus be used for troubleshooting improperly tracked visits as well as allowing visit metric cards to use filters on the complete visit instead of individual events.
Usage analytics reports use the Search ID in addition to the Visit ID when linking events.
Reports cards (except visit metric card) use the Search ID to minimize the impact of improperly tracked visits on the Has Clicks dimension and the Query Click-Through (%)metric. The Search ID is more reliable since the Search ID does not rely on a tracking cookie, which can lead to different values when looking at the Visit Count.
Starting with the July 2016 release of the Coveo JS UI, a visit tracking mechanism that does not rely on third-party cookies will help reduce the occurrences of Search ID vs Visit ID discrepancies.
In a later release, events from improperly tracked visits are planned to be rejected, and only the Visit ID should be used to measure visit count.
In the following screen captures, the number of visits is different depending on if a report or the Visit Browser is used to review visit counts.
In a usage analytics report, depending on the method used to count visits:
When reporting on both Visit ID and Search ID, there six distinct Visit IDs for a Visit Count of six.
When using the Visit ID with Click Date Time, there are still six distinct Visit IDs, but for a Visit Count of nine.
In the Visit Browser, for the same period and the same user, 10 visits and 10 distinct Visit IDs were counted.