Create a project
Set the exact website origin and choose an attribution window. Keep test and live analytics in separate projects.
Reylin brings consented website events and verified Stripe receipts into one view—so you can compare acquisition sources without mistaking attention for revenue.
Watch the demo instead ↗Change the period or currency to explore this synthetic report. Open the full demo for more views. These examples use synthetic data, not customer results.
Loading synthetic report…
| Search | $880 |
|---|---|
| Campaign | $630 |
| Direct | $400 |
| Unattributed | $240 |
Loading synthetic report…
Set the exact website origin and choose an attribution window. Keep test and live analytics in separate projects.
Load the tracker, connect it to your consent decision and send the events you actually need. No permission means no tracking request.
Associate the consented visitor ID on your trusted checkout server, then connect the matching Stripe account. Verified receipts can be attributed to recorded touches.
Start with the acquisition source. Follow the recorded journey. Keep confirmed revenue separate from assumptions.
Give your assistant the installation brief and documented read API. Public MCP and OAuth connections are still under validation; the setup prompt is not a live connector or a permission grant.
Read agent setup/agent-setup/prompt.md/docs/api/dashboardA consent-aware browser tracker, product-scoped Stripe analytics and an authorized Search Console adapter. Check each connection’s setup and current limits before collecting real data.
Proposed USD prices, not live offers. No checkout, free trial or automatic paid conversion is promised here.
$7 / month
$15 / month
Build a practical SaaS measurement plan: acquisition, activation, verified payments and data quality, with a worked example and a weekly review template.
Read the guide →FOUNDATIONSLearn how revenue attribution joins visits to verified payments, chooses a credit rule, and keeps missing sources, refunds and currencies honest.
Read the guide →FOUNDATIONSDiagnose Direct visits and Unattributed payments separately. Use a practical decision tree without guessing sources or rewriting your history.
Read the guide →No. The demonstration uses labeled synthetic fixtures. Authenticated project views use only that project’s stored records, including an honest zero when nothing has arrived.
No. Here, net receipts are recorded successful payments minus currently successful refunds in the reporting model. Fees, taxes, FX, payouts and formal revenue recognition are outside this view.
No. A valid consented visitor association and an eligible recorded touch are needed. Missing associations remain Unattributed; the service does not fill the gap with a guessed source.
No. Your site must explicitly grant consent before tracking. The tracker can record pageviews and supported SPA navigation automatically after opt-in; custom events require explicit calls. The current tracker uses a session-scoped pseudonymous ID, not fingerprinting or cross-device identification.
No. Your customer-revenue connection and your subscription to this service are separate integrations with separate ownership and credentials.
No. Use your payment provider and accounting records for financial statements. Reconciliation warnings, incomplete imports and the stated reporting boundaries matter.
Explore the dashboard, understand the measurements, then follow the installation guide for your own website.