Pelcro Autocapture: paywall conversion tracking

🔍 Problem Statement

As a publisher, I can't see where readers drop off in the paywall flow, which limits my ability to improve subscription conversion.

💡 User Story

• As a publisher, I want paywall interactions captured automatically, so that I can find and fix conversion drop-offs without custom tracking code.

• As a Pelcro product team member, I want a standard paywall event schema, so that conversion analysis is consistent across clients and analytics tools.

• As a Pelcro AI harness, I want documented instructions for every event and property, so that I can interpret paywall behavior and help improve conversions for clients.

🎯 Definition of Done (DoD)

• ✔ Given a paywall renders, when a reader interacts with it, then the SDK emits the standard events defined in the Event Definitions below.

• ✔ Given any event, when it is sent, then it carries the common properties defined below.

• ✔ Given a reader identifies or subscribes, when the event fires, then the anonymous ID merges with the known customer ID.

• ✔ Given a reader has not consented, when the paywall renders, then no events are emitted or identifiers stored.

• ✔ Given a client, when it calls the events API [clarify endpoint], then it receives paywall funnel conversion by step, variant, and source.

• ✔ Given the event schema, when the AI harness loads its instructions, then it receives a definition of every event and property, so it can analyze paywall funnels and recommend conversion improvements.

• ✔ This change will impact SDK, UI, and API, specifically JS-SDK event tracking, ReactJS Elements paywall components, and [clarify events API endpoint].

• ✔ This solution will include the following limitations: no session replay; no capture of form input values or personal data; sites not using the Pelcro paywall excluded; [clarify scroll depth and rage-click scope].