Note that, unlike most of Algolia functionality, the Analytics API is not present in our API clients; you must therefore use the REST API endpoints directly. In this overview, we will focus exclusively on the dashboard features.
Basic Analytics Metrics
Most Popular Searches
Available on all subscription plans.
We aggregate the multiple “character by character” queries to find the words or expressions searched by your users, and return a list of the most popular expressions searched, with some stats:
average hits: average number of hits matched by the query with typo tolerance.
…without typos: average number of hits of exact matches (without typo tolerance).
count: number of times the search is performed.
Queries with No Results
Available on all subscription plans, except the Starter plan.
If you want to know what your index catalogue is missing, or improve the keywords and synonyms you’re using, you can have a look at this handy analytics feature. It’ll show the most popular queries that returned 0 (or a small number of) results. The displayed count is the number of times the query has been made on the index by all your users. If a query has been made two times by one user you will see x2.
Advanced Analytics Metrics
The following analytics are available only for customers on our advanced subscription plans. For new customers, this includes the Essential, Business, and Enterprise plans; and for customers still on the older plans, this includes Growth, Pro, and Enterprise.
Activity by Country
If you have implemented Algolia on the front-end, you can see where the queries are coming from geographically.
When doing backend search, make sure to forward the IP of the end user. Otherwise Algolia will see the queries coming from only one location: the location of your backend server.
Most Popular Filters
To see how your users are using your search filters, you can click on the
It’s possible at query time to specify the analyticsTags parameter to tag this specific query in order to be able to split the analytics data. For example, it’s possible to send two different tags - mobile and website - to see how mobile users search in comparison to website users.
Did you find this page helpful?
We're always looking for advice to help improve our documentation!
Please let us know what's working (or what's not!).
We're constantly iterating thanks to the feedback we receive.