Name the behavior, not a person
A goal definition gives an event key a display label, color and description without rewriting historical event identity. Send explicit consented events using the installed tracker. Avoid email addresses, names, account IDs and free-text user input in event names or properties.
Goal property schemas use bounded enum values with explicit missing/excluded-history reporting. They are not arbitrary custom JSON or proof of anonymity.
// Only after the site's own consent decision grants collection:
reylin.consent(true);
reylin.track('signup');Build an ordered funnel
A saved funnel can contain one to twenty validated steps: event goals, declared page predicates/prefixes and an optional final ledger-only payment. Steps must occur in order within the configured conversion window.
Progression reports show entry/step counts, adjacent conversion and drop-off. A seven-step funnel is supported; adding steps is not evidence that historical events exist for them. A missing prerequisite should remain an empty state, not synthetic success.
Payment is not a browser goal
A browser event named purchase cannot create verified revenue. The payment step depends on a reconciled provider payment with an eligible visitor association. Unlinked receipts remain financially visible as Unattributed but cannot invent a person’s funnel path.
Per-step geography/source/revenue matrices and a complete subscription-lifecycle goal stream are not available. Subscription snapshots and cash receipts remain separate reports.
Verify before reading conversion
- Confirm the approved project origin and consent behavior.
- Send one synthetic test event and check its unique identity and recorded timestamp.
- Confirm the event key matches the saved goal rather than only its display label.
- Check step order, time window and eligible visitor history.
- Test payment conversion with authorized provider test fixtures; never use a real charge merely to make a funnel look complete.