Notes: Tracking Integration

Test tracking requests, send multiple events, and handle special tracking cases correctly.

Transfer test possibilities

If the JSON object is sent correctly, the interface returns the HTTP status code 200. If there is a problem with the tracking request, the response returns HTTP status code 400 together with an error message such as The parameter [id] is required and cannot be empty. This makes it easy to validate the integration and confirm that all required parameters were sent.

Another good way to verify your tracking integration is to use the Analytics Dashboard in the FactFinder Management Interface.

Sending of multiple events in one request

FactFinder NG lets you send multiple events in one URL or method request. This is especially useful for buy events, because it reduces the total number of requests and lowers network traffic.

Only events of the same type can be sent in a single request. For example, you can send multiple buy events together or multiple cart events together, but not a mix of both. To send multiple events, pass the relevant parameters multiple times.

See Swagger-UI for examples.

“Add to shopping cart” feature on the result page

If users can add products directly to the shopping basket from the search results page, send both click data and cart data when that happens. That is the only way to determine that the item was added to the basket directly from a search result.

---

Other

You can also trigger tracking events in the source code when the details page is opened. This avoids relying on JavaScript in the visitor’s browser. If you do this, make sure all required parameters are still sent.