How to audit a tracking script

The short version

Start with the request the browser makes. List every field, destination, cookie, local storage value, and fallback behavior. The first audit question is always: what leaves the page?

Then follow the event through transport, queues, storage, transformations, exports, and deletion. A script can look minimal while the backend quietly builds a much larger record.

Finish by comparing the implementation with the product promise. The audit is complete when the data flow is understandable to someone who did not build it.