AnalyticsClient

algoliasearch.api.AnalyticsClient
See theAnalyticsClient companion object
class AnalyticsClient(appId: String, apiKey: String, region: Option[String], clientOptions: ClientOptions) extends ApiClient

Attributes

Companion
object
Graph
Supertypes
class ApiClient
trait AutoCloseable
class Object
trait Matchable
class Any

Members list

Value members

Concrete methods

def customDelete[T : Manifest](path: String, parameters: Option[Map[String, Any]], requestOptions: Option[RequestOptions])(implicit evidence$1: Manifest[T], ec: ExecutionContext): Future[T]

This method lets you send requests to the Algolia REST API.

This method lets you send requests to the Algolia REST API.

Value parameters

parameters

Query parameters to apply to the current query.

path

Path of the endpoint, anything after "/1" must be specified.

Attributes

def customGet[T : Manifest](path: String, parameters: Option[Map[String, Any]], requestOptions: Option[RequestOptions])(implicit evidence$1: Manifest[T], ec: ExecutionContext): Future[T]

This method lets you send requests to the Algolia REST API.

This method lets you send requests to the Algolia REST API.

Value parameters

parameters

Query parameters to apply to the current query.

path

Path of the endpoint, anything after "/1" must be specified.

Attributes

def customPost[T : Manifest](path: String, parameters: Option[Map[String, Any]], body: Option[Any], requestOptions: Option[RequestOptions])(implicit evidence$1: Manifest[T], ec: ExecutionContext): Future[T]

This method lets you send requests to the Algolia REST API.

This method lets you send requests to the Algolia REST API.

Value parameters

body

Parameters to send with the custom request.

parameters

Query parameters to apply to the current query.

path

Path of the endpoint, anything after "/1" must be specified.

Attributes

def customPut[T : Manifest](path: String, parameters: Option[Map[String, Any]], body: Option[Any], requestOptions: Option[RequestOptions])(implicit evidence$1: Manifest[T], ec: ExecutionContext): Future[T]

This method lets you send requests to the Algolia REST API.

This method lets you send requests to the Algolia REST API.

Value parameters

body

Parameters to send with the custom request.

parameters

Query parameters to apply to the current query.

path

Path of the endpoint, anything after "/1" must be specified.

Attributes

def getAddToCartRate(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetAddToCartRateResponse]

Retrieves the add-to-cart rate for all your searches with at least one add-to-cart event, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day. The rate is the number of add-to-cart conversion events divided by the number of tracked searches. A search is tracked if it returns a queryID (clickAnalytics is true). This differs from the response's count, which shows the overall number of searches, including those where clickAnalytics is false. There's a difference between a 0 and null add-to-cart rate when clickAnalytics is enabled: - Null means there were no queries: since Algolia didn't receive any events, the add-to-cart rate is null. - 0 mean there were queries but no add-to-cart events were received.

Retrieves the add-to-cart rate for all your searches with at least one add-to-cart event, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day. The rate is the number of add-to-cart conversion events divided by the number of tracked searches. A search is tracked if it returns a queryID (clickAnalytics is true). This differs from the response's count, which shows the overall number of searches, including those where clickAnalytics is false. There's a difference between a 0 and null add-to-cart rate when clickAnalytics is enabled: - Null means there were no queries: since Algolia didn't receive any events, the add-to-cart rate is null. - 0 mean there were queries but no add-to-cart events were received.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getAverageClickPosition(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetAverageClickPositionResponse]

Retrieves the average click position of your search results, including a daily breakdown. The average click position is the average of all clicked search result positions. For example, if users only ever click on the first result for any search, the average click position is 1. By default, the analyzed period includes the last eight days including the current day. An average of null when clickAnalytics is enabled means Algolia didn't receive any click events for the queries. The average is null until Algolia receives at least one click event.

Retrieves the average click position of your search results, including a daily breakdown. The average click position is the average of all clicked search result positions. For example, if users only ever click on the first result for any search, the average click position is 1. By default, the analyzed period includes the last eight days including the current day. An average of null when clickAnalytics is enabled means Algolia didn't receive any click events for the queries. The average is null until Algolia receives at least one click event.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getClickPositions(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetClickPositionsResponse]

Retrieves the positions in the search results and their associated number of clicks. This lets you check how many clicks the first, second, or tenth search results receive. An average of 0 when clickAnalytics is enabled means Algolia didn't receive any click events for the queries.

Retrieves the positions in the search results and their associated number of clicks. This lets you check how many clicks the first, second, or tenth search results receive. An average of 0 when clickAnalytics is enabled means Algolia didn't receive any click events for the queries.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getClickThroughRate(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetClickThroughRateResponse]

Retrieves the click-through rate (CTR) for all your searches with at least one click event, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day. There's a difference between a 0 and null CTR when clickAnalytics is enabled: - Null means there were no queries: since Algolia didn't receive any events, CTR is null. - 0 mean there were queries but no click events were received.

Retrieves the click-through rate (CTR) for all your searches with at least one click event, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day. There's a difference between a 0 and null CTR when clickAnalytics is enabled: - Null means there were no queries: since Algolia didn't receive any events, CTR is null. - 0 mean there were queries but no click events were received.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getConversionRate(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetConversionRateResponse]

Retrieves the conversion rate (CR) for all your searches with at least one conversion event, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day. There's a difference between a 0 and null CR when clickAnalytics is enabled: - Null means there were no queries: since Algolia didn't receive any events, CR is null. - 0 mean there were queries but no conversion events were received.

Retrieves the conversion rate (CR) for all your searches with at least one conversion event, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day. There's a difference between a 0 and null CR when clickAnalytics is enabled: - Null means there were no queries: since Algolia didn't receive any events, CR is null. - 0 mean there were queries but no conversion events were received.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getNoClickRate(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetNoClickRateResponse]

Retrieves the fraction of searches that didn't lead to any click within a time range, including a daily breakdown. It also returns the number of tracked searches and tracked searches without clicks. By default, the analyzed period includes the last eight days including the current day.

Retrieves the fraction of searches that didn't lead to any click within a time range, including a daily breakdown. It also returns the number of tracked searches and tracked searches without clicks. By default, the analyzed period includes the last eight days including the current day.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getNoResultsRate(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetNoResultsRateResponse]

Retrieves the fraction of searches that didn't return any results within a time range, including a daily breakdown. It also returns the count of searches and searches without results used to compute the rates. By default, the analyzed period includes the last eight days including the current day.

Retrieves the fraction of searches that didn't return any results within a time range, including a daily breakdown. It also returns the count of searches and searches without results used to compute the rates. By default, the analyzed period includes the last eight days including the current day.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getPurchaseRate(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetPurchaseRateResponse]

Retrieves the purchase rate for all your searches with at least one purchase event, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day. The rate is the number of purchase conversion events divided by the number of tracked searches. A search is tracked if it returns a query ID (clickAnalytics is true). This differs from the response's count, which shows the overall number of searches, including those where clickAnalytics is false. There's a difference between a 0 and null purchase rate when clickAnalytics is enabled: - Null means there were no queries: since Algolia didn't receive any events, the purchase rate is null. - 0 mean there were queries but no purchase conversion events were received.

Retrieves the purchase rate for all your searches with at least one purchase event, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day. The rate is the number of purchase conversion events divided by the number of tracked searches. A search is tracked if it returns a query ID (clickAnalytics is true). This differs from the response's count, which shows the overall number of searches, including those where clickAnalytics is false. There's a difference between a 0 and null purchase rate when clickAnalytics is enabled: - Null means there were no queries: since Algolia didn't receive any events, the purchase rate is null. - 0 mean there were queries but no purchase conversion events were received.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getRevenue(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetRevenue]

Retrieves revenue-related metrics, such as the total revenue or the average order value. To retrieve revenue-related metrics, send purchase events. By default, the analyzed period includes the last eight days including the current day. Revenue is based on purchase conversion events (a conversion event with an eventSubtype attribute of purchase). The revenue is the price attribute multiplied by the quantity attribute for each object in the event's objectData array.

Retrieves revenue-related metrics, such as the total revenue or the average order value. To retrieve revenue-related metrics, send purchase events. By default, the analyzed period includes the last eight days including the current day. Revenue is based on purchase conversion events (a conversion event with an eventSubtype attribute of purchase). The revenue is the price attribute multiplied by the quantity attribute for each object in the event's objectData array.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getSearchesCount(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetSearchesCountResponse]

Retrieves the number of searches within a time range, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day.

Retrieves the number of searches within a time range, including a daily breakdown. By default, the analyzed period includes the last eight days including the current day.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getSearchesNoClicks(index: String, startDate: Option[String], endDate: Option[String], limit: Option[Int], offset: Option[Int], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetSearchesNoClicksResponse]

Retrieves the most popular searches that didn't lead to any clicks, from the 1,000 most frequent searches. For each search, it also returns the number of displayed search results that remained unclicked.

Retrieves the most popular searches that didn't lead to any clicks, from the 1,000 most frequent searches. For each search, it also returns the number of displayed search results that remained unclicked.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

limit

Number of items to return.

offset

Position of the first item to return.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getSearchesNoResults(index: String, startDate: Option[String], endDate: Option[String], limit: Option[Int], offset: Option[Int], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetSearchesNoResultsResponse]

Retrieves the 1,000 most frequent searches that produced zero results.

Retrieves the 1,000 most frequent searches that produced zero results.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

limit

Number of items to return.

offset

Position of the first item to return.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getStatus(index: String, requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetStatusResponse]

Retrieves the time when the Analytics data for the specified index was last updated. If the index has been recently created or no search has been performed yet the updated time is null. The Analytics data is updated every 5 minutes.

Retrieves the time when the Analytics data for the specified index was last updated. If the index has been recently created or no search has been performed yet the updated time is null. The Analytics data is updated every 5 minutes.

Required API Key ACLs:

  • analytics

Value parameters

index

Index name.

Attributes

def getTopCountries(index: String, startDate: Option[String], endDate: Option[String], limit: Option[Int], offset: Option[Int], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetTopCountriesResponse]

Retrieves the countries with the most searches in your index.

Retrieves the countries with the most searches in your index.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

limit

Number of items to return.

offset

Position of the first item to return.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getTopFilterAttributes(index: String, search: Option[String], startDate: Option[String], endDate: Option[String], limit: Option[Int], offset: Option[Int], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetTopFilterAttributesResponse]

Retrieves the 1,000 most frequently used filter attributes. These are attributes of your records that you included in the attributesForFaceting setting.

Retrieves the 1,000 most frequently used filter attributes. These are attributes of your records that you included in the attributesForFaceting setting.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

limit

Number of items to return.

offset

Position of the first item to return.

search

Search query.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getTopFilterForAttribute(attribute: String, index: String, search: Option[String], startDate: Option[String], endDate: Option[String], limit: Option[Int], offset: Option[Int], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetTopFilterForAttributeResponse]

Retrieves the 1,000 most frequent filter (facet) values for a filter attribute. These are attributes of your records that you included in the attributesForFaceting setting.

Retrieves the 1,000 most frequent filter (facet) values for a filter attribute. These are attributes of your records that you included in the attributesForFaceting setting.

Required API Key ACLs:

  • analytics

Value parameters

attribute

Attribute name.

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

limit

Number of items to return.

offset

Position of the first item to return.

search

Search query.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getTopFiltersNoResults(index: String, search: Option[String], startDate: Option[String], endDate: Option[String], limit: Option[Int], offset: Option[Int], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetTopFiltersNoResultsResponse]

Retrieves the 1,000 most frequently used filters for a search that didn't return any results. To get the most frequent searches without results, use the Retrieve searches without results operation.

Retrieves the 1,000 most frequently used filters for a search that didn't return any results. To get the most frequent searches without results, use the Retrieve searches without results operation.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

limit

Number of items to return.

offset

Position of the first item to return.

search

Search query.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getTopHits(index: String, search: Option[String], clickAnalytics: Option[Boolean], revenueAnalytics: Option[Boolean], startDate: Option[String], endDate: Option[String], limit: Option[Int], offset: Option[Int], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetTopHitsResponse]

Retrieves the object IDs of the 1,000 most frequent search results. If you set the clickAnalytics query parameter to true, the response also includes: - Tracked searches count. Tracked searches are Search API requests with the clickAnalytics parameter set to true. This differs from the response's count, which shows the overall number of searches, including those where clickAnalytics is false. - Click count - Click-through rate (CTR) - Conversion count - Conversion rate (CR) - Average click position If you set the revenueAnalytics parameter to true, the response also includes: - Add-to-cart count - Add-to-cart rate (ATCR) - Purchase count - Purchase rate - Revenue details for each currency There's a difference between 0% rates and null rates: - Null means there were no queries: since Algolia didn't receive any events, the rates (CTR, CR, ATCR, purchase rate) are null. - 0% rates mean there were queries but no click or conversion events were received.

Retrieves the object IDs of the 1,000 most frequent search results. If you set the clickAnalytics query parameter to true, the response also includes: - Tracked searches count. Tracked searches are Search API requests with the clickAnalytics parameter set to true. This differs from the response's count, which shows the overall number of searches, including those where clickAnalytics is false. - Click count - Click-through rate (CTR) - Conversion count - Conversion rate (CR) - Average click position If you set the revenueAnalytics parameter to true, the response also includes: - Add-to-cart count - Add-to-cart rate (ATCR) - Purchase count - Purchase rate - Revenue details for each currency There's a difference between 0% rates and null rates: - Null means there were no queries: since Algolia didn't receive any events, the rates (CTR, CR, ATCR, purchase rate) are null. - 0% rates mean there were queries but no click or conversion events were received.

Required API Key ACLs:

  • analytics

Value parameters

clickAnalytics

Whether to include metrics related to click and conversion events in the response.

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

limit

Number of items to return.

offset

Position of the first item to return.

revenueAnalytics

Whether to include metrics related to revenue events in the response.

search

Search query.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getTopSearches(index: String, clickAnalytics: Option[Boolean], revenueAnalytics: Option[Boolean], startDate: Option[String], endDate: Option[String], orderBy: Option[OrderBy], direction: Option[Direction], limit: Option[Int], offset: Option[Int], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetTopSearchesResponse]

Returns the most popular searches. For each search, it also includes the average number of hits. If you set the clickAnalytics query parameter to true, the response also includes - Tracked searches count. Tracked searches are Search API requests with the clickAnalytics parameter set to true. This differs from the response's count, which shows the overall number of searches, including those where clickAnalytics is false. - Click count - Click-through rate (CTR) - Conversion count - Conversion rate (CR) - Average click position If you set the revenueAnalytics query parameter to true, the response also includes: - Add-to-cart count - Add-to-cart rate (ATCR) - Purchase count - Purchase rate - Revenue details for each currency There's a difference between 0% rates and null rates: - Null means there were no queries: since Algolia didn't receive any events, the rates (CTR, CR, ATCR, purchase rate) are null. - 0% rates mean there were queries but no click or conversion events were received.

Returns the most popular searches. For each search, it also includes the average number of hits. If you set the clickAnalytics query parameter to true, the response also includes - Tracked searches count. Tracked searches are Search API requests with the clickAnalytics parameter set to true. This differs from the response's count, which shows the overall number of searches, including those where clickAnalytics is false. - Click count - Click-through rate (CTR) - Conversion count - Conversion rate (CR) - Average click position If you set the revenueAnalytics query parameter to true, the response also includes: - Add-to-cart count - Add-to-cart rate (ATCR) - Purchase count - Purchase rate - Revenue details for each currency There's a difference between 0% rates and null rates: - Null means there were no queries: since Algolia didn't receive any events, the rates (CTR, CR, ATCR, purchase rate) are null. - 0% rates mean there were queries but no click or conversion events were received.

Required API Key ACLs:

  • analytics

Value parameters

clickAnalytics

Whether to include metrics related to click and conversion events in the response.

direction

Sorting direction of the results: ascending or descending.

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

limit

Number of items to return.

offset

Position of the first item to return.

orderBy

Attribute by which to order the response items. If the clickAnalytics parameter is false, only searchCount is available.

revenueAnalytics

Whether to include metrics related to revenue events in the response.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

def getUsersCount(index: String, startDate: Option[String], endDate: Option[String], tags: Option[String], requestOptions: Option[RequestOptions])(implicit ec: ExecutionContext): Future[GetUsersCountResponse]

Retrieves the number of unique users within a time range, including a daily breakdown. Since it returns the number of unique users, the sum of the daily values might be different from the total number. By default: - Algolia distinguishes search users by their IP address, unless you include a pseudonymous user identifier in your search requests with the userToken API parameter or x-algolia-usertoken request header. - The analyzed period includes the last eight days including the current day.

Retrieves the number of unique users within a time range, including a daily breakdown. Since it returns the number of unique users, the sum of the daily values might be different from the total number. By default: - Algolia distinguishes search users by their IP address, unless you include a pseudonymous user identifier in your search requests with the userToken API parameter or x-algolia-usertoken request header. - The analyzed period includes the last eight days including the current day.

Required API Key ACLs:

  • analytics

Value parameters

endDate

End date of the period to analyze, in YYYY-MM-DD format.

index

Index name.

startDate

Start date of the period to analyze, in YYYY-MM-DD format.

tags

Tags by which to segment the analytics. You can combine multiple tags with OR and AND. Tags must be URL-encoded. For more information, see Segment your analytics data.

Attributes

Inherited methods

override def close(): Unit

Attributes

Definition Classes
ApiClient -> AutoCloseable
Inherited from:
ApiClient
def setClientApiKey(apiKey: String): Unit

Attributes

Inherited from:
ApiClient