Web analytics

You know what your traffic costs. Now find out what it earned.

Sources, campaigns, geography, devices and page speed — with the click ID that brought each visitor and the revenue that followed, on one row. Ask in plain English and get the answer, not a chart to interpret.

  • One tag, any platform
  • Consent-gated
  • Replaces Plausible and Google Analytics

One subscription in place of the stack you're running today

MixpanelAmplitudeHotjarFullStoryLaunchDarklyOptimizelyChartMogulKlipfolioTriple WhaleGainsightVWOPlausible
Sound familiar?

Three tools agree you had a good month. None of them can prove it.

“Traffic is up. Is revenue?”

Your analytics counts visits and your ad platform counts clicks. Neither one can tell you which campaign paid for itself.

“Where did this signup come from?”

The campaign parameters were stripped somewhere between the ad and the form, so a paid conversion gets filed under “direct”.

“Which of these pages is costing us?”

Speed lives in one tool, bounce in another and revenue in a third, so a slow template never gets priced.

Flowgrid · one tagWhat every tool already tells youLive

Pageviews

Activated accounts

1 , 2 8 41,,943100

Sessions

Qualified signups

4 1 23,,828044

Bounce rate

Paid → activated

4 16..24%%

Avg. time on page

Revenue influenced

£ 1 8 22,:41040

Top page

Top source

P A/IBDL:OMGE/RSIENOO

Nothing new was installed.
The board just stopped hedging.

Every number on the right comes off the same events as the ones on the left. The difference is a definition, not a second tracker.

What you get

Attribution that survives contact with the real internet.

Attribution

Paid traffic that stays attributed.

Google and Meta click IDs are captured alongside UTMs, so the conversion is still traceable to the campaign after the parameters get stripped in a redirect or a privacy filter.

  • gclid and fbclid captured on every landing session
  • Campaign, source, medium and revenue on the same row
  • Works on the plain tag — nothing to configure per campaign
Revenue by sourceLast 28 days
SourceVisitorsRevenue
Paid searchgclid2,496$16,664
Organic searchGSC4,062$20,840
Referralutm4,683$10,712
Direct—4,476$19,736

Click IDs captured alongside UTMs — paid stays attributed after the parameters are stripped.

Search Console, joined in

The queries that convert, not the ones that rank.

Impressions, clicks and positions sit beside on-site behaviour, so a term that ranks first and converts nobody stops being a win you report on.

  • Search queries next to what those visitors then did
  • Page-level impressions against page-level revenue
  • One connection, no export or spreadsheet in between
Revenue by sourceLast 28 days
33,160+29%vs previous period
Organic
100%
Paid search
83%
Referral
56%
Direct
34%
Performance in context

A slow page, priced in revenue.

Core Web Vitals per page, next to the bounce and the conversion for that page. The engineering argument stops being about milliseconds and starts being about money.

  • LCP, CLS and INP per page and per device
  • Beside the conversion rate for the same page
  • Mobile and desktop split on every metric
Ask FlowgridLive

Which campaign actually produced revenue this month?

Answer
  • Organic96%
  • Paid search76%
  • Referral42%
  • Direct39%
Working shownFollow-ups keep contextNo SQL
What changes
One tag
Next, React, Shopify, Webflow, WordPress or plain HTML. Nothing to configure, no tracking plan to agree.
Every event
Device, page, referrer and campaign are attached automatically — attribution is not a project you schedule.
Click IDs
gclid and fbclid captured alongside UTMs, so paid traffic survives the parameters being stripped.

No warehouse, no export, no reconciliation step. The campaign that brought the visitor is on the same row as the revenue they produced.

The maths

One tag, not four dashboards.

Flowgrid
A typical marketing stack
Traffic, sources, geography
Included
Your web analytics tool
Which campaign produced revenue
Campaign and revenue on the same row
Two tools and a spreadsheet
Paid attribution after parameter stripping
Click IDs captured on landing
Filed under “direct”
Search Console queries
Joined to on-site behaviour
A separate tab
Page speed beside conversion
Same view, same page
A third tool
The sessions behind a number
Friction sessions, one click from the chart
A fourth subscription

Most teams arrive running a privacy analytics tool, their ad platform's own reporting and a heatmap subscription, with a spreadsheet holding the story together.

In your words

Ask it like you’d ask your agency.

No query language, no ticket, no waiting for the monthly report.

  • Which campaign actually produced revenue this month?
  • Why did organic traffic fall but conversions hold?
  • Which pages are slow enough to cost us signups?
  • Where in the world are the visitors who convert?
  • Which search queries are we ranking for but not winning clicks on?
Before you ask

The things everyone asks first.

Attribution should not be the expensive part.

Web analytics is included on every paid plan — alongside product analytics, replay, heatmaps, goals and experiments, on one bill.

  • Free to start, no credit card
  • Every surface included on every paid plan
  • Usage-based, so a quiet month costs less
See pricing