Gate tracking behind consent and prove nothing fires before it
Tracking that starts before the reader has agreed to it, gated with a network capture as proof.
The ticket
Ensure no tracking fires before consent is given.
Acceptance criteria
- A network capture shows no analytics calls before consent
- Consent state persists and is respected on later visits
- Withdrawing consent stops collection
- The check runs automatically rather than being verified by hand once
What lands as proof
A network capture from a fresh session, which is the only evidence that nothing fires early.
Why teams defer it
- It works correctly in the developer's browser, where consent was accepted months ago.
- Third-party scripts often start collecting on load regardless of the consent wrapper around them.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: ensure no tracking fires before consent is given. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means network capture showing no calls until consent is given, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.