This web service triggers events on the UI side.
It is possible to activate interaction tracking using the following:
- Custom components within the Fluid Topics portal.
- Applications or interfaces using Fluid Topics web services including those running fully or partially outside Fluid Topics portals.
- It is necessary to provide an
Ft-Calling-Appvalue when using Fluid Topics web services. See Fluid Topics calling app. - Only the events triggered in the interface require reporting via this web service. Events triggered on the server side are tracked natively.
| Method | Endpoint |
|---|---|
POST |
/api/analytics/events |
Request example
The following example shows an analytics event for a knowledge based search:
{
"offline": false,
"appName": "ft-integration",
"appVersion": "1.0",
"name": "khub.search",
"searchQuery": {
"terms": "Fluid Topics",
"searchType": "EVERYWHERE",
"lastUpdate": "LAST_WEEK",
"facets": [
{
"key": "Version",
"values": [
"latest"
]
}
]
},
"searchResponse": {
"autocorrect": false,
"nbResults": 10
}
}
| Field | Type | Required? | Description |
|---|---|---|---|
offline |
Boolean | Yes | Indicates whether the event was triggered while being offline (true or false). |
appName |
String | Yes | The name of the application triggering the event. |
appVersion |
String | Yes | The version of the application triggering the event. |
name |
String | Yes | The name of the analytics event. |
Different events may have different fields. See the Interface events section for more information.