Feature request: disable client-side tracking via Pixel

[thomkrupa]

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!

[leandrosimoes]

This is a real problem in the company where I work. Google is disapproving all our marketing pages because of this tracking, and we are losing lots of money. I stopped using builder.io for our marketing pages and started looking for a new solution. It is a shame.

[samijaber]

Hi @leandrosimoes, can you elaborate on how Google is "disapproving" your marketing pages? What is the exact issue you're encountering? How are you losing money?

For the record, we answered @thomkrupa on a different channel, but will paraphrase here:

Our pixel is used for commercial purposes to track the number of views a content entry receives. Our pixel is a javascript-free API endpoint that fires when content is rendered. No identifying or personal information is captured nor stored.