Revenue-first analytics
From search result to paying user.
One dashboard.
See which pages and channels bring paying customers, and which the AI engines have never seen. So you know what to write, and where to spend.
Sign in with Google. Seven days of Pro, no card. Two screens work before you name a single event.
Traffic — every channel and campaign, ranked by what a visitor from there has been worth.
The whole path, on one dashboard.
Analytics tools start at the click. SEO tools stop at it. Rookdash runs the full length, from the page going live to the customer coming back.
- You publish a pagePagesEvery URL on the site, with what each one has earned.
- Google, Bing and AI crawl itIssues · AI & BotsWhether it was indexed, and which AI engines fetched it. Or never did.
- Someone searches, or sees an adKeywordsThe query or the campaign, and the page that answered it.
- They clickPagesImpressions, clicks and position, on the same row as the money.
- They arriveTrafficThe channel and campaign that brought them, and what each has been worth.
- They sign up and use itUsers · FeaturesWho they are, where they landed, and which parts of the product they reach.
- They payTraffic · PagesRevenue lands on the page and the channel that first brought them.
- They come backRetentionDaily, weekly and monthly actives. Cohorts by the week they signed up.
Then back to the top: the revenue says which page to write next.
Three things it tells you on day one.
/pricing ranks #3 and earned $4,800 last month. ChatGPT has never fetched it.
Cloudflare's edge logs see every request, including the ones your analytics script never runs for. The list that matters is the inverse: pages already earning money that no AI engine has seen.
Meta sent three times the visitors Google did. For a third of the money.
Revenue is credited to the payer's first touch, not the click that closed. So a campaign that brings volume without customers has nowhere to hide.
41 people signed up on a Tuesday. 23 came back that week.
Retention reads your product's own behaviour, so it needs no event names and no setup beyond the key. It is complete the day the key is saved.
Right now this is three tabs and a spreadsheet.
Search Console for rankings. PostHog for behaviour. An ad platform for spend, and a sheet that joins them by hand. Rookdash joins them on the URL, and shows both halves.
Before they arrive
From Search Console, Bing and Cloudflare
- PagesOne row per URL: rankings, index status, AI crawls, visitors, revenue.
- KeywordsEvery query, its page, its clicks, and the money behind it.
- IssuesWhere the sitemap, Google and the edge disagree about a page.
- AI & BotsWhich engines crawl what, and the earning pages they skip.
After they arrive
From PostHog
- TrafficChannels, campaigns, countries, pages — each with revenue per visitor.
- RetentionDaily, weekly, monthly actives. Cohorts by signup week. How the base moved.
- UsersEvery person, their goal tier, and their journey from query to payment.
- FeaturesWhich parts of the product people use, how much, and what they do there.
Three steps, and screens light up as you go.
The tracking already exists. Setup is telling Rookdash where to read it and which event means money.
- 1
Sign in with Google. Paste a PostHog key.
Retention and Features work now. Neither needs an event name.
- Retention
- Features
- Users
- 2
Name the event that means money.
Traffic works now. Every channel and campaign gets a revenue per visitor.
- Traffic
- 3
Add Search Console and Cloudflare.
The organic screens fill in overnight. Each connector works on its own.
- Pages
- Keywords
- Issues
- AI & Bots
Pricing
Every project starts on seven days of Pro, no card. Keep the organic half, or drop to Lite for the product side alone.
Lite
$29 per month
Product analytics, with the revenue attached.
- PostHog connector
- Traffic — revenue per visitor, by channel and campaign
- Retention — actives, and cohorts by signup week
- Users — every person, from how they found you to the payment
- One person's journey, from the search query on
- Features — which parts of the product people reach
No card required
Pro
$49 per month
Everything in Lite, plus the half that happens before they arrive.
- Search Console and Bing — Pages, Keywords, Issues
- Cloudflare edge logs — AI & Bots
- The earning pages no AI engine has fetched
- Rankings and revenue on one row, joined on the URL
No card required
Questions
Do I need to add a script to my site?
No. PostHog is already on it. Rookdash reads PostHog, Search Console and Cloudflare through their APIs, so there is nothing to install and nothing that can slow a page down.
What do I have to connect?
PostHog for behaviour and revenue. Search Console for rankings. Cloudflare for the edge logs that show AI crawlers. Bing is optional. Each one works on its own, and every screen shows what it can with whatever is connected.
How do you know an AI engine crawled a page?
From Cloudflare's edge logs, which see every request, including the ones your analytics script never runs for. That is also where the gap between edge traffic and PostHog traffic comes from.
Can my team see it?
Yes. Invite viewers from the Team screen. A viewer sees revenue as shares and indices rather than amounts, unless you switch that off for the project.
Where are my keys stored?
Encrypted at rest, with a master key that lives only on the server. Each key is verified against its provider before it is saved and is only ever decrypted server-side.
Find out where the next customer comes from.
Seven days of Pro, no card. Connect PostHog and two screens work today.
Rookdash