Conversion Event Boundary

WeAcuRe can measure public page quality and product interest only after the event names, purpose, privacy wording, and consent boundary are documented. The current prototype has no campaign tags, no conversion scripts, and no audience lists.

Current status

Allowed first events

• Landing page view by page group, region page, and device class.
• Pricing page view and checkout-intent page view.
• Early access button click before a live form endpoint is enabled.
• Study pack interest, clean export interest, and glossary interest.
• Static error page visit and broken internal link report.

Blocked event payloads

• Do not send birth date, birth time, location, chart output, palace labels, star labels, or glossary selections.
• Do not send email, phone number, payment identifier, support message, private notes, or user-uploaded files.
• Do not create audience lists, retargeting groups, or lookalike groups before explicit review.
• Do not combine campaign events with member, payment, support, or chart records.

Before event tracking is enabled

• Record every event name, page, purpose, and blocked payload before activation.
• Confirm the Conversion Measurement Plan before mapping event names to any platform.
• Update Privacy, Terms, Contact, and Measurement Readiness with matching wording.
• Review the ad platform account boundary before connecting campaign events.
• Run static checks and browser smoke checks before sending paid traffic.

Related pages

Review Measurement Readiness, Conversion Measurement Plan, Search and Ads Readiness, Campaign Copy Readiness, Landing Page Readiness, Checkout Intent Boundary, Email Consent Boundary, Birth Data Privacy, Privacy Boundary, and Terms before enabling campaign events.