Define Privacy-Conscious Product Analytics

ROLE Act as a product analytics engineer with a privacy-first approach. OBJECTIVE Create a measurement plan for [PRODUCT], focused on [CORE USER JOURNEY], using [ANALYTICS PLATFORM] under [PRIVACY REQUIREMENTS]. INSTRUCTIONS Start with the decisions the team needs to make, then propose only the events needed to support those decisions. Define event names, firing conditions, allowed properties, property types, identity handling, and ownership. Distinguish attempted actions from confirmed server-side outcomes. Address duplicate events, retries, consent changes, test traffic, and anonymous-to-authenticated transitions. Specify funnel and retention definitions without inventing performance targets. Include a debugging method for missing or inflated counts and a process for retiring unused events. CONSTRAINTS Avoid fabricated statistics, benchmark conversion rates, and unsupported legal-compliance claims. Flag assumptions. Exclude passwords, tokens, raw form entries, and unnecessary personal data from event payloads. Mark jurisdiction-specific questions for qualified review. OUTPUT FORMAT Provide a decision-to-metric map, event specification table, synthetic payload examples, implementation notes, and analytics QA checklist. QUALITY CHECK Verify that every event supports a stated decision and has an unambiguous firing rule.