In this article
Stripe is open in one tab and your analytics in another, and you're trying to line up the days by eye. Did last Tuesday's traffic spike bring any sales? It's hard to tell when the two charts use different scales, different date ranges and maybe different timezones.
Here's what putting revenue and traffic on one chart can tell you, what it can't, and three practical ways to do it.
First, decide which question you're asking
Two different things get called "revenue and traffic on one dashboard".
An overlay puts revenue per day and visitors per day on the same time axis. It answers questions like these:
- Did revenue move when traffic moved?
- Is there a delay between a traffic spike and the sales that follow?
- Did launch week bring money, or only visitors?
Attribution splits revenue by traffic source or campaign. It answers how much came from the newsletter compared with search, or which campaign paid for itself.
An overlay only needs two daily series. Attribution needs each payment linked back to a visit, which means carrying an identifier from the landing page through to checkout. That's real extra work, and it's never perfectly accurate. A lot of frustration comes from expecting attribution from a setup that only does an overlay.
What an overlay is good for
An overlay doesn't say where the money came from. It still answers useful questions:
- Spotting a break. If traffic is steady and revenue drops to zero for two days, look at checkout, a pricing page change or a payment problem before you look at marketing.
- Judging spikes. A big traffic day with no change in revenue suggests the visitors were curious rather than ready to buy.
- Seeing lag. For some products people visit, leave and buy days later. An overlay over a few weeks can show that delay.
- Weekly patterns. If both lines dip every weekend, that's normal. If only revenue dips, it's worth a question.
Option 1: a spreadsheet
Good for a one-off look, with no new tools.
- Export daily visitors from your analytics tool as a CSV.
- Export payments from Stripe for the same period.
- Group the payments by day and sum the amounts.
- Join the two tables on the date.
- Chart visitors and revenue as two lines, with revenue on a second axis.
Five things trip people up:
- Timezones. If the two exports use different ones, days shift against each other.
- Gross or net. Pick amounts before or after fees and refunds, and stay consistent.
- Refunds. A refund on Friday for a Monday sale can make Friday look negative. Decide which day it belongs to.
- Subscriptions. Renewals arrive whatever your traffic does that day. If most of your revenue is recurring, chart only new purchases next to traffic.
- Currencies. If you charge in several, convert before summing.
The downside is that the sheet is out of date the moment you close it.
Option 2: build it yourself
If you want a live view and enjoy plumbing, pull both sources into one place.
- Pull payments from the Stripe API on a schedule and store daily totals.
- Pull daily visitors from your analytics tool's API or export, if it has one.
- Put both in a database, a notebook or a BI tool and chart them together.
The upside is control: you choose how refunds, fees and subscriptions are handled, and you can add attribution later. The cost is maintenance. API changes, failed jobs and timezone bugs are now yours to fix.
Option 3: an analytics tool with revenue
Some analytics tools connect to your payment provider and draw revenue on the same chart as traffic. Before you connect anything, ask:
- Is access read-only? An analytics tool shouldn't need to create charges or refunds.
- Which providers are supported? If you sell through more than one, check that all of them are covered and whether they're combined.
- Overlay or attribution? Read the docs, not the headline. If a tool claims revenue by source, find out how it links payments to visits.
- How are refunds and fees handled? This changes the numbers you see.
- What does it need on your site? Attribution often relies on identifiers that follow a visitor to checkout. That can affect whether you need a cookie banner.
If you need revenue by channel
Attribution is possible with most stacks. The basic pattern has four steps:
- Tag your links. Use consistent UTM parameters on campaigns, newsletters and social posts. A naming convention saves pain later.
- Capture the source on landing. Read the UTM tags or referrer when the visitor arrives.
- Carry it to checkout. Pass the source along when you create the checkout. With Stripe, a common approach is to attach it to the payment as metadata or a reference field.
- Report on that field. Group payments by the stored source, in your own pipeline or in a tool that supports it.
Expect gaps. Some visitors arrive with no referrer and show up as direct traffic. Some buy days later on another device. Different tools count differently, which is why the numbers rarely match. Treat attribution as a rough guide, not an exact ledger.
A short checklist
- Decide: overlay, attribution, or both.
- Use the same timezone for traffic and revenue.
- Pick gross or net and stick with it.
- Decide how refunds and recurring payments are shown.
- Read weeks, not single days, if sales volume is low.
- If you need attribution, tag links with UTMs and pass the source into checkout.
Putting the two numbers side by side won't explain everything. It does make the obvious questions easier to ask, and the broken days easier to spot.
Lomen is an overlay, not attribution. It connects read-only to Stripe, Shopify, Lemon Squeezy, Polar and Paystack, adds the revenue together and draws it on the same chart as visitors. It won't tell you how much came from search or a newsletter, so if revenue by source is what you need, it's the wrong tool for that job.