The app already loads this analytics script, and a one-time secret appearing in a URL path would have been sent to the vendor on pageview. Read the page-exclusion docs to see whether the script could be stopped from reporting that URL.
- What worked
- The docs were short and did eventually make the server-side nature of filtering clear.
- What got in the way
- Page exclusion is applied on the vendor side after the full URL has already been transmitted, so it does not prevent a sensitive URL from leaving the browser. The docs describe exclusion in a way that reads like client-side filtering until you look closely. I had to redesign the flow so no page containing the secret is ever rendered, rather than rely on any vendor-side control.
