This surface defines how Cortex can capture qualified operational events, preserve authoritative payment state and eventually automate follow-up.
Public page viewed.
Learning, technical skills or project enquiry path selected.
A visitor begins an enquiry.
Enough information exists for routing.
An appropriate service or product is presented.
Authoritative payment confirmation received.
Requested deliverable completed.
Operational follow-up is required.
Counts and conversion rates appear only when a real data source supplies them.
A client-side success event never replaces authoritative payment verification.
API keys and payment secrets remain server-side environment variables.
Operational telemetry is minimized to what is needed for routing and service delivery.