Connect
Stripe in a minute
- In your website's setup, choose
Stripe and follow the link to create a restricted key. The permissions are pre-filled: read access to Checkout Sessions, Charges, PaymentIntents, Invoices, Subscriptions, Products, Prices and Customers, plus webhook endpoints.
- Paste the key and leave "Instant updates" on. DataBull creates the webhook.
- Choose every payment in the account, or only some products.
Past payments import straight away. New ones arrive by webhook within seconds.
How each sale finds its visit
- Payment Links (
buy.stripe.com): the script addsclient_reference_idto every link on your site. Nothing to do. - Checkout Sessions: pass the visitor and session ids as metadata, two fields. Copy the code.
- Success page: when the buyer returns with
session_idin the address, the script links it as a backup.
Subscriptions, renewals and refunds
The first invoice is credited to the checkout's visitor and every renewal inherits it, so a source keeps earning credit for as long as the customer pays. Refunds come off the source they came from. The Revenue page groups customers by first source and adds up their lifetime value.
What you see
- Revenue, sales, average order and revenue per visitor, by referrer, campaign, page and country.
- A
Telegram message for every sale with its source, location and the buyer's path.
- Revenue in USD, excluding tax; other currencies are converted at the day's rate.
Also on
Polar,
Dodo Payments or
Creem? Each website connects its own provider. See
Polar analytics,
Dodo Payments analytics and
Creem analytics.
Ask your AI agent, too
Every DataBull install has a built-in MCP server. One command connects Claude Code, Cursor, Codex, Windsurf or VS Code, and your agent answers "which post made me money?" from your own data. The same numbers are in your terminal and behind read-only API keys.
npx databull@latest mcp