Traffic, with a business outcome

Know which visits become paying customers.

Reylin brings consented website events and verified Stripe receipts into one view—so you can compare acquisition sources without mistaking attention for revenue.

Private access only. Entering a domain does not install tracking or create an account.

Watch the demo instead ↗
Read-only product preview

See the question behind every number.

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.

example.reylin.appIllustrative data · not a live report
Explore demo ↗

Loading synthetic report…

Acquisition source

Net receipts
Search$880
Campaign$630
Direct$400
Unattributed$240

Synthetic report · fixed historical window

Loading synthetic report…

01 / Installation guide

From your website to a useful decision.

01

Create a project

Set the exact website origin and choose an attribution window. Keep test and live analytics in separate projects.

02

Collect with permission

Load the tracker, connect it to your consent decision and send the events you actually need. No permission means no tracking request.

03

Join the payment to the visit

Associate the consented visitor ID on your trusted checkout server, then connect the matching Stripe account. Verified receipts can be attributed to recorded touches.

Installation guide
02 / Explore demo

One story, from discovery to payment.

Start with the acquisition source. Follow the recorded journey. Keep confirmed revenue separate from assumptions.

Acquisition and revenue

Compare recorded sources and pages beside currency-separated receipts. Missing associations remain Unattributed, never guessed.

Read the guide →

Goals and ordered funnels

Choose ordered page or goal steps, then see where progression stops. A browser purchase event is not a verified payment.

Read the guide →

Visitor journeys and activity

Read consented event sequences in permission-scoped reports. An empty private project never borrows demonstration numbers.

Read the guide →

Search Console context

Connect separately authorized search data to reporting. The public demo has no Google authorization and does not invent keywords.

Read the guide →
03 / API

A clear starting point for your agent.

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/dashboard
04 / Current connection limits

Connect the pieces you actually use.

A 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.

JavaScriptStripeGoogle Search ConsoleREST API
Explore integrations
05 / USD

A plan that follows your event volume.

Proposed USD prices, not live offers. No checkout, free trial or automatic paid conversion is promised here.

Make your next decision with context.

All guides →

Before you connect.

Are the demo figures real customers or results?

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.

Is net revenue the same as profit?

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.

Will every payment have a marketing source?

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.

Does installing the script automatically track everyone?

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.

Does connecting Stripe activate my subscription to this service?

No. Your customer-revenue connection and your subscription to this service are separate integrations with separate ownership and credentials.

Can I use this as my accounting system?

No. Use your payment provider and accounting records for financial statements. Reconciliation warnings, incomplete imports and the stated reporting boundaries matter.

Find the next useful signal.

Explore the dashboard, understand the measurements, then follow the installation guide for your own website.