An analytics parameter contains a form answer

What to change

Review the actual outgoing data and ask which reporting purpose requires each parameter. If unintended collection is confirmed, have the authorised technical owner stop the affected collection and remove unnecessary field values at their source. If real information may already have been sent, involve the responsible privacy and analytics owners to assess the scope and the platform's available deletion process. Keep that assessment separate from proving that future events are corrected; a clean test does not establish what happened previously.

A worked example

Illustrative example

Illustrative test: A sample message is absent from the corrected event while its action count remains. The owner separately records whether earlier collection needs investigation, using restricted evidence rather than copying real messages into the test report.

How to check the result

The current payload matches the documented measurement purpose, and any question about previous collection has an accountable review owner.

A mistake to avoid

Hashing unnecessary text does not justify collecting it, and changing a tag does not remove information already sent.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordUse a distinctive fictional phrase in an authorised test and inspect both event parameters and query strings for unintended copies.Have the technical owner stop confirmed unintended collection, then verify the corrected event still records only the approved action.If past real information may be affected, assign an authorised owner to review its scope and any appropriate platform deletion request.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.