One question, several trustworthy views
Start with recorded sources and pages, then inspect goal progression and currency-separated receipts. A traffic event is not a payment. Missing visitor links remain Unattributed; an observed visit without a campaign or referrer can be Direct.
The public dashboard is a synthetic example, not customer performance. Private reports begin empty and only use the authenticated project’s recorded data.
- Acquisition: source, declared campaign dimensions and page breakdowns with revenue or visitor sorting.
- Behavior: custom goals, ordered page/goal funnels, event search and permission-scoped pseudonymous journeys.
- Time: bounded date ranges, timezone calendar buckets, previous-window comparison and rolling consented activity.
- Operations: saved segments, goal/funnel definitions, exports and an explicit data lifecycle.
Revenue with a separate trust boundary
Verified Stripe payment and refund reconciliation is implemented. An authorized customer Stripe connection, correct account/mode and real provider acceptance are prerequisites. Your own subscription to Reylin is separate from the revenue of your customers.
Product-scoped connections can exclude unrelated products in a shared Stripe account. Unknown or mixed-product payments wait for review instead of being divided by guesswork. MRR is a separate contracted-subscription metric, not receipts, payouts or profit.
What is not promised
- No geographic enrichment/map, prediction scores or cross-device identity.
- No automatic advertising-spend import or full ROAS calculation.
- No claim that every framework or payment provider has a supported connector.
- Remote MCP/OAuth has local protocol tests but is not mounted as a usable public connector. No CLI or assistant-directory listing is available.
- Published guides support five languages; the application, service emails and settings are not fully localized.