Polaris reads your GA4 and BigQuery data, then walks your site the way a customer does — screenshots, clicks, forms and all. You get one prioritized list of what's costing you money, with the amount attached.
No install for this part — just GA4 Viewer access.
What the page looks like
Apple Pay button renders below the fold on iOS Safari at 390px. Circled because it's where the numbers say people leave.
What the numbers say
Mobile checkout conversion is down 18% week over week — the dashboard alone doesn't say why.
Rough monthly figures are enough. This is its own one-step request — separate from the audit form below, no GA4 access needed here.
Your analytics tells you what happened. Your website shows you why. Usually two different people look at them, weeks apart — an analyst reading a dashboard, a designer looking at a page, neither one looking at the other's screen.
Conversion dropped 18% on mobile checkout last week. The dashboard is confident about the number and silent about the reason.
The Apple Pay button moved below the fold on a template update three weeks ago. Nobody connected the two events.
One pass, one output: the number, the page, and the line that connects them — plus what it's worth to fix.
Everything below runs on the same dataset. No syncing exports between an analytics tool, a heatmap tool, a survey tool and a testing tool that have never seen each other's data. Click a step.
STEP Where you are
Polaris reads GA4 and BigQuery and walks your top pages the way a visitor would. You get numbers and a screenshot of the exact spot they describe — not a dashboard you have to translate yourself.
ARTIFACT YOU SEE
Report slide: the metric, plus a screenshot with the problem circled.
The same underlying analysis, told five different ways depending on who's reading it. Switch audiences below — it's the same report, not five different products.
Written for someone who runs the business, not the analytics stack. No ARPU, no PDP, no jargon that needs a glossary.
P0
Checkout button hides below the fold on iPhone — costing roughly 4% of mobile sessions.
P1
Shipping cost only appears at the last step — a top exit-survey answer this month.
Three findings, each tied to a dollar or percentage figure — built for a five-minute read before a budget conversation.
≈4%
mobile sessions hitting the checkout issue
-18%
week-over-week mobile conversion
P0
priority — fixable this sprint
Device × channel × landing page × new/returning and more — cross-tabbed, not editorialized. You draw your own conclusions.
Campaign, ad group and creative performance as seen through GA4 — landing page fit, not bid strategy. Full ceiling of what this can and can't show on the Ads page.
Campaign "Spring-Retarget" sends 61% of clicks to a page with the same checkout issue flagged above.
Creative set B converts at 2.4x creative set A on the same landing page — worth a budget shift.
Every mode above, combined into one deck built for defending a CRO budget line to people who weren't in the room for the analysis.
Client identities are withheld, but the numbers on the "real audit" cards are quoted exactly as they appeared in the delivered report — not smoothed into a round, illustrative figure.
Same paid campaign, two landing pages: £2.19 vs. £0.03 revenue per session — a 73x gap routing ~77,000 sessions/month to the losing one.
The site's #1 and #2 searched terms have zero presence in navigation → the matching page converts at 27x the RPS of the category-browse path visitors get instead.
Revenue per user spans 30x across markets — the city carrying most sessions earns below the site average per user; ad budget still follows volume, not yield.
Annual-plan toggle defaults to monthly → estimated $40k/yr left on the table.
Exit-intent popup fires before the page has scrolled once → survey shows visitors find it "premature," not "annoying."
"AI wrote it" is a fair reason to be skeptical. Here's what stands between a raw model output and a report with your name on the send list.
One agent generates the analysis. A separate verification pass checks every claim against the source data before it ships.
Rate comparisons use a Wilson interval, not a raw percentage — so a 2-of-9 sample doesn't get reported like a 200-of-900 one.
A segment under the session threshold doesn't get a confident-sounding claim attached to it. Small samples get labeled small.
A person reads every report before it reaches you. Not a rubber stamp — an actual pass by someone with CRO background.
Findings are generated from a query against your actual data, not paraphrased from a general impression of "typical" sites.
Not a single generic prompt — a library of scenario-specific analysis paths refined against real reports, not a demo.
Not a mockup
Brand blurred, numbers untouched — 490 sessions, 2,925 clicks, from a single-hero-product DTC accessories brand.
Most sites run three vendors for this — one for A/B tests, one for surveys, one for heatmaps — because those are usually three separate companies with three separate tags. Polaris ships all of it from a single script tag, on the same data as everything else here.
Polaris asks for Viewer access to your own GA4 and BigQuery — nothing more. The connection runs on your data, in your account. Full detail on the Security page.
We request read access, never the ability to change your GA4 or BigQuery settings.
Your data produces your report. It doesn't get folded into any model training set.
One click in your own Google Account permissions ends the connection completely.
The first report needs no snippet on your site — only read access to data you already collect.
01
Add our service account to your GA4 property as a Viewer. Five minutes, done by you, revocable anytime.
02
Data pull, site walkthrough, analysis, generation, verification pass, human review — no self-serve black box.
03
Within a few business days, reviewed by a person — not "instantly," and we'd rather say that upfront.
The analysis is grounded in CRO methodology that predates the AI layer entirely — evidence tiers, hypothesis frameworks, funnel and usability checklists refined across real audits. The model applies that methodology to your data; it didn't invent it.
35
built analysis scenarios
149
reports generated to date
7
report modes per analysis
Artem
Strategy & client relations
Konstantin
Engineering — the pipeline, the code, the leads
Viktoria
Content — video, voice, the blog
When a GA4 metric crosses the threshold you set, or a page stops responding the way it should, Signals tells you exactly that — and stops there. That's a deliberate choice, not a missing feature: a monitoring system that always has an opinion is one you eventually stop trusting.
Below the session threshold, a segment gets labeled "not enough data yet" instead of a confident-sounding number. No claim ships without a query behind it.
Polaris reports what it finds. It doesn't auto-implement changes, push code, or edit your pages — every fix is a decision your team makes.
Today that's GA4, BigQuery and Google Ads via GA4. If a question needs a source we're not connected to, the honest answer is "we can't see that yet" — not a guess dressed up as an answer.
One free audit. No snippet required. Viewer access to your GA4, five minutes of your time.