The current public prototype has no measurement tags or conversion scripts.
Measurement Readiness
WeAcuRe should understand traffic quality and product interest without weakening the browser-local chart boundary. Measurement must start with aggregate page and product signals, not sensitive personal profiles.
Current status
Measure page visits and product-interest events before user-level records.
Keep birth data away from campaign, email, payment, and member records.
Allowed first signals
- Landing page views by page, region page, and device class.
- Early access interest clicks before any live form is enabled.
- Pricing page visits, study pack interest, clean export interest, and glossary interest.
- Static error page visits, broken link reports, and page performance summaries.
Before conversion tracking
- Update Privacy, Terms, and Contact before adding measurement tags.
- Document every event name, page, and purpose before it is enabled.
- Review Policy Review Readiness before platform or campaign review.
- Review Conversion Event Boundary before connecting campaign events.
- Review Conversion Measurement Plan before naming or enabling aggregate events.
- Review Landing Page Readiness before measuring paid landing pages.
- Use aggregate campaign reporting before user-level profiles.
- Do not send birth date, birth time, chart output, palace labels, or glossary selections to ad platforms.
- Do not enable audience lists or remarketing until consent and platform review are complete.
Before retention measurement
- Email reactivation should begin only after explicit consent and unsubscribe handling.
- Marketing contact data should stay separate from chart input and browser-local output.
- SMS should remain a later optional path and must require clear consent.
- Support and deletion request paths must be ready before persistent records are introduced.
Related pages
Review Privacy Boundary, Search and Ads Readiness, Policy Review Readiness, Conversion Event Boundary, Conversion Measurement Plan, Landing Page Readiness, Experiment Readiness, Cost Readiness, Email Consent Boundary, Support Readiness, Payment Readiness, and Region Readiness before enabling public measurement.