Released 2022.06.28

• We updated the aggributes/event_sources endpoint to return the new properties “hidden” and “source_group” for each event source. We also provided a new aggributes/event_sources_groups endpoint that returns the full list of event source groups.

Released 2022.05.17

• New feature:  We added the endpoint /transformations/long_tail to gather long-tail user questions and their related information.

Released 2022.05.03

• New feature:  We added the endpoint /transformations/billing to gather the metrics that Inbenta uses to calculate Inbenta solutions' cost.

Released 2022.01.25

• New feature: We added new endpoints to obtain the rating types and values: /aggributes/rating_types and /aggributes/ratings.

Released 2021.09.07

• Fixed: The aggregates/appearances_and_clicks_by_uq endpoint was not returning results whose num_appearances_with_click_x_appearance value was a number between 0.5 and 1. It is fixed now.

Released 2021.08.10

• Fixed: We fixed the total count on aggregates/appearances_and_clicks_by_uq when using the groupby setting.
• Fixed: We fixed the env parameter in the response for some aggregates that were returning internal database values instead of the descriptive names "development", "preproduction" or "production". Now, the descriptive names are returned.
• A new filter is available for the field "num_appearances_with_click_x_appearances" when the /aggregates/appearances_and_clicks_by_uq endpoint is called. This filter accepts values between 0 and 1.

Released 2021.07.27

• Added: The clicks to push contents (num_clicks_push) were included to the aggregates/total_clicks_by_content_id endpoint.

Released 2021.03.09

• Added: The clicks to push contents were included to the /aggregates/total_clicks_by_type endpoint.

Released 2020.07.22

• Fixed: In the API routes, the explanation of the date format for aggregates was incorrect, which caused confusion. This is now fixed.

Released 2020.03.04

• Added: You can now send multiple session ids at once as an aggregate filter.

Released 2019.10.30

• Added: We added the possibility to create grouping in aggregates. This allows you to get data grouped by day, month or year. When data is grouped, all metrics for each aggregate will come as a total in the response by default. Average, min and max values can also be obtained by using the template "_". (e.g. if there is a metric named "num_sessions", you can ask for "total_num_sessions" as well as "average_num_sessions".

Released 2019.10.16

• Added: You can now use null values as filters on all fields, even if they allow multiple values.

Released 2019.10.02

• Improved API Routes and API definitions in the Developers Portal. API Routes now clearly define properties for raw events and the API Definitions was cleaned up to remove redundant information and show only relevant entities for developers.
• Fixed: A bug was found where, when a property of an aggregate did not have any values, an array with a null value was returned. This is now fixed.

Released 2019.09.18

• Added: We added a "no_results_count" metric to the "session_details" aggregate. It counts how many events in a particular session contained the "NO_RESULTS" data key. This new metric is not returned by default: To start using it, you must add it to the "properties" filter.

Released 2019.05.26

• Added: Aggregates endpoints. These endpoints give you access to aggregated data. The metadata endpoint gives you information about what aggregates are available at a given time. This first version introduces the aggregate "session_details" that groups sessions together based on their session_id. For more information, see Reporting API Routes.

Released 2019.05.15

• Added: Aggributes endpoints. Aggributes are attribute collections that help you build your aggregates and enrich your tracking data. The API has now two endpoints to retrieve them, /aggributes to see which ones are available and /aggributes/{key} to get all the values for a specific one. For more information, see Reporting API Routes.

Released 2019.04.03

• First release.