Notes
Consent-Aware Filters for App Analytics
Collect only properties that support decisions you actually review. Unused fields add QA cost and privacy risk without improving product judgment.
Store consent state as a first-class property so analysts can filter compliant cohorts without rebuilding pipelines each quarter.
Separate identity keys from content payloads. Prefer hashed identifiers where possible and document retention for raw event stores.
Disable vendor auto-collection you do not need before the first production release—not after a questionnaire arrives.