Feature request: disable client-side tracking via Pixel

Hey,

This is more like a feature request.

I believe it's not appropriate to track traffic by Builder via Pixel, especially when there is a canTrack prop. Even if it's set to false, it still sends tracking requests.

I recently discovered this, and it's a significant blocker for us and many of our clients. This practice is not GDPR-friendly and is quite unusual for a Headless CMS.

I think tracking should happen server-side. I assume Builder has data on the number of API requests, etc.

What is Builder's stance on this? I saw a post on the community forum stating that it's a "critical" feature. I would like to raise awareness about this issue, get a clear response from Builder, and eventually plan a migration for ourselves if there is no option to disable client-side tracking.

Thanks!

The issue identifies the client-side Pixel tracking path and the canTrack prop, but names no files or tests. Start by locating those entry points and documenting the current request behavior; done requires an agreed, tested way to disable client-side tracking and a maintainer decision on scope.

Written by the indexing model from the issue text.