Migration to the Analytics API

With the new AI Cloud dashboards and the new logging, we will be deprecating the ReportingAPI by December 31st, 2025. After that date, no data will be downloadable through the ReportingAPI. To keep access to your logging data, you should migrate to our new Analytics API. This API is already usable; you can migrate now or use both in parallel until 31 Dec 2025.

The credentials for the Analytics API are the same as for the ReportingAPI. The authorization mechanism is also the same. We’ve explained how to use those credentials in How to get an interaction log from the Reporting API using Postman.

To access the Analytics API, you should call the https://analytics.digitalcx.com/:CUSTOMERKEY/projects/:PROJECTKEY/interactions endpoint.

Request Parameters:

These parameters influence the presence of data in two columns and otherwise filter or limit the rows of data returned.

curl:
curl --location 'https://analytics.digitalcx.com/:CUSTOMERKEY/projects/:PROJECTKEY/interactions?culture=&filterText=&paginateData=true&continuationToken=&includeUserinfo=false&interactionTypes=2&sessionMode=&environment=Production&mainInteractionTypes=&activeSessionOnly=true&endDate=&startDate='

Notes on Parameters

ActiveSessionOnly

An ‘Active Session’ is defined as a session containing interactions of types other than Events, DataRetrievals or the starts of Dialogs.
Having this as a filter helps you only retrieve actually interesting data instead of a lot of ‘'irrelevant’' Events.

Interaction types

Interaction type filter:

• Event: 1

• QA: 2

• QA and Event: 3

• FaqClick: 4

• Dialog: 8

• LinkClick: 16

• Feedback: 32

• FaqSearch: 64

• TransactionalDialog: 128

• DataRetrieval: 256

• GenerativeAI: 512

• All: All

A combination of any would mean an overlap, not exact match

Example: Interactiontypes: 131 would return interaction with types that are event or QA or TDialog

The InteractionTypes filter queries on the allinteractiontypes column. MainInteractionType queries the mainInteractiontype  column; the type that was the most relevant to that interaction from a recognition perspective. The Interaction counts you see in the Management Report dashboard for various interactiontypes base themselves on the MainInteractionType.

If you wish to retrieve all interactions of a particular type, as the old ReportingAPI used to do, use the InteractionTypes filter. If you wish to retrieve all interactions of a given type where the interactiontype is the one used for recognition, use MainInteractionType. This is mainly an important distinction for (Transactional) Dialogs started by other interactions.

The interactiontypes this makes the most difference for are Dialogs, Transactional Dialogs, Events and DataRetrievals. GenerativeAI interactions will usual have Q&A as the Maininteractiontype. However, interactions with HALO agents may have GenerativeAI as the Maininteractiontype. For Q&A, FAQClicks, FAQSearches, Linkclicks and Feedback both filters should give the same results.

DataRetrievals were not available for download in the older interactionlogs. They are used to determine a total (including inactive) sessioncount and to estimate which FAQs were shown how often. In dashboards that do not report on these numbers, DataRetrievals are also not used.

SessionMode

Possible session modes:

• Public (Default)

• Internal

• Test  (Interactions to the Staging engine should have this Session Mode)

• Monitor

IncludeUserInfo

Additional_sessioninfo and variables (or other columns later) have some potentially sensitive details.
These columns will only be included when specifically requested and with the correct user roles (admin or content engineer) to be able to see the relevant columns – same as with the ReportingAPI.

Limitations on the request

• You cannot request a date more than 90 days back.

• You cannot request more than one day’s worth of data at the same time

• ContinuationToken will be in the response header with continuationToken as key

• Returns a csv.

• When the user does not have enough rights or includeUserInfo: false was set, additional_sessioninfo and variables will be empty strings

Response

Content type: text/csv

If the accept header "accept", "application/json" is passed along in the request the response will be in JSON.

Possible headers: continuationToken: string

For returned columns, see: Interaction Logs from the Analytics API. These colums will be either flat values or have a JSON structure.

Error and Status Codes