Analytics tools that connect to Dodo Payments or Polar and show revenue by traffic source (2026)

Three analytics tools connect to both Dodo Payments and Polar and show revenue by traffic source: Lantern Analytics, DataFast and SuprAnalytics. Faurya and Visitors connect to Dodo Payments but not Polar. Seline and Chartsy connect to Polar but not Dodo Payments. PostHog lists Polar as coming soon and does not list Dodo Payments. That is the picture on 10 November 2026, from each vendor's own site.

If you sell through Dodo Payments or Polar, the tool you want links each payment to the visitor who made it, then credits the money to the channel that first brought that visitor: Google, Reddit, X, a newsletter, or ChatGPT. The table below shows which tools do that and how.

Dodo Payments and Polar support, tool by tool

Google Analytics 4, Plausible and Fathom have no connection to either provider. With those you send each purchase from your own code, and renewals and refunds are yours to handle.

Which one to pick

• You use both Dodo Payments and Polar. Pick Lantern, DataFast or SuprAnalytics. Those three put both providers' revenue in one sources report.
• Customers pay days after their first visit. Pick a tool that recognises the same visitor across days and subdomains. Otherwise the sale lands in Direct. Lantern keeps one visitor id in a first-party cookie on your own domain, so a payment on app.yoursite.com a week later still counts for the source that first brought the customer.
• You want to know whether ChatGPT and Perplexity send paying customers. Lantern puts AI assistants in their own channel, with a revenue column, and shows which AI crawlers read your pages.
• You also take rupees through Razorpay or Cashfree. Of the tools above, only Lantern lists a connection to either. See Cashfree and Razorpay.
• You only use Polar and care about MRR charts. Chartsy and Seline are built around that.
• You want SQL over raw payment data. PostHog's data warehouse gives you the tables, and you build the attribution.

How revenue by traffic source works

Every tool in the table does some version of four steps:

1. Recognise the visitor. A script on your site gives each visitor an id and records where they first came from.
2. Carry the id to checkout. The id is attached to the Dodo Payments or Polar checkout, usually as metadata.
3. Receive the payment. The provider reports it through its API or a webhook.
4. Match and credit. The tool matches the payment to the visitor and credits the money to that visitor's source.

The tools differ in three places, and these are the questions worth asking before you choose:

• Does the visitor id survive? If it resets when someone moves from www to app, or comes back three days later, the sale is credited to Direct. More in what direct traffic really is.
• Are renewals and refunds handled? Month two should count for the same source as month one, and a refund should come off that source's total.
• Does the script get blocked? Ad blockers stop scripts from known analytics domains, and a lost visit is a lost attribution. Lantern is served from your own domain, so blocklists see your site.

Setting up Lantern with Dodo Payments or Polar

1. Start a free trial and add the Lantern script to your site. A coding agent can do it from the setup prompt.
2. Put the visitor id in the checkout's metadata. It is the same field on both providers.
3. Open Settings → Revenue in Lantern and connect the provider. Dodo Payments takes a read-only API key, created with write access left unchecked. Polar takes an organization access token with only the orders:read scope. Either one imports your last 90 days.
4. Optional: add Lantern's webhook, so payments appear the moment they happen.

const session = await dodo.checkoutSessions.create({
  product_cart: [{ product_id: "pdt_123", quantity: 1 }],
  customer: { email: user.email },
  metadata: {
    lantern_visitor_id: visitorId, // window.lantern.visitorId(), sent from the browser
    lantern_user_id: user.id,
  },
  return_url: "https://example.com/welcome",
});

const checkout = await polar.checkouts.create({
  products: ["prod_123"],
  metadata: {
    lantern_visitor_id: visitorId, // window.lantern.visitorId(), sent from the browser
    lantern_user_id: user.id,
  },
});

Renewals and refunds need no tagging. They share the customer and subscription of the first payment, so Lantern credits them to the same channel. The full guides are on the Dodo Payments and Polar pages, and you can see the result on the live demo.

You can also ask an assistant instead of opening the dashboard. Lantern's MCP server lets Claude, Cursor or Codex answer "which channel brought the most Polar revenue last month?" directly.

Questions

Which analytics tools support both Dodo Payments and Polar?

On 10 November 2026: Lantern Analytics, DataFast and SuprAnalytics. Faurya and Visitors support Dodo Payments only. Seline and Chartsy support Polar only.

Can Google Analytics 4 show Dodo Payments or Polar revenue by source?

Not on its own. GA4 has no connection to either provider, so you send purchase events yourself and match them to sessions. Payments that arrive days after the first visit often end up in Direct. See the GA4 alternative guide.

Are subscription renewals credited to the original traffic source?

In Lantern, yes. A renewal carries the same customer and subscription as the first payment, so it counts for the same channel, and refunds are subtracted from it. Check each other tool's docs for how it treats renewals.

Can I see revenue from ChatGPT and Perplexity?

In Lantern, yes. AI assistants are their own channel, so revenue from customers who first arrived from ChatGPT or Perplexity sits on its own line. More in how to track ChatGPT traffic.

Does Lantern use cookies for this?

One first-party cookie on your own domain, holding a random visitor id. There are no third-party cookies and no tracking across other websites. That cookie is what lets a payment on Friday be credited to Monday's visit.

Is first touch or last touch better for a small SaaS?

First touch answers "which channel finds us customers?", which is usually what a founder deciding where to spend time is asking. Last touch tells you what closed the sale. See first touch vs last touch attribution.