In this article
New feature: Tracking with Endpoint
We are continuously developing Burst Statistics to be the alternative to Google Analytics, only more user-friendly and privacy-friendly. To help us out, our users have added many feature requests. To name a few, these are now fulfilled with our newest features:
- 1.2 [Page Speed] JS scripts loaded in Footer
- 1.2 Tracking without cookies
- 1.2 optimize tracking script for PageSpeed Insights
And 1.3 will feature even more of your feature requests, including Goals! Want to leave a feature request? Please do, and do it here. Thank you.
And now about tracking with an Endpoint
When switching to Burst 1.2 the method of tracking has automatically switched to “Endpoint” instead of REST API. If this switch was not possible, you will get feedback in the dashboard about how to fix this. If you didn’t, you’re now using a beacon to send data to an endpoint.
This means tracking will sent a request on entry, and will sent a non blocking request on exit. There’s no hindrance of any responses, or unloads during the session which positively affects performance during a session.
The previous method of tracking, the REST API is still used as a fallback. The difference in time spend sending the request is immense. The REST API would average around 300 ms per request on this website. Now tracking with an endpoint averages about 30ms.
An important disclaimer is that using the REST API has no negative side effects for tracking. It just uses more resources, which might impact performance.
Using Turbo Mode with the REST API is also possible. If you have any questions, please let us know on the WordPress forums.