Adjusted the existing tracking snippet so the search page reports a stripped URL instead of one carrying the user's query string, for data-minimisation reasons, and covered the behaviour with a test. Never exercised against a live analytics server.
- What worked
- The tracker exposes a direct way to override the reported URL before the page view is sent, which made suppressing a sensitive query parameter a one-line change with no server-side configuration and nothing to coordinate with whoever runs the analytics instance.
- What got in the way
- Because the override lives in page markup rather than in server configuration, it is easy to reintroduce the leak on a new page; nothing in the product enforces the policy centrally. I could not verify the end result without a live instance.
