What a law firm should check when consent choices change what the team can see: a QA pass before a campaign goes live
Before a new campaign goes live, a law firm can test the full path with a known record. The test should finish at the business system, not at the browser console.
Read the symptom
Consent is part of the measurement context. A tag may not run, a signal may be modeled elsewhere, or two reports may contain rows collected under different choices.
Inspect the path
- Record the consent state for the test visit.
- Check which tags fire before and after the choice is made.
- Compare the browser event with the server side record.
- Write down what the system cannot observe under each state.
Run the QA pass
Treat the consent state as part of the evidence instead of hiding it from the report. Keep the test result with the record it describes so the next review starts with evidence, not a guess.
If you need a persistent record of the path, see ClickTrail.