Analytics by 5H3LL · Learn · Pricing

5H3LL product guides · Updated 27 October 2026

From a SaaS campaign to a recorded payment

Use verified payment data with traffic, goals and journeys to investigate which sources receive revenue credit. Keep profit and causal impact separate from attribution.

Connect the two parts of the journey

The browser tracker observes consenting visitors and their campaign context. A supported backend payment integration verifies successful payments and refunds. Checkout metadata can connect those records when a suitable visitor and session are available. Installing the browser script alone does not record Stripe revenue.

Customer Stripe integration and the Stripe subscription you pay for your 5H3LL plan are separate connections. Configure revenue tracking for each website in its payment settings.

Review revenue per visitor

Revenue per visitor is attributed revenue divided by observed visitors in the same filtered period and currency. For an illustrative £180 attributed to 300 visitors, the result is £0.60 per visitor. Keep the sample size next to the ratio and check whether one large purchase dominates it.

Calculate marketing ROI outside the attribution label

Keep ad spend, sponsorship fees, refunds and operating costs in your finance records. A simple revenue-based return calculation is (attributed revenue minus campaign cost) divided by campaign cost; that is not automatically net profit or a causal measure of incremental sales.

Use equivalent observation periods and allow for buying delay. Missing consent, hidden referrers and cross-device purchases leave gaps, which should remain visible rather than being assigned to a guessed source.

Start with one campaign

Choose a meaningful completed goal, tag the campaign URL and verify a payment through the supported provider setup. Inspect the campaign under the website dashboard, then use journeys to investigate what happened before purchase.

Does this support Stripe?

Yes. Each website can connect a restricted customer Stripe key and verified webhook. Follow the setup guide and keep credentials server-side.

Does it support Lemon Squeezy natively?

Not currently. A custom backend adapter could use the server-side payments API, but authentication, webhook verification, idempotency and attribution metadata would need implementation. There is no one-click Lemon Squeezy connector.

Can I see the exact cause of every sale?

No. Attribution assigns credit using observed data and matching rules. It is not a complete causal model or a guarantee that every payment can be matched.

Free plan available. Paid plans from £3. Refund policy.