Read reports for a larger website
Larger websites open a report view that calculates totals in the database. You can compare dates, see sources and revenue, and inspect payment records without downloading every recorded visit.
Instructions reviewed
Choose your dates and attribution model
- Open your website dashboard
The larger-site view opens automatically when the available event snapshot exceeds 250,000 events, payment records exceed 10,000, or crawler rows exceed 25,000.
- Choose Dates and Compare
Use a recent period, month to date, year to date, or custom dates. This view uses UTC. Reports read the available records in the latest 365 days; an older comparison can have less history.
- Choose attribution
First-Touch, Last-Touch, Linear and Time decay use the recorded entry visits. Earlier recorded touches remain available for buyers. Unmatched payments stay in the overall revenue total, even when they cannot be credited to a source.
Filter the revenue chart
Use Paid ads or AI search above Follow the money, or choose a specific Channel and Source. These controls change the chart only. The summary cards, breakdown table and payment list still show the entire selected date range.
Sales appear above zero and refunds below zero. Net revenue subtracts refunds on their recorded dates. Focus or tap a chart date to inspect the exact amounts and visitor count. A person can appear under more than one source, so source visitor counts do not add up to unique visitors.
Read the breakdown and payment pages
Choose Sources, Channels, Landing pages or Campaigns. The table returns the leading 500 rows, ordered by revenue, and tells you the total number of matching rows. Use the table's page buttons to read 25 rows at a time. The row limit does not limit the report totals.
Select Load latest payments to read up to 50 payments and refunds. Select Next 50 payments to continue. Their totals are calculated independently of which payment page is visible. Older payment pages can change as new records or corrections arrive.
Know which reports still have limits
The monthly collection allowance and reporting capacity are separate. This release does not promise a response-time guarantee at every pricing tier or extend report history beyond 365 days. If a report cannot finish, it shows an error rather than partial totals.
| Report | Larger-site support |
|---|---|
| Overview, timeline, sources, channels, campaigns and landing pages | Complete database totals from available records. Breakdown lists return the top 500 rows. |
| Payments and refunds | Separate pages; REST, CLI and MCP return next_cursor when another payment page is available. |
| Journeys, maps, audience, goals, funnels and other detailed reports | Still use the complete event snapshot. Above the 250,000-event guard, those report requests fail explicitly. This larger-site dashboard does not show empty substitutes. |
Still need a hand?
Send a question without needing to sign in.