PDR-008: Add Analytics, Event Taxonomy, and Conversion Instrumentation

[kas1987]

Objective

Instrument the atlas so the CEO can understand what buyers browse, compare, quiz, save, and inquire about before the full rebuild scales.

Current state

The current frontend is static and data-driven, but there is no formal event taxonomy or analytics layer visible in the inspected code.

Scope

• Define event taxonomy for page view, character view, body view, family view, quiz start/complete, compare add/remove, contact start/submit, CTA click.
• Add lightweight analytics adapter that can be no-op locally and configurable for production.
• Avoid logging sensitive personal form data.
• Add data attributes to key CTAs and cards.
• Add docs for analytics setup and privacy boundaries.
• Prepare optional n8n/CRM webhook handoff for inquiry events.

Acceptance criteria

• Analytics can be enabled/disabled from one config point.
• Events include useful catalog context IDs without personal data leakage.
• Local development does not throw errors when analytics is disabled.
• Inquiry submit event excludes message body, email, phone, and name.
• Documentation lists all event names and payload fields.

Dependencies

• assets/site.js
• contact.html, quiz.html, character.html, body/browse pages
• PDR-006 for CRM-ready intake payload alignment

Suggested owner agent

Auditor with Cartographer implementation support

PDR package

Package this as PDR-008-analytics-event-taxonomy-conversion-instrumentation.md.