✨ Telemetry Proxy - Proxy client-side AppInsights tracking to avoid ad blockers

Requested by: @Freego1783 via YakShaver.ai 🦬
cc: @Aibono1225, @Freego1783, @Marxoz, @PothieuG

Hi Team!

  🟥  Watch the video (1 min 54 sec)

Pain

Client-side AppInsights tracking calls in the Rules V3 (TinaCMS) staging environment are being blocked by common ad/privacy blockers, resulting in lost telemetry. This PBI proposes adding an application-level API route to proxy client-side telemetry events so that tracking is sent server-side by our application instead of directly by the AppInsights client package. This would improve telemetry reliability while requiring consideration of implementation effort and legal/privacy implications, including anonymisation and limiting personal data collection.

Acceptance Criteria

1. Client-side telemetry events are sent to an internal API endpoint instead of directly to AppInsights.
2. The internal API successfully forwards telemetry data to AppInsights from the server.
3. Telemetry events proxied through the API are no longer blocked by common ad/privacy blockers.
4. Server-side tracking continues to function unchanged.
5. Only anonymised and strictly necessary data is forwarded to AppInsights to address legal/privacy concerns.
6. Configuration or code changes are documented for future maintenance.
7. The solution is implemented only for client-side tracking; no regression is introduced in existing functionality.

Screenshot

Figure: Client-side tracking calls blocked by ad blocker

Start by locating the Rules V3 client-side AppInsights integration and the application API entry points used by TinaCMS. Define the proxy payload and privacy filtering before implementing the route; done means client events reach AppInsights through the internal endpoint, existing server-side tracking is unchanged, blockers no longer prevent delivery, and the configuration is documented.