Analytics QA should begin with a small set of critical journeys. Test fresh installs, returning users, failed actions and consent changes. Inspect raw payloads rather than relying only on dashboard totals.
Keep evidence with the release
Record the app version, device, environment, consent state and expected payload for each test. When a defect appears later, this evidence narrows the investigation.
Automate stable checks where possible, but retain manual tests for context-sensitive behaviour. Assign an owner to approve analytics alongside functional QA.
Turn uncertainty into a testable question
If your team is seeing these issues, document the affected journey, platform, app version, expected behaviour and report. This creates a useful starting point for an implementation review.