Integrations
Revenue integrations for AnalyticFast
Choose the provider that collects your customers’ payments. A tracker records acquisition and visits; a signed provider webhook records money. Checkout metadata connects the two. These integrations attribute revenue for your website, separately from the provider that bills your AnalyticFast workspace.
Choose your payment provider
- Stripe setup — A successful Stripe payment tells you what sold. A tracked visit plus checkout metadata tells you which source brought the buyer. AnalyticFast joins those records without treating a checkout-button click as revenue.
- Paddle Billing setup — Paddle Billing can carry analytics IDs alongside a transaction. Connect its signed notifications and pass custom data at checkout to connect an acquisition source to the money actually collected.
- Lemon Squeezy setup — Lemon Squeezy returns checkout custom data with order and subscription events. Use that handoff to relate a sale to its visit, while keeping initial subscription invoices from inflating revenue.
- Polar setup — Connect Polar’s paid-order events to tracked visits with checkout metadata. Signed delivery establishes the payment; the optional visitor IDs establish the link back to acquisition.
- Whop setup — Whop payment events can connect a membership sale to its acquisition source when the checkout carries analytics IDs. A plain outbound link cannot establish that connection on its own.
- Dodo Payments setup — Dodo Payments supports checkout metadata and signed payment/refund delivery. Connect both so a sale can retain its source even after the buyer leaves your website to pay.
A reliable setup order
- Install one tracker and verify your public website.
- Connect the site’s revenue webhook and keep its signing secret private.
- Pass optional visitor/session IDs into the provider’s documented metadata fields before checkout.
- Test a payment, duplicate delivery, renewal if applicable, and refund on a separate test site.
Not every provider supports metadata in a hosted-link query string. Each guide names the supported handoff instead of promising that any Buy link is automatically attributable. For transactions you already verify in your backend, see server integration recipes and all provider contracts.
What to reconcile
Compare the same currency, dates and gross/net definition. Refunds reduce revenue; attribution can remain unknown when browser context is missing. The dashboard does not replace your provider’s payout or tax reports. Learn how revenue attribution works before interpreting a source total.
Add your website to AnalyticFast, then open Settings → Revenue to copy its webhook URL.
Questions, answered.
Will connecting a webhook attribute every historical payment?
No. Saving a webhook configures future deliveries. Past payments need available historical visit context and a separately supported replay or import process. Missing source context is not something a webhook can reconstruct.
Does the test button send a real payment?
No. It is a local parser preview: it contacts no provider, verifies no signed delivery, and records no revenue. Use a separate AnalyticFast test site and your provider sandbox to check payment, renewal, retry and refund delivery.
Do I need to expose payment credentials in my website?
No. The Site ID is public. Webhook signing secrets belong in the Revenue settings, and payment API keys belong on your server. Only optional visitor and session IDs travel from the browser to your checkout code.