Task: To understand if this cookieless, EU-hosted analytics solution can meet my website's tracking needs and simplify data collection without a cookie banner.
Personas: GDPR-focused Small Business Owner · Skeptical Marketing Manager · Time-pressed Web Developer · Content Creator Seeking Engagement Insights
Models: GLM-5.3-Flash + Claude-Haiku (a finding confirmed by both counts more strongly)
Method: synthetic personas read the page in a real browser and thought aloud; an attention model predicted the first glance.
Field 1 — First glance
Where the eye lands
red = high predicted attention***
13% of the predicted first glance lands on an action · 87% on text/decoration. This page must trigger an action — so the share is worth tracking over time.
Does the eye land on the action — or on the decoration? Ranked by predicted attention:***
Add to your site free5%
See how it works1%
Try free1%
Web-Tracking.eu1%
Documentation1%
Pricing1%
Coverage
The four kinds of friction
Works = the personas praised the field · problem = friction · nothing noted = neither praise nor friction.
Safety
dare I?
2
problems
Meaning
do I get why?
2
problems
Capability
can I manage it?
1
problem
Effort
can I be bothered?
7
works
Plus 1 defect(s) — real bugs (dead button / broken link) outside the four fields.
Recommendations
Improvement opportunities
Most important first. “Trade-off” = the new friction the fix itself may create.
AddSafety
1. Publish concrete plan prices and add-on costs on the comparison
Behaviour it should unlock: Compare plans and start signup with a known amount and a clear add-on bill. Leaving prices hidden costs the owner the two personas who already wanted to buy and left rather than guess what they would pay.
Finding: no prices shown despite pricing claims. Field is correctly tryghed (cost/commitment uncertainty), not missing education: they abandon comparison because they will not choose a plan they cannot price. Put numbers next to every pricing claim so comparison can finish.
Trade-off — new friction the fix itself may create: Public prices need upkeep and can cause sticker-shock drop-off or competitor matching.
Addresses: No prices shown despite pricing claims
ChangeDefect
2. Point See how it works at a live page that explains tracking mechanics
Behaviour it should unlock: Open how the product actually works from the homepage and keep exploring to judge fit. A dead or purely promotional path ends the visit; the owner loses that user before any trial.
Findings: the See how it works link is dead, and the CTA shows marketing, not mechanics. The dead link is a true defekt (broken control), not kan — do not add hints around a 404. The content failure is mening: they never learn cookieless collection, EU hosting, or why no cookie banner, so they cannot judge fit. Same CTA, working destination, mechanics instead of slogans.
Trade-off — new friction the fix itself may create: A real mechanics page must be maintained; if it is long, it becomes new besvaer.
Addresses: See how it works link is dead, How-it-works CTA shows marketing, not mechanics
ChangeDefect
3. Send Get started to account creation, not the homepage
Behaviour it should unlock: Create an account and enter the tool from Get started in one click. The loop means users never start; the owner loses signups those visitors were ready to complete.
Finding: Get started loops back to the homepage. Labeled kan, but the mechanism is defekt: the control does not navigate. Extra copy or help will not work; retarget the button to signup or onboarding.
Trade-off — new friction the fix itself may create: A working signup CTA can increase incomplete or bot accounts unless a light gate exists.
Addresses: Get started loops back to the homepage
AddSafety
4. Spell out what consumes the AI Analytics quota
Behaviour it should unlock: Start or buy without fearing a surprise quota hit. Unclear limits stall purchase; the owner loses buyers who wanted AI insights but would not risk an unknown cap.
Finding: AI Analytics quota is unexplained. Labeled mening, but the mechanism is tryghed: they hesitate because they cannot tell whether the insights they want count against the quota (overage/commitment risk), not because AI analytics lacks meaning. State what burns quota, what does not, and what happens at the limit.
Trade-off — new friction the fix itself may create: Quota rules add copy to scan and may expose tight limits, causing some to defer.
Addresses: AI Analytics quota is unexplained
Can be dispensed with
Elements the personas' reactions show do not carry their weight. The recommendation is to remove them.
Promotional marketing copy on the How-it-works path — Personas needed product mechanics to judge fit; nobody used or missed the slogans, so remove them rather than polish them.
Field 2–4 — Think-aloud
Where recipients drop off
SafetyStart here
No prices shown despite pricing claims
2/4 personas · severity 2.5/5 · 1 page(s)
Users cannot tell what they would pay or what is an add-on, so they abandon plan comparison and leave without signing up.
Skeptical Marketing Manager3/5GLM-5.3-Flash
„'Simple pricing. No surprises' headline, but the tiers show only event limits — no actual monthly prices anywhere visible, so I can't evaluate the real cost"
„'Optimise is an add-on on top of the analytics' — as a novice I can't tell if the engagement features I want are included or cost extra, and no price is visible here."
/ · step 5
Divergence — only one persona
Defect See how it works link is dead — only Skeptical Marketing Manager (4/5): “'See how it works' [2] link does not navigate — clicked multiple times with no page change. Either dead link or not a real clickable element.”
Meaning How-it-works CTA shows marketing, not mechanics — only Time-pressed Web Developer (2/5): “Clicked 'See how it works' but landed on pain-point marketing copy instead of actual mechanics”
Meaning AI Analytics quota is unexplained — only Content Creator Seeking Engagement Insights (2/5): “'AI Analytics (10/month)' is cryptic — I can't tell what counts as one AI Analytics use or whether the 'Why do they leave?' insights come out of that quota”
Capability Get started loops back to the homepage — only Content Creator Seeking Engagement Insights (2/5): “Clicking 'Get started' landed me back at the top of the homepage instead of a signup or the tool itself — felt like I went in a circle”
Expert lens — methodical review
Expert friction review
Methodical expert review of the page text and the personas' findings — not a persona simulation. Findings without persona confirmation are marked as hypotheses.
Workflows & repeated useEffortConfirmed by persona findings: Get started loops back to the homepage, See how it works link is dead
Primary CTAs waste a click every visit
Anyone who comes to evaluate or buy hits Get started or See how it works and does not advance. That failed click repeats every session and never reaches install, a dashboard, or a second use. Repeated dead-end clicks cost more than a weak onboarding.
Behaviour it blocks: Blocks the evaluate-then-sign-up loop on every session; the owner pays in repeat bounce instead of activation.
Decision points (RACE)SafetyConfirmed by persona findings: No prices shown despite pricing claims
Leaving beats plan choice when price is hidden
The page claims pricing but shows no amounts or add-on costs. Under purchase pressure the cheap move is to close the tab, not guess spend. The desired action (pick a plan) is not the cheapest action.
Behaviour it blocks: Blocks plan comparison and paid signup; the owner loses buyers who already had intent.
Decision points (RACE)MeaningConfirmed by persona findings: How-it-works CTA shows marketing, not mechanics, See how it works link is dead
How-it-works loses to closing the tab
The control that should explain cookieless collection delivers marketing or nothing. Users cannot judge fit against a cookie-banner stack, so bounce wins. The wanted action is more expensive than leaving.
Behaviour it blocks: Blocks the does-this-replace-my-tracker decision; the owner loses the evaluators this page is for.
System feedback loopsMeaningConfirmed by persona findings: AI Analytics quota is unexplained
AI Analytics quota fails the so-what test
A quota is shown with no rule for what consumes it and no benchmark. If the user does nothing, the number still does not imply a next step. The figure is meaning-friction, not guidance.
Behaviour it blocks: Blocks trial and purchase of AI insights; the owner loses upgrades that stall on unclear risk.
What's missingCapabilityConfirmed by persona findings: Get started loops back to the homepage
No working entry to signup or the product
Users expect Get started to open an account or snippet. That destination does not function, and no other start-here path is available. The conversion flow has no terminal action.
Behaviour it blocks: Blocks completing signup; ready buyers cannot create an account.
What's missingMeaningConfirmed by persona findings: How-it-works CTA shows marketing, not mechanics
No proof of cookieless, no-banner tracking
The job is to confirm EU-hosted cookieless analytics can drop a cookie banner. There is no mechanic, event list, or cue that collection works without a consent UI. Fit cannot be verified.
Behaviour it blocks: Blocks the core fit check; the owner loses sites shopping specifically to remove banners.
Implementation frictionDefectConfirmed by persona findings: Get started loops back to the homepage
Get started is a homepage loop
The main conversion control returns users to the same page. Nothing was submitted, so there is no undo and no recovery into a real signup. A self-loop is a dead end, not a start.
Behaviour it blocks: Blocks account creation at the last click; CTA intent is discarded.
Implementation frictionDefectConfirmed by persona findings: See how it works link is dead
See how it works is a dead end
The explanation link does not open. A click that promises a path and fails is more expensive than scrolling. Exploration stops on the homepage.
Behaviour it blocks: Blocks product understanding; visitors leave instead of continuing.
Remove before you add — verdict per element
The expert's mandatory verdict on every significant element: does it carry its weight? "Remove" means remove — not improve.
Element
Verdict
Why
Trade-off
Get started
Keep
It is the only named conversion control; removing it would hide the action this flow exists to complete.
—
See how it works
Remove
A dead or marketing-only link spends a click and never explains the product, so it does not earn its place.
Evaluators lose a labeled education path; do not refill the slot with campaign copy.
pricing claims
Cut down
Plan talk without amounts or add-ons burns trust and does not help a buy decision.
Sender loses vague we-have-plans social proof; that is cheaper than the current abandon.
AI Analytics quota
Cut down
A cap with no counting rule or benchmark adds hesitation without changing the next step.
Softens quota as an upgrade lever for the sender.
Strengths
What worked
works · MeaningConfirmed by both models
Headline instantly matches core needs
4/4 personas
The homepage headline and value proposition immediately signal cookieless, EU-hosted analytics with no banner and no credit card, so the product feels made for the visitor.
GDPR-focused Small Business OwnerGLM-5.3-Flash
„Headline and subtext immediately confirm the three things I care about: no cookie banner, EU data residency, no credit card to try it"
GDPR-focused Small Business OwnerClaude-Haiku
„Headline immediately signals the solution matches my need: cookieless, no banner, EU-based. Clear value proposition."
4 more quotes
GDPR-focused Small Business OwnerClaude-Haiku
„Headline and problem statements directly address my concerns: GDPR risk with Google Analytics, data leaving Europe, consent banner filtering. Feels relevant and trustworthy."
GDPR-focused Small Business OwnerClaude-Haiku
„Clear value proposition addressing all my pain points: GDPR compliance, no cookie banner friction, EU hosting, transparent pricing with free tier, and emphasis on simplicity ('takes 3 minutes'). Builds confidence."
Skeptical Marketing ManagerClaude-Haiku
„Headline directly addresses my core problem: GA data gaps due to consent banners. Value prop is clear and specific to EU context."
Time-pressed Web DeveloperGLM-5.3-Flash
„The headline instantly tells me the core value — no cookie banner — and 'Built in Denmark. Hosted in Germany' pre-answers my EU-compliance question in one line."
works · MeaningConfirmed by both models
Pain points mirror users' real problems
4/4 personas
Named objections around consent-banner data loss, GDPR/US-transfer risk, and GA complexity make the product feel personally relevant rather than generic.
GDPR-focused Small Business OwnerGLM-5.3-Flash
„Naming the US-server GDPR risk and the consent-banner data loss shows they understand my exact legal and data-accuracy problem"
Skeptical Marketing ManagerGLM-5.3-Flash
„The pain points mirror my exact situation — consent banner data gaps and the US data transfer risk — so the product immediately feels relevant rather than generic marketing."
4 more quotes
Skeptical Marketing ManagerClaude-Haiku
„The three pain points directly mirror my concerns as a skeptical marketing manager — consent filtering, GDPR risk, and GA complexity. Feels like they understand my actual problems, not just selling a generic alternative."
Time-pressed Web DeveloperGLM-5.3-Flash
„The pain points are exactly my clients' objections — shows they understand the developer/agency use case"
Time-pressed Web DeveloperClaude-Haiku
„Clear problem statement (GDPR risks, data leaving EU, complexity) directly addresses my compliance concerns as a developer"
„The pain points speak my language — 'you just want to know how many visitors you have' nails exactly why GA overwhelms me; feels like they actually get a novice content creator"
works · EffortConfirmed by both models
Risk-free setup in minutes
4/4 personas
No password, no credit card, a free plan, and a one-line script that takes a few minutes removes every excuse not to try it.
GDPR-focused Small Business OwnerGLM-5.3-Flash
„'No password, no credit card' and 'Set up in 3 minutes' — removes every excuse and makes trying it feel risk-free"
GDPR-focused Small Business OwnerClaude-Haiku
„The 3-minute setup (no password, no credit card, one script line) directly removes friction for my concern about implementation complexity."
4 more quotes
GDPR-focused Small Business OwnerClaude-Haiku/auth/login
„Clear, friction-free signup: no credit card required, free plan, Google option available, pre-filled test email ready to go"
Skeptical Marketing ManagerGLM-5.3-Flash
„The 3-minute setup with no password, no credit card, and a single script line removes the usual trial friction — and page change tracking with 14-day before/after speaks directly to a real GA workflow pain."
Time-pressed Web DeveloperGLM-5.3-Flash/auth/login
„'Free plan. No credit card. Takes 60 seconds.' — instantly removes signup risk and effort concerns"
Time-pressed Web DeveloperClaude-Haiku
„Setup process is straightforward and minimal: email-only signup, no password/card required, one-line script paste. Matches my need for easy integration."
works · SafetyConfirmed by both models
Concrete EU and cookieless compliance claims
3/4 personas
Specific statements about no cookies, Germany hosting, Schrems II, and data never leaving the EU confirm the legal compliance users came to verify.
GDPR-focused Small Business OwnerGLM-5.3-Flash
„'No cookies needed — no consent banner required' and '100% EU hosted in Germany, no Schrems II issues' directly confirm the legal compliance I came to verify, and 'one script tag, ~3 minutes' confirms it's easy to implement"
GDPR-focused Small Business OwnerClaude-Haiku
„Clear, direct answers to my main concerns: GDPR compliance (no cookies, EU-hosted, Schrems II compliant), simple implementation (one script tag), and optional GA4 forwarding gives me control."
3 more quotes
Skeptical Marketing ManagerGLM-5.3-Flash
„They openly disclose that optional GA4 forwarding sends data to Google (US) while their own data stays in the EU — honest, concrete hosting details (Germany, Schrems II)."
Time-pressed Web DeveloperGLM-5.3-Flash
„'No cookies needed — no consent banner required' concretely confirms the cookieless promise, and 'Add to your site — takes 3 minutes' signals a lightweight integration"
Time-pressed Web DeveloperGLM-5.3-Flash
„'Your data never leaves the EU' plus built in Denmark / hosted in Germany — konkrete hosting-fakta, som er det præcise compliance-svar, jeg kan videregive til min kunde"
works · Safety
Honest competitor comparisons
3/4 personas
Tables and copy that admit weaknesses and even recommend rivals for some use cases build credibility with skeptical buyers.
Skeptical Marketing ManagerGLM-5.3-Flash/pricing
„'Considering another tool?' section promising an honest comparison including 'where they beat us' — admitting weaknesses is a strong credibility signal for a skeptical buyer like me"
Skeptical Marketing ManagerGLM-5.3-Flash/compare
„The table openly admits weaknesses ('including where we lose') and marks competitors' partial capabilities honestly rather than trashing everything — that builds credibility with me as a skeptical buyer"
3 more quotes
Skeptical Marketing ManagerGLM-5.3-Flash/compare
„The 'Honest take' section explicitly recommends competitors (including GA4) for use cases where they fit better — that directly addresses my wariness of over-hyped solutions and builds real trust. Plus the €5/mo entry price finally gives me a concrete cost anchor."
Time-pressed Web DeveloperGLM-5.3-Flash/compare
„'Honest take: when to pick what'-afsnittet angiver åbent, hvornår konkurrenterne er det bedre valg — det gør sammenligningen troværdig i stedet for at virke som markedsføring"
„'Simple pricing. No surprises' with a free tier listing 'All core features' directly answers my worry that the engagement features might be a paid add-on"
works · CapabilityConfirmed by both models
Obvious next-step paths
2/4 personas
A clearly labelled path to how it works and a direct signup flow with no extra steps make it obvious how to proceed.
GDPR-focused Small Business OwnerClaude-Haiku/auth/login
„Clear, direct signup flow matching my goal — no unnecessary steps, free plan confirmed, no credit card required"
„'See how it works' is right there in the hero — a clearly labelled path to exactly the explanation I came for, no hunting required"
works · Safety
FAQ kills billing and legal anxiety
2/4 personas
Specific answers on ePrivacy, hard event-limit stops with no overages, prorating, and a DPA make committing feel safe and predictable.
Skeptical Marketing ManagerGLM-5.3-Flash/pricing
„The FAQ answers my exact objection with specifics: cookieless justified via ePrivacy Directive Article 5(3), and hitting the event limit just pauses recording with no overage charges — credible, not marketing fluff"
Skeptical Marketing ManagerGLM-5.3-Flash/pricing
„Event limit FAQ promises a hard stop with no overage charges and keeps dashboard/historical data accessible — predictable billing with no gotchas"
„The FAQ directly answers practical worries — hitting the event limit just pauses recording with no overage charges, and I can switch plans anytime with automatic prorating. That makes choosing a plan feel low-risk."
„The FAQ kills my billing anxiety — 'no overage charges', instant plan switching, and EU-only data storage with a DPA on request all make it feel safe to commit"
works · Effort
Step-by-step migration guides
2/4 personas
Per-competitor switching guides, including Google Analytics, directly address the effort of leaving an existing tool.
Skeptical Marketing ManagerGLM-5.3-Flash/compare
„Per-tool step-by-step migration guides, including one specifically for Google Analytics — directly addresses my switching-effort concern instead of leaving me to figure it out alone"
Time-pressed Web DeveloperGLM-5.3-Flash/compare
„Step-by-step migration guides for each competitor directly address the switching/maintenance concern"
Isolated praise
Meaning Developer-grade performance facts — only Time-pressed Web Developer: “Concrete numbers: ~4.5 KB gzipped, async, no Core Web Vitals impact, one line of code — exactly the developer facts I came for”
Meaning Engagement insights explain why visitors leave — only Content Creator Seeking Engagement Insights: “The promise 'find out why they leave' speaks directly to my exact problem as a content creator — feels immediately relevant”
Safety Works alongside Google Analytics — only Skeptical Marketing Manager: “'Works alongside Google Analytics if you want' — I can trial this in parallel without touching my existing GA setup, which makes trying it feel low-risk”
Meaning Features described with concrete specifics — only Skeptical Marketing Manager: “Clear feature list addressing my main concerns: no consent banner friction, EU hosting (Schrems II compliant), simple one-script implementation, and concrete features like visitor drop-off prediction and SEO optimization”
Raw data
Full transcript
Everything the personas wrote, turn by turn — the summaries above are clustered out of exactly these words. Open a persona to read all of it.
GDPR-focused Small Business Owner · GLM-5.3-Flash · 5 steps · done
Step 1/Meaning
Read: Landing page for a cookieless analytics tool. Headline says tracking without cookie banner, EU-hosted (built in Denmark, hosted in Germany), no credit card needed.
Thought aloud: „Okay, this headline is speaking directly to me — 'Tracking without the cookie banner' is exactly my problem. Cookieless analytics for European websites, data never leaves the EU... that's my two biggest worries addressed right up front. Built in Denmark, hosted in Germany — good, that sounds legit for GDPR. 'See the legal basis' is the link I'd want to check, because every vendor claims compliance and I need proof. But first let me scroll down to get the full picture — I especially want to see pricing for a small site before I click anything."
Worked: Headline and subtext immediately confirm the three things I care about: no cookie banner, EU data residency, no credit card to try it
Action: scroll
Step 2/Meaning
Read: A section calling out Google Analytics problems: consent banners lose visitors, data goes to US servers (GDPR risk), and GA is too complex. Plus a claim they simulate why visitors leave and suggest fixes. Three 'Get started' links and a 'Compare all features' link further down.
Thought aloud: „This is hitting my exact worries — the US server thing is the GDPR risk I keep reading about. Good sign they know the legal angle. Now I need the practical stuff: is it EU-hosted, what does it cost for a small shop? Those three 'Get started' links look like a pricing section right below."
Worked: Naming the US-server GDPR risk and the consent-banner data loss shows they understand my exact legal and data-accuracy problem
Action: scroll
Step 3/Safety
Read: Feature list: no cookies/no consent banner needed, 100% EU hosted in Germany, one script tag (~4.5 KB, async), team access, trend comparison, plus an AI add-on called Optimise. There are 'Get started' links and a 'Compare all features' link further down — likely pricing tiers below.
Thought aloud: „Okay, this answers my three big questions right here: no cookies so no banner, data stays in Germany, and one line of code — that's the simple legal solution I wanted. They're even honest that optional GA4 forwarding goes to the US, which actually makes me trust them more. Now I just need the price for a small site. Those three 'Get started' links look like plan tiers — scrolling down to see them."
Worked: 'No cookies needed — no consent banner required' and '100% EU hosted in Germany, no Schrems II issues' directly confirm the legal compliance I came to verify, and 'one script tag, ~3 minutes' confirms it's easy to implement
Action: scroll
Step 4/Effort
Read: Setup steps: email only, no password or credit card, paste one line — plus WordPress plugin, page-change tracking, engagement scoring, AI integration. Three 'Get started' buttons below, probably plans, but I still haven't seen any actual prices.
Thought aloud: „The 3-minute setup with no credit card is exactly what I want to hear. But I still don't know what this costs for a small site — those 'Get started' links hint at pricing tiers just below. That's my last open question. Scrolling down to find the numbers."
Worked: 'No password, no credit card' and 'Set up in 3 minutes' — removes every excuse and makes trying it feel risk-free
Action: scroll
Step 5/Meaning
Read: Pricing table: Free 10k events/1 site, Starter 100k/5 sites, Growth 500k/20 sites. No prices shown on the visible tiers, but 'Start free' is clear. Closing CTA: 'Add to your site — takes 3 minutes'.
Thought aloud: „There's my pricing answer for a small site: free tier covers 10,000 events and 1 website — that's plenty for my shop. I don't see euro amounts, but honestly 'free' is the number I care about. I've now confirmed everything: no cookie banner, German hosting, one line of code, free for small sites. I'm done here."
Worked: Free tier with 10,000 events/month and 1 website directly answers my 'what does a small site cost' question — the answer is zero.
Action: done
GDPR-focused Small Business Owner · Claude-Haiku · 9 steps · done
Step 1/Meaning
Read: Page headline: 'Tracking without the cookie banner.' Subheading explains cookieless analytics for EU websites, data stays in EU, no cookie banner needed, works with Google Analytics. Built in Denmark, hosted in Germany. Free to add, no credit card required.
Thought aloud: „Okay, this looks like exactly what I need — GDPR-compliant analytics without a cookie banner. The headline directly addresses my pain point. The key claims are right there: EU-hosted, no cookie banner, legal. But I need to verify this is actually compliant and see the pricing. Let me first understand what's on this page by scrolling down to see all options, then I'll either check the legal basis or jump to pricing/implementation details."
Worked: Headline immediately signals the solution matches my need: cookieless, no banner, EU-based. Clear value proposition.
Action: scroll
Step 2/Meaning
Read: Page explains the core problem: consent banners filter data, GA sends data to US (GDPR risk), and GA is too complex. They claim to offer simulation and improvement suggestions. Multiple 'Get started' buttons below. I'm 22% down the page.
Thought aloud: „Good — this is hitting my pain points directly. GDPR risk, incomplete data, complexity. But I need to verify: is it actually EU-hosted? Is it truly GDPR-compliant? And I need to see pricing. The 'See the legal basis' link might confirm compliance, but I should first scroll down to see the full offering and pricing before diving into legal docs. Let me scroll to see what's below."
Worked: Headline and problem statements directly address my concerns: GDPR risk with Google Analytics, data leaving Europe, consent banner filtering. Feels relevant and trustworthy.
Action: scroll
Step 3/Safety
Read: Features overview: no cookies, EU-hosted (Germany), one script tag, team access, trend comparison, AI insights, GA4 forwarding optional. Multiple 'Get started' buttons visible. I'm 43% down the page with more content below.
Thought aloud: „Good — this is confirming the key points I need: no cookie banner (✓), EU-hosted in Germany (✓), simple implementation (one script tag). But I still haven't seen pricing, which is critical for a small business. Let me scroll down to see the rest of the page and find pricing info before I commit to 'Get started'."
Worked: Clear, direct answers to my main concerns: GDPR compliance (no cookies, EU-hosted, Schrems II compliant), simple implementation (one script tag), and optional GA4 forwarding gives me control.
Action: scroll
Step 4/Effort
Read: I'm seeing the setup process (3 minutes: create account, add site, paste script) and several 'Get started' buttons. There's more content below. I need to see pricing and verify EU hosting before committing.
Thought aloud: „I've confirmed no cookie banner and one-line implementation, which is great. But I haven't seen pricing yet — that's critical for a small business. And I want to double-check the EU hosting claim before I start. Let me scroll down to see what's below, especially pricing and any legal/hosting details."
Worked: The 3-minute setup (no password, no credit card, one script line) directly removes friction for my concern about implementation complexity.
Action: scroll
Step 5/Safety
Read: Pricing section visible: Free tier (10k events, 1 website), Starter (100k events, 5 websites), Growth (500k events, 20 websites). All include core features. There's more content below. I can see 'Get started' buttons for each tier and a link to compare features.
Thought aloud: „Perfect — I found the pricing. Free tier exists, which is good for testing. Starter at 100k events for 5 websites looks reasonable for a small e-commerce site. But I still need to confirm: is this actually EU-hosted, and can I really implement it without a cookie banner? I saw those claims earlier but need to verify before committing. Let me scroll down to see if there's more detail about hosting or implementation, or if I should click 'See the legal basis' to confirm GDPR compliance."
Worked: Pricing is transparent and simple — free tier available, clear tier progression, no hidden costs mentioned
Action: scroll
Step 6/Safety
Read: Bottom of the landing page showing the main value prop: no cookie banner, real numbers, can add alongside Google Analytics. Free tier available. Multiple 'Get started' buttons and a final CTA 'Add to your site — takes 3 minutes'. I'm at 100% scroll position.
Thought aloud: „I've confirmed the key points: GDPR-compliant, EU-hosted (Germany), no cookie banner, simple one-line implementation, and pricing (free tier + Starter at 5€/month for 100k events). This checks all my boxes. Now I need to actually verify the implementation is as simple as they claim and see what the onboarding looks like. The 'Add to your site — takes 3 minutes' button is the most direct path to test the actual setup process."
Worked: Clear value proposition addressing all my pain points: GDPR compliance, no cookie banner friction, EU hosting, transparent pricing with free tier, and emphasis on simplicity ('takes 3 minutes'). Builds confidence.
Action: click 7
Step 7/auth/loginCapability
Read: Login page asking for email to get started. Options: email signup, Google signin, or back to home. Free plan, no credit card needed.
Thought aloud: „Good — I'm at the signup flow. I've already confirmed GDPR compliance, EU hosting, no cookie banner, and pricing. Now I need to actually verify I can set this up without friction. The email field is ready. I'll enter my email to proceed and see how simple the implementation actually is."
Worked: Clear, direct signup flow matching my goal — no unnecessary steps, free plan confirmed, no credit card required
Action: fill 1 test@example.com
Step 8/auth/loginEffort
Read: Signup page asking for email. I can enter my email and continue, or use Google. No credit card required, free plan, 60 seconds setup.
Thought aloud: „I'm at the signup flow. I've already verified everything I need: GDPR-compliant, EU-hosted in Germany, no cookie banner, one-line implementation, and reasonable pricing. I need to complete the signup to actually see the implementation and confirm it works. The email field is pre-filled with test@example.com — I'll use that and continue."
Worked: Clear, friction-free signup: no credit card required, free plan, Google option available, pre-filled test email ready to go
Action: click 3
Step 9/auth/check-email
Read: I'm on a 'Check your email' page. It says a login link was sent to test@example.com and expires in 15 minutes. There's a link to try a different email.
Thought aloud: „I'm stuck. I can't actually receive or click an email verification link — I don't have a real inbox. I've already confirmed everything I needed: GDPR-compliant, EU-hosted in Germany, no cookie banner, one-line implementation, and pricing exists. The signup flow requires email verification, which I can't complete. I should exit here — I've accomplished my core task of verifying the solution meets my requirements."
Read: Landing page for a cookieless analytics tool for European websites. Headline promises tracking without a cookie banner, shows visitors GA misses, explains why visitors leave, EU-hosted data, built in Denmark/hosted in Germany, free to start, works alongside Google Analytics.
Thought aloud: „Okay, the headline hits my exact sore spot — the consent banner is why my GA numbers have holes in them. So the promise is immediately relevant. My eye went to 'Add to your site free' second, but I've been burned by 'free' tools before, so I'm not clicking anything yet. What I want to know: how does cookieless tracking actually work technically, does it really match GA's reporting, and what's behind 'why they leave' and the SEO stuff. I also notice 'Works alongside Google Analytics' — that matters to me, I could run it in parallel instead of ripping out GA on day one. And 'See the legal basis' is the kind of claim I'd want to verify later, because 'your data never leaves the EU' is exactly the kind of line every vendor slaps on their homepage. First, methodically: I'll read the whole page top to bottom before I click anywhere."
Worked: 'Works alongside Google Analytics if you want' — I can trial this in parallel without touching my existing GA setup, which makes trying it feel low-risk
Action: scroll
Step 2/Meaning
Read: Four pain-point blocks: consent banners filtering GA data, data leaving Europe/GDPR risk, GA being too complex, and a promise to simulate why visitors leave and suggest improvements.
Thought aloud: „This is speaking my language. Incomplete data from consent banners — that's literally my weekly complaint. The US server transfer point is the GDPR risk my legal team keeps flagging. And 'simulate why they leave a page, suggest concrete improvements, then measure whether it worked' — that's the feature I came here to scrutinize. Bold claim; GA can't do that. But I'm wary of hype, so I want the technical detail on how cookieless tracking actually works before I trust any of this. There's more content below — pricing tiers and a feature comparison, judging by the links. I'll read through it all before deciding anything."
Worked: The pain points mirror my exact situation — consent banner data gaps and the US data transfer risk — so the product immediately feels relevant rather than generic marketing.
Action: scroll
Step 3/Safety
Read: Feature grid continues: clean dashboard, no cookies, EU hosting in Germany, one 4.5KB script tag, team roles, trend comparison. Then sections on AI-powered insights and importing from Google Analytics — those are cut off at the bottom.
Thought aloud: „Good details — the ~4.5KB async script and no Tag Manager claim addresses my performance concerns. EU/Germany hosting with the GA4 forwarding caveat stated openly is actually a trust signal, they're not hiding the US transfer issue. Now the two features I came for: the 'why they leave' persona thing and the SEO fixes. Both sections are right below, need to read them properly before judging."
Worked: They openly disclose that optional GA4 forwarding sends data to Google (US) while their own data stays in the EU — honest, concrete hosting details (Germany, Schrems II).
Action: scroll
Step 4/Effort
Read: Feature list continues: WordPress plugin install with site ID baked in, page change tracking with 14-day before/after comparisons, engagement quality scoring (bounce/skim/engaged/gold), and AI agent integration via MCP for plain-language queries and SEO fixes like cannibalisation and canonicals. Then a 3-step setup: email only, no password or credit card, add domain, paste one script line.
Thought aloud: „The page change tracking with before/after windows is genuinely useful — that's something I hack together manually in GA with annotations. Engagement scoring beyond bounce rate is a real GA weakness addressed. The AI/MCP bit sounds buzzwordy but it names concrete fixes (cannibalisation, canonical) which is what I want to see. The setup promise — email only, no password, no credit card, one script line — lowers the barrier a lot. Still haven't seen the 'why they leave' feature or a proper GA comparison; there's more below, so I'll keep reading before deciding anything."
Worked: The 3-minute setup with no password, no credit card, and a single script line removes the usual trial friction — and page change tracking with 14-day before/after speaks directly to a real GA workflow pain.
Action: scroll
Step 5/Safety 3/5Safety
Read: Pricing section with three tiers — Free (10,000 events, 1 site), Starter (100,000 events, 5 sites), Growth (500,000 events, 20 sites) — listing features like team access, AI Analytics, Google Analytics import, data export. Closing copy: 'See what you've been missing' and a 3-minute setup link below.
Thought aloud: „'Simple pricing. No surprises' — except I don't actually see any prices. Event limits are useful, but what does Starter cost per month? I need a number for my budget case. The Google Analytics import on the paid tiers is a real plus — I don't want to lose years of historical data when I switch. Data export on Growth also eases my lock-in worries. 'AI Analytics (10/month)' is vague though — ten what, reports? As someone wary of AI hype, that label tells me nothing. Let me finish the page before judging."
Friction: 'Simple pricing. No surprises' headline, but the tiers show only event limits — no actual monthly prices anywhere visible, so I can't evaluate the real cost
Worked: Google Analytics import on paid tiers and data export on Growth directly address my migration and vendor lock-in concerns
Action: scroll
Step 6/Safety
Read: Bottom of the page: final CTA section — 'See what you've been missing', 'Stop annoying your visitors with cookie banners. See your real numbers. Decide for yourself.' Plus reassurances: no credit card, no cookie banner, and can run alongside Google Analytics. Links above include 'Compare all features', 'See how it works', and several 'Get started' buttons.
Thought aloud: „Okay, I've read through the whole page now. The 'Add alongside Google Analytics if you want' line is smart — it lowers the risk for me, I could run both in parallel and compare the numbers myself instead of trusting their marketing. That's the kind of proof I'd actually accept. But before I even think about adding a script, I need the full picture: how their cookieless tracking stacks up against GA4 feature by feature, and whether the 'why they leave' and SEO stuff is real or just landing-page fluff. The 'Compare all features' link is exactly the artifact I'm looking for — that's my next step, not the signup buttons."
Worked: 'Add alongside Google Analytics if you want' — running both tools in parallel lets me verify their data against GA myself before committing, which directly addresses my trust issue
Action: click 6
Step 7/pricingSafety
Read: Pricing page with four tiers — Free, Starter, Growth, Scale — but the tier cards only show names and target audiences so far. There's also a 'Considering another tool?' section teasing an honest comparison with GA, Plausible, Fathom, and Matomo.
Thought aloud: „Finally, the actual pricing page. I came here because the homepage showed event limits but no prices. I can see the four tier names, but the actual monthly costs must be below — I'm not judging this page until I've scrolled through all four tiers. The 'Considering another tool?' block is interesting too — an honest comparison that admits where competitors beat them is exactly the kind of thing that earns my trust, but prices first, comparison after."
Worked: 'Considering another tool?' section promising an honest comparison including 'where they beat us' — admitting weaknesses is a strong credibility signal for a skeptical buyer like me
Action: scroll
Step 8/pricingSafety
Read: I'm in the FAQ section now, below the plan comparison table. The FAQ answers are concrete: events defined clearly (pageviews + custom events each count as one), a direct answer on consent banners citing ePrivacy Article 5(3), what happens at the event limit (they stop recording, no overage charges), and plan switching with prorated billing. There's still content below the fold.
Thought aloud: „This FAQ is actually doing work for me. The consent banner answer isn't hand-wavy — it cites the exact legal mechanism (ePrivacy 5(3), no storage or access on the device) which is the argument I'd need to defend this to our DPO. And 'we stop recording, no overage charges' removes the surprise-bill fear. I'm at 64% down the page, so there's more to read before I judge this — let me finish the FAQ and see what's underneath."
Worked: The FAQ answers my exact objection with specifics: cookieless justified via ePrivacy Directive Article 5(3), and hitting the event limit just pauses recording with no overage charges — credible, not marketing fluff
Action: scroll
Step 9/pricingSafety
Read: Bundt af pris-FAQ: hitting event limit pauses recording with no overage charges, plan switches are prorated, data lives on Hetzner servers in Germany, and a DPA is available via email.
Thought aloud: „The no-overage-charges answer is exactly the concrete detail I wanted — a hard stop instead of surprise billing, and my historical data stays accessible. DPA on request plus Hetzner/Germany storage ticks my compliance boxes. I've now been through the full FAQ. My last open question is how this actually stacks up against GA4 feature-by-feature — and there's a 'See the comparison' link right here. That's my next stop before I decide anything."
Worked: Event limit FAQ promises a hard stop with no overage charges and keeps dashboard/historical data accessible — predictable billing with no gotchas
Action: click 4
Step 10/compareSafety
Read: A comparison table titled 'Compare Web-Tracking.eu' — rows for cookieless, consent banner, EU hosting, script size, engagement scoring, page change annotations, with columns that appear to be Plausible, Matomo, Fathom and others. I can see links to 'From Google Analytics' and other competitors further down, and there's more table content below the fold.
Thought aloud: „An honest comparison page including 'where we lose' — that's a good sign, most vendors never show that. The engagement quality scoring and page change annotations are marked as unique to them, which matches what I saw on the homepage. But the column I actually care most about — Google Analytics, the thing I'm replacing — isn't fully visible in this viewport. Before I judge this table, I need to scroll down and see the rest, especially the GA column and whatever these 'From X' links lead to."
Worked: The table openly admits weaknesses ('including where we lose') and marks competitors' partial capabilities honestly rather than trashing everything — that builds credibility with me as a skeptical buyer
Action: scroll
Step 11/compareSafety
Read: Resten af comparison-tabellen: AI insights powered by Mistral AI (France), MCP integration for Claude/Cursor, team roles, custom events, data export, API, custom first-party domain. Open source: No for Web-Tracking.eu. Free tier 10k events/mo, lowest paid tier €5/mo. Then an 'Honest take: when to pick what' section that recommends GA4, Plausible, Fathom or Matomo depending on needs, and lists when Web-Tracking.eu makes sense (EU hosting without self-hosting).
Thought aloud: „Finally a concrete price — €5/mo entry tier answers the question the homepage dodged. The Mistral AI detail matters to me: a European AI for the insights feature, consistent with their EU story. The 'Honest take' section is the most credible thing on this page — it literally tells me to stay on GA4 if I need Google Ads attribution depth or can't move my tag setup. That's the opposite of over-hyped marketing, and it makes the 'pick us' case more believable. Open source 'No' is a small minus but they state it plainly. There's still content below — I want to see the migration links, especially 'From Google Analytics', since that's my actual situation."
Worked: The 'Honest take' section explicitly recommends competitors (including GA4) for use cases where they fit better — that directly addresses my wariness of over-hyped solutions and builds real trust. Plus the €5/mo entry price finally gives me a concrete cost anchor.
Action: scroll
Step 12/compareEffort
Read: Bottom of the compare page: a 'Migration guides' section with step-by-step switching instructions per tool — Google Analytics, Plausible, Fathom, Matomo — plus a 'Try free →' CTA.
Thought aloud: „Migration guides with a dedicated GA one — that's exactly my situation. If they document the switch step-by-step, that removes my last practical objection about effort. This is the final check before I'd commit; let me open the GA guide."
Worked: Per-tool step-by-step migration guides, including one specifically for Google Analytics — directly addresses my switching-effort concern instead of leaving me to figure it out alone
Read: Landing page headline: 'Tracking without the cookie banner.' Subheading emphasizes cookieless analytics for European websites, claims to show visitors GA misses, promises data stays in EU. No credit card, no cookie banner, works with GA. Built in Denmark, hosted in Germany.
Thought aloud: „Okay, this is exactly what I'm looking for — a cookieless tracking alternative positioned against GA's consent-banner limitations. The headline is direct and speaks to my pain point. The 'no credit card' and 'works alongside GA' are reassuring. But I'm skeptical — I need to understand HOW this actually works technically before I commit. The eye-tracking shows the headline and CTA dominate, which makes sense. Let me scroll down to see the full pitch, features, and proof points before I decide whether to dig into 'how it works' or jump to signup."
Worked: Headline directly addresses my core problem: GA data gaps due to consent banners. Value prop is clear and specific to EU context.
Action: scroll
Step 2/Safety
Read: Hero section with three pain points about GA (consent banners, GDPR data transfer, complexity) and a value prop about understanding visitor drop-off. Multiple 'Get started' buttons visible below. I'm at 22% scroll depth with more content below.
Thought aloud: „Good — this confirms the core positioning: cookieless tracking + visitor behavior insights. I see the three main objections I have (consent data loss, GDPR risk, GA complexity) being directly addressed. But I need to understand the technical mechanism before I commit. Let me scroll down to see the full feature set and the 'why they leave' and 'SEO fixes' features mentioned in my task. I should also look for any technical explanation or comparison to GA capabilities."
Worked: The three pain points directly mirror my concerns as a skeptical marketing manager — consent filtering, GDPR risk, and GA complexity. Feels like they understand my actual problems, not just selling a generic alternative.
Action: scroll
Step 3/Meaning
Read: The page shows core features: cookieless tracking, AI personas predicting visitor drop-off, SEO optimization tools, EU data hosting, one-script implementation, team access, and trend comparison. Multiple 'Get started' links visible, plus feature comparison and implementation options. I'm at 43% scroll depth with more content below.
Thought aloud: „I'm seeing the value proposition clearly now — no cookies, EU-hosted, simple implementation. But I need to understand the technical details of the 'cookieless' tracking before I commit. How does it actually work without cookies? And I want to see the 'why they leave' feature in action and understand the SEO fixes. The 'See how it works' link might explain the technical side. Let me click that first before diving into signup."
Worked: Clear feature list addressing my main concerns: no consent banner friction, EU hosting (Schrems II compliant), simple one-script implementation, and concrete features like visitor drop-off prediction and SEO optimization
Action: click 2
Step 4/
Read: I'm at 13% of the page. I see three key objections listed: consent banners causing data loss, GDPR risk from US data transfer, and GA complexity. There are multiple 'Get started' links below and a 'See how it works' link. I need to understand the technical mechanism before committing.
Thought aloud: „I clicked 'See how it works' in step 3, so I should be seeing technical details now — but the screen still shows the objections section. Either that click didn't navigate, or I'm still on the main page. I need to scroll down to see what's actually below, or check if the 'See how it works' section is further down on this same page. Let me scroll to see the full content before deciding on my next action."
Action: scroll
Step 5/Meaning
Read: I'm still on the homepage showing the value props: 'why they leave' feature with synthetic personas, 'concrete SEO fixes' with AI suggestions, and basic analytics without cookies. Below are multiple 'Get started' buttons and a feature comparison link.
Thought aloud: „Wait — I clicked 'See how it works' in step 3, but I'm still seeing the homepage objections section. Either the click didn't register, or 'See how it works' didn't navigate anywhere. Let me scroll down to see if there's technical explanation content further down on this same page, or if I need to try clicking that link again. The page says I'm only 34% down, so there's definitely more content."
Worked: The feature descriptions are concrete and specific: 'synthetic personas built from your real search queries', 'AI suggestions for your search-result snippet', 'automatic detection of your own pages competing'. This is exactly the kind of proof I need — not vague marketing, but actual methods.
Action: scroll
Step 6/Meaning
Read: I'm still on the homepage at 56% scroll depth. I can see feature details: EU data storage, simple 1-line code implementation, team access, trend comparison, AI insights, GA4 import, WordPress plugin, page change tracking, engagement scoring, and AI agent integration. There are multiple 'Get started' buttons below, and a 'Compare all features' link.
Thought aloud: „I clicked 'See how it works' two steps ago but I'm still on the homepage. Either the click didn't register, or 'See how it works' doesn't navigate — it might just scroll the page. I'm at 56% down, so there's more content below. Let me scroll down to see if there's more information about the technical implementation, or if I can find another way to access the technical details. I need to understand how the cookieless tracking actually works before I commit to anything."
Worked: The feature list is concrete and specific — EU hosting, 4.5 KB script, async loading, WordPress plugin, AI insights, GA4 import, and engagement scoring beyond bounce rate. These are real differentiators I can evaluate.
Action: scroll
Step 7/
Read: I'm at 77% down the homepage. I see the onboarding flow (create account → add site → paste script) and pricing tiers (Free/Starter/Growth). The 'See how it works' link I clicked earlier didn't navigate — I'm still on the homepage. There's more content below.
Thought aloud: „I've been stuck on the homepage for three steps now. The 'See how it works' click in step 3 didn't work — either it's not a real link or it just scrolls within the page. I need to stop assuming and actually see what's below. I'm at 77%, so let me scroll to the bottom and see if there's a technical explanation section, or if I need to take a different route — maybe 'Get started' or 'Add to your site' is where the technical details live. Let me scroll down first to see the full page."
Action: scroll
Step 8/
Read: I'm at the bottom of the homepage showing 'See what you've been missing' section with CTA buttons. The page says there's more content below (99% scrolled). I can see multiple 'Get started' links and a comparison link.
Thought aloud: „I've been stuck on the homepage for four steps now — clicked 'See how it works' but stayed here. The scroll position says there's MORE content below even though I'm at 99%. Let me scroll down to see if there's actual technical documentation or if the page just has more marketing copy. I need to understand the technical mechanism before committing to anything."
Action: scroll
Step 9/Defect 4/5
Read: Bottom of homepage: final CTA section with 'See what you've been missing', value prop (no banners, real numbers), and multiple 'Get started' links. I'm at 100% scroll, so I've seen the full page.
Thought aloud: „I've clicked 'See how it works' [2] four times now and stayed on the homepage each time. This is clearly not a working link — either it's broken or it's not actually a clickable element. I'm stuck in a loop. I need to try a different action. The 'Get started' buttons [3], [4], [5] are my actual conversion path. Since I need to understand how this works technically AND evaluate the features, I should click 'Get started' to enter the actual product flow. That's the real test of whether this solution works for me."
Friction: 'See how it works' [2] link does not navigate — clicked multiple times with no page change. Either dead link or not a real clickable element.
Action: click 3
Step 10/auth/login
Read: Login page titled 'Get started'. Email field, website field, and two sign-in options: 'Continue with email' and 'Sign in with Google'. Also a back link to homepage. The page promises free plan, no credit card, 60 seconds to set up.
Thought aloud: „Okay, I'm now on a login/signup page. I've been stuck on the homepage trying to click 'See how it works' which didn't work. Now I'm here at /auth/login. My goal is to understand the technical details of how cookieless tracking works, and to evaluate the 'why they leave' and 'SEO fixes' features. I can't verify email (no inbox), so signing up won't work. But wait — I should check if there's any public documentation or demo I can access without signing in. Let me go back to the homepage first and look for alternative ways to access technical information or a feature walkthrough that doesn't require login. The back link is right here."
Action: click 5
Step 11/
Read: Back on the homepage. I see the value prop clearly: cookieless, EU-hosted, no banner. There are multiple 'Get started' links below. I've already wasted time clicking 'See how it works' [2] which didn't navigate. I need to understand the technical details and evaluate the features, but the 'See how it works' link is broken. I should try a different path — either scroll to see what else is on this page, or click 'Get started' to move forward and see if I can access the technical/feature details from there.
Thought aloud: „I've clicked [2] multiple times and it didn't work — that's a dead link. I'm running low on patience. I need to either find working navigation or decide this isn't worth my time. Let me scroll down to see what else is on this page — maybe there's a better entry point to the technical details or features I need to evaluate."
Action: scroll
Step 12/
Read: Homepage showing objections to GA (consent banners, GDPR risks, complexity) and a value prop about finding why visitors leave. Multiple 'Get started' links visible below, plus a 'Compare all features' link. I'm at 22% scroll depth with more content below.
Thought aloud: „I've been trying 'See how it works' [2] multiple times and it's not working — that's a dead link. I'm frustrated but I need to move forward. My actual goal is to understand the cookieless tracking and evaluate the features. I can see there are 'Get started' buttons below [3], [4], [5] and a 'Compare all features' link [6]. Let me scroll down to see the full page and find a working path forward. I've wasted enough steps on [2]."
Action: scroll
Time-pressed Web Developer · GLM-5.3-Flash · 11 steps · done
Step 1/Meaning
Read: Hero for a cookieless, EU-hosted analytics tool. Headline promises tracking without a cookie banner, data stays in the EU, built in Denmark/hosted in Germany, free to add, works alongside Google Analytics.
Thought aloud: „Okay, 'Tracking without the cookie banner' — that's exactly the pitch I need for my EU clients. If this is truly cookieless, I can rip out those annoying consent banners. Sounds like a Plausible/Fathom-style tool. Before I sign up for anything I want the technical facts: how do I install it, how heavy is the script, is there an API and decent docs. 'See how it works' should get me there fastest."
Worked: The headline instantly tells me the core value — no cookie banner — and 'Built in Denmark. Hosted in Germany' pre-answers my EU-compliance question in one line.
Action: click 2
Step 2/Meaning 2/5Meaning
Read: Still on the homepage, now at a 'Sound familiar?' section listing pain points: consent banners filtering data, GA sending data to US servers, GA being too complex. Links for 'Get started' and 'Compare all features' further down.
Thought aloud: „I clicked 'See how it works' and what I get is the problem pitch — okay, I already bought into the problem, that's why I'm here. Where's the actual mechanics? Script snippet, install steps, file size? Let me scroll — this is probably just the top of the section."
Friction: Clicked 'See how it works' but landed on pain-point marketing copy instead of actual mechanics
Worked: The pain points are exactly my clients' objections — shows they understand the developer/agency use case
Action: scroll
Step 3/Safety
Read: Still on the landing page, now mid-way. I'm past the 'Optimise' add-on pitch (personas, SEO fixes, before/after measuring) and into the core analytics section: traffic dashboard, top pages, referrers, countries. Then 'No cookies needed — no consent banner required'. Below there are Get started links and 'Add to your site — takes 3 minutes'.
Thought aloud: „Still no actual mechanics — this is all feature marketing. But 'No cookies needed' does confirm the cookieless claim, which is the whole reason my client cares. 'Add to your site — takes 3 minutes' is the first thing that smells like implementation info. Let me scroll to the bottom — pricing, technical details, docs links usually live down there."
Worked: 'No cookies needed — no consent banner required' concretely confirms the cookieless promise, and 'Add to your site — takes 3 minutes' signals a lightweight integration
Action: scroll
Step 4/Meaning
Read: Implementation details at last: one line of code, ~4.5 KB gzipped async script, no Core Web Vitals impact. Also feature list — team roles, GA import, WordPress plugin, MCP/AI integration.
Thought aloud: „Now this is what I needed: one line of code, 4.5 KB async — performance question answered. MCP integration and 'public install tools work without an account' is dev-friendly. I should click 'Add to your site — takes 3 minutes' to see the actual implementation steps."
Worked: Concrete numbers: ~4.5 KB gzipped, async, no Core Web Vitals impact, one line of code — exactly the developer facts I came for
Action: click 7
Step 5/auth/loginSafety
Read: Signup/login page: email field, website field, magic-link via email or Google. 'Free plan. No credit card. Takes 60 seconds.'
Thought aloud: „Clean minimal signup — email plus my site URL, that's low effort, and 'no credit card' kills the usual hesitation. But this whole flow runs on a login link sent to my inbox — I can't receive or verify email in this test, so this is as far as I can go through signup. That's not the site's fault, it's my constraint. What I still haven't seen is the exact implementation steps and any API/docs — a dev like me wants to read those BEFORE creating an account. Back to home to see if documentation is publicly reachable."
Worked: 'Free plan. No credit card. Takes 60 seconds.' — instantly removes signup risk and effort concerns
Action: click 5
Step 6/Safety
Read: Tilbage øverst på forsiden efter mit signup-klik — samme budskab: cookieless EU-analyse, data forlader aldrig EU, bygget i Danmark, hostet i Tyskland.
Thought aloud: „Det klik sendte mig tilbage til forsiden i stedet for til et dashboard — ligegyldigt, tilmelding ville alligevel kræve en rigtig indbakke, hvilket jeg ikke har i denne test. Tilbageværende spørgsmål er udviklersiden: API-adgang og faktisk dokumentation. Ingen docs-link synligt heroppe, men der er et 'Compare all features'-link længere nede, og footere har normalt dokumentationslinks. Jeg scroller gennem resten af siden, før jeg dømmer den."
Worked: 'Your data never leaves the EU' plus built in Denmark / hosted in Germany — konkrete hosting-fakta, som er det præcise compliance-svar, jeg kan videregive til min kunde
Action: scroll
Step 7/
Read: Back on the homepage, about 22% down — this is the same pain-point pitch I already read: consent banners filter your data, GA sends data to US servers, GA is too complex. One new angle: they claim to simulate why visitors leave, suggest improvements, and measure whether it worked.
Thought aloud: „I've looped back to the homepage. Doesn't matter — I already got my core answer earlier: one line of code, 4.5 KB async, so performance impact is settled. The last thing on my checklist is developer-friendliness: API access and proper docs. 'Compare all features' further down this page is the most likely place to confirm that, so I'm jumping straight to it instead of re-reading marketing I've already seen."
Action: click 6
Step 8/pricing
Read: Pricing page with four tiers: Free, Starter, Growth, Scale. Plus a comparison section against GA, Plausible, Fathom, Matomo with a 'See the comparison' link.
Thought aloud: „Pricing is secondary for me — my client question is implementation and performance, which I already answered (one line, 4.5 KB async). But this comparison page could be useful for justifying the choice to my client. Quick look, then I'm done."
Action: click 4
Step 9/compareSafety
Read: A comparison table vs Plausible, Matomo, Fathom etc. — script size ~3 KB gz, async yes, one script tag install yes, WordPress plugin yes, but no self-hosting option. They even admit where they lose.
Thought aloud: „This table is actually the fastest way to sanity-check what I found earlier — ~3 KB gz matches the 4.5 KB claim, async confirmed, one script tag confirmed. And they openly say 'No' on self-hosting, which makes the rest credible. My one remaining open question is developer features: API access and docs. The table continues below — if there's an API row down there, I'm done."
Worked: The table states script size (~3 KB gz) and async/Core Web Vitals impact as explicit rows — exactly the performance facts I came for — and honestly marks their own weaknesses (no self-hosting), which makes it believable
Action: scroll
Step 10/compareSafety
Read: Bunden af sammenligningstabellen: API-adgang er 'Ja' på tværs af alle værktøjer, MCP-integration er kun her, plus et ærligt 'hvornår skal man vælge hvad'-afsnit og migrationslinks (GA, Plausible, Fathom, Matomo) og en 'Prøv gratis'-CTA længere nede.
Thought aloud: „API-adgang: ja — det er min udviklervenlige boks markeret. MCP-integration er unik for dem, pæn bonus. Og dette 'Honest take'-afsnit fortæller mig faktisk, hvornår jeg IKKE bør vælge dem, hvilket mærkeligt nok gør hele sammenligningen troværdig. EU-hosting i Tyskland uden besværet med selv-hosting er præcis min klients sag. Lad mig se resten af siden — de migrationslinks kan indeholde de faktiske implementeringstrin."
Worked: 'Honest take: when to pick what'-afsnittet angiver åbent, hvornår konkurrenterne er det bedre valg — det gør sammenligningen troværdig i stedet for at virke som markedsføring
Action: scroll
Step 11/compareEffort
Read: Bottom of the compare page — migration guides for switching from GA, Plausible, Fathom, Matomo.
Thought aloud: „Migration guides are a nice maintenance-angle touch — confirms they make switching easy, which matters for low ongoing effort. But my core questions are already answered: one line of code, 4.5 KB async, API access, MCP. I'm done here."
Worked: Step-by-step migration guides for each competitor directly address the switching/maintenance concern
Action: done
Time-pressed Web Developer · Claude-Haiku · 12 steps · step-budget
Step 1/Meaning
Read: A cookieless analytics platform targeting EU websites. Headline promises tracking without cookie banners. Key claims: EU data residency, no credit card needed, works with Google Analytics. Multiple 'Get started' and 'Add to site' CTAs visible.
Thought aloud: „Okay, this is exactly what I need — an EU-compliant analytics solution. The headline and 'Add to your site free' button match what I'm looking for. They're claiming cookieless, EU-hosted, and easy integration. But I need the actual implementation details: script size, performance impact, API docs, and exact setup steps. Let me scroll down to see what else is on this page before I click anything — I want to understand what they offer before committing to a flow."
Worked: Headline immediately signals EU compliance and cookieless approach — directly addresses my brief. 'No credit card' and 'Works alongside Google Analytics' are reassuring for a freelancer evaluating options.
Action: scroll
Step 2/Meaning
Read: The page explains the problem with Google Analytics (consent banners, data leaving EU, complexity) and promises better insights. I can see multiple 'Get started' buttons below. I'm 22% down the page with more content below.
Thought aloud: „I need to find the exact implementation steps and confirm script size/performance impact. The 'Add to your site — takes 3 minutes' link at the bottom sounds promising for implementation details. But I should scroll down first to see all options and understand what's available before clicking."
Worked: Clear problem statement (GDPR risks, data leaving EU, complexity) directly addresses my compliance concerns as a developer
Action: scroll
Step 3/Meaning
Read: I see key features: one-line script integration (~4.5 KB gzipped, async load, no Core Web Vitals impact), EU-hosted, no cookies needed, team access. Multiple 'Get started' links below. I'm at 43% down the page with more content below.
Thought aloud: „Good — the script size and performance claims are right here: 4.5 KB gzipped, async, no impact on Core Web Vitals. That's exactly what I need to confirm. But I need the actual implementation steps and maybe API docs. Let me scroll down to see what's below — there might be a technical docs link or a more detailed integration guide further down."
Worked: Script size and performance impact clearly stated upfront (4.5 KB gzipped, async, no Core Web Vitals impact) — exactly what a developer needs to know
Action: scroll
Step 4/Effort
Read: I can see the setup process: create account (email only, no password/card), add domain, paste one script tag. Performance claims confirmed earlier (4.5 KB gzipped, async). There's more content below — likely the actual onboarding flow or more features.
Thought aloud: „Good, the 3-minute setup is clear and matches what I need. I've got the script size and performance impact already. Now I need to see the actual implementation — either click 'Get started' to begin the onboarding, or scroll down to see if there's more technical detail about the script integration or API access for developers. Let me scroll down first to see what else is there before committing to a flow."
Worked: Setup process is straightforward and minimal: email-only signup, no password/card required, one-line script paste. Matches my need for easy integration.
Action: scroll
Step 5/
Read: Pricing tiers (Free, Starter, Growth) with event limits and features. At 86% down the page with more content below. I can see 'Add to your site' and 'Get started' buttons, plus a link to compare features.
Thought aloud: „I've already confirmed the script size (4.5 KB gzipped), performance impact (no Core Web Vitals impact), and the 3-minute setup claim. Now I need to find the actual implementation steps and check for developer-friendly features like API access or documentation. The pricing section isn't my goal — I should scroll down to see if there's more technical info, documentation links, or API details below."
Action: scroll
Step 6/Meaning
Read: Bottom of page: 'See what you've been missing' section with tagline about cookie banners and real numbers. Multiple 'Get started' links visible, plus 'Add to your site — takes 3 minutes' link at bottom.
Thought aloud: „I've scrolled through the entire page and confirmed the key info I need: 4.5 KB gzipped script, async loading, no Core Web Vitals impact, 3-minute setup. But I haven't actually found the implementation steps yet — just claims about how easy it is. I need to click into the actual setup flow to see the exact code/steps and check for API access or documentation. The 'Add to your site — takes 3 minutes' link at the bottom looks like the direct entry point to implementation."
Worked: Script size (4.5 KB gzipped) and performance claims (async, no Core Web Vitals impact) are clearly stated upfront — exactly what I need to assess for a client project.
Action: click 7
Step 7/auth/login
Read: Login page with email entry field, Google sign-in option, and a 'Continue with email' button. The page says it takes 60 seconds, no credit card needed, and uses Google only for email verification.
Thought aloud: „I'm on the login/signup page now. I need to get to the implementation steps and confirm the technical details. The previous steps mentioned I already have the script size (4.5 KB gzipped) and performance info. But I'm now at a login wall. I should enter an email to proceed and access the actual implementation instructions. Let me fill in the email field and continue."
Action: fill 1 dev@example.com
Step 8/auth/login
Read: Login page asking for email to get started. I see an email field pre-filled with 'dev@example.com', a website field, and options to continue with email or Google. There's also a back link to home.
Thought aloud: „I'm stuck in a login flow, but I can't actually verify email since I don't have access to an inbox. The previous steps got me the key info I needed (4.5 KB gzipped, async, no Core Web Vitals impact, 3-minute setup). But I need the actual implementation steps and API access details — that's what I came for. The login wall is blocking me from getting to the technical documentation. I should go back to the home page and look for a direct link to docs or implementation guide without needing to log in."
Action: click 5
Step 9/
Read: I'm back on the homepage. The page shows 'Tracking without the cookie banner' with claims about cookieless analytics, EU data residency, and no cookie banner needed. There are multiple 'Get started' links and an 'Add to your site' link visible. I'm at 0% scroll position with more content below.
Thought aloud: „Wait — I'm back at the homepage after the login attempt. I've already confirmed the technical specs I need (4.5 KB gzipped, async, no Core Web Vitals impact). But I still need the exact implementation steps and ideally API access or documentation. The login flow didn't work because I can't verify email. Let me try a different approach — I should look for developer documentation or a direct implementation guide without needing to log in. Let me scroll down and see if there's a public docs link or developer section I missed."
Action: scroll
Step 10/
Read: Back at the homepage. I can see the main value props: consent-free tracking, GDPR-compliant, simpler than Google Analytics. Multiple 'Get started' buttons and an 'Add to your site — takes 3 minutes' link visible. I'm 22% down the page with more content below.
Thought aloud: „I've already got the technical specs I need from the previous scroll (4.5 KB gzipped, async, no Core Web Vitals impact). I tried the login flow but hit the email verification wall — that's a dead end without a real inbox. The homepage keeps showing the same value props and CTAs. I need to find actual implementation documentation or API details. Let me scroll down to see if there's a developer docs section, pricing breakdown, or technical integration guide further down the page. If not, I'm done here — I've confirmed the key performance metrics, and the rest requires either logging in (which I can't complete) or finding a dedicated docs site."
Action: scroll
Step 11/
Read: Homepage showing analytics features: cookieless script (4.5 KB gzipped, async, no Core Web Vitals impact), EU-hosted data, no cookies needed, one-line setup. Multiple 'Get started' buttons visible. I'm 43% down the page with more content below.
Thought aloud: „I've already confirmed the core technical specs I need: 4.5 KB gzipped, async loading, no Core Web Vitals impact, and 3-minute setup. The login flow didn't work because I can't verify email. I'm running low on patience — I need to either find the actual implementation documentation without logging in, or conclude this isn't accessible to me as a developer without an account. Let me scroll down one more time to see if there's a public docs link or API reference section below, then I'll decide whether to give up or try the 'Add to your site' link again."
Action: scroll
Step 12/
Read: I'm back at the homepage, 65% down the page. I can see the 3-minute setup flow (Create account → Add site → Paste one line) and several 'Get started' buttons. I've already confirmed the technical specs I need: 4.5 KB gzipped, async loading, no Core Web Vitals impact.
Thought aloud: „I've been going in circles. I got the key technical info I needed earlier (script size, performance impact, 3-minute setup). I tried to access implementation details through login but hit the email verification wall. I'm down to my last step of patience. The homepage keeps showing me the same overview. I should either: (1) try one more direct path to implementation docs without login, or (2) conclude that the public-facing info is sufficient for my needs. Looking at the elements, [7] 'Add to your site — takes 3 minutes' seems to be the actual implementation entry point. Let me try that one more time to see if it bypasses login or shows the actual steps."
Read: Headline: 'Tracking without the cookie banner.' It's cookieless analytics for European websites — built in Denmark, hosted in Germany, data stays in the EU. It claims to show visitors Google Analytics misses and 'find out why they leave'. No credit card needed. Links: 'See the legal basis', 'Add to your site free', 'See how it works', plus several 'Get started' links further down.
Thought aloud: „Okay, first thing my eyes hit: 'Tracking without the cookie banner' — instantly relatable, I hate nagging my readers with cookie popups on my blog. And then I read 'find out why they leave' — wait, that is literally the question I keep asking about my posts. EU-hosted, no credit card... that all lowers my guard. Before I click anything I want to see what this 'why they leave' thing actually looks like and whether there's something about engagement scoring. Scrolling down."
Worked: The promise 'find out why they leave' speaks directly to my exact problem as a content creator — feels immediately relevant
Action: scroll
Step 2/Meaning
Read: Okay, this section hits home — three pain points about Google Analytics, and honestly 'GA is too complex' is exactly me. But the line that really grabs me: 'Find out why they leave — and what to do about it'. That sounds like the 'Why do they leave?' feature I came here for. It says they simulate why visitors leave, suggest concrete improvements, and measure if it worked. I want to read more before I commit to anything.
Thought aloud: „Whoa, okay, this is speaking my language. Consent banners messing with data — yes, I've seen my numbers look weird. And 'we simulate why they leave a page, suggest concrete improvements' — that's literally what I want to know! But it's all claims so far. I need to see HOW it works, and whether the advice is actually simple. Let me keep reading down the page before I click anything."
Worked: The 'Find out why they leave — and what to do about it' section directly names my exact problem and promises concrete improvements plus measurement — that's a strong hook for me
Action: scroll
Step 3/Safety 2/5Meaning
Read: Feature list flying by: synthetic personas that predict why visitors leave, AI snippet suggestions, before/after measurement, traffic dashboard, no cookies, EU hosting, one script tag, team roles, trend comparison. Also saw 'Optimise is an add-on on top of the analytics' — and three 'Get started' links plus 'Compare all features' further down.
Thought aloud: „Okay wait — 'synthetic personas... predict what makes visitors leave' — that is literally the 'Why do they leave?' thing I came for! And 'we measure before/after so you can see how much it moved, not just guess' — that's the kind of plain-language promise I love. But 'Optimise is an add-on' — does that mean the good stuff costs extra? Hmm. I haven't actually seen 'Engagement quality scoring' spelled out yet, and there's clearly more page below. Keep scrolling before I click anything."
Friction: 'Optimise is an add-on on top of the analytics' — as a novice I can't tell if the engagement features I want are included or cost extra, and no price is visible here.
Worked: 'Synthetic personas built from your real search queries... predict what makes visitors leave' and 'we measure before/after — so you can see how much it moved, not just guess' — plain, concrete language that directly matches my goal of understanding why readers bounce.
Action: scroll
Step 4/Meaning
Read: Feature blurbs: WordPress plugin one-click install, page change tracking with 14-day before/after stats, engagement quality scoring (sessions bucketed as bounce/skim/engaged/gold), AI agent integration, then a 3-step setup guide with Get started links and a 'Compare all features' link further down.
Thought aloud: „Okay THIS is the thing I came for — 'Engagement quality scoring'. Bounce, skim, engaged, gold... that actually makes sense to me, no jargon wall. And 'find your most valuable pages — and the gold-traffic ones with weak content' is exactly the kind of actionable advice I was hoping for, it tells me WHERE to look and WHAT to fix. The page change tracking with before/after is a nice bonus for checking if my redesigns actually worked. There's still more page below, and I spotted a 'Compare all features' link down there — that might finally answer whether this stuff is included or costs extra. Scrolling down."
Worked: Engagement quality scoring is explained in plain language — the bounce/skim/engaged/gold buckets and 'gold-traffic pages with weak content' make it obvious what insight I'd actually get
Action: scroll
Step 5/Meaning 2/5Safety
Read: Pricing section: three plans — FREE (10k events, 1 website, all core features, 10 AI Analytics/month), STARTER (100k, 5 sites, team access, 50 AI Analytics, GA import), GROWTH (500k, 20 sites, priority support, data export). Closing line: 'See what you've been missing... Decide for yourself.' There's still a bit of page below me.
Thought aloud: „Oh nice, actual pricing — and 'Start free' with 'All core features' on the free plan, that's a relief, so the engagement scoring stuff isn't locked behind a paywall apparently. But hmm, 'AI Analytics (10/month)' — ten of WHAT per month? Is that the 'why do they leave' brain? Is 10 enough to actually learn anything about my blog? That's vague. Whatever — there's still a chunk of page below me, let me finish reading before I click anything."
Friction: 'AI Analytics (10/month)' is cryptic — I can't tell what counts as one AI Analytics use or whether the 'Why do they leave?' insights come out of that quota
Worked: 'Simple pricing. No surprises' with a free tier listing 'All core features' directly answers my worry that the engagement features might be a paid add-on
Action: scroll
Step 6/Safety
Read: I'm at the bottom of the page now — closing pitch: 'See what you've been missing', 'No credit card. No cookie banner. Add alongside Google Analytics if you want.' Plus final CTA links like 'Add to your site — takes 3 minutes' and a 'Compare all features' link up a bit.
Thought aloud: „Okay, so the ending is reassuring — no credit card, no cookie banner, works alongside Google Analytics. That lowers the barrier. But I still have that nagging question from the pricing table: what exactly is 'AI Analytics (10/month)' and is the 'Why do they leave?' stuff included in free? Before I sign up for anything, I want to see the full feature list — 'Compare all features' sounds like exactly where I can check that."
Worked: 'No credit card. No cookie banner.' right at the signup pitch removes my two biggest hesitations about trying a new analytics tool.
Action: click 6
Step 7/pricingSafety
Read: Pricing page with four tiers — Free, Starter, Growth, Scale — plus a 'Considering another tool?' section promising an honest comparison with Google Analytics, Plausible, Fathom and Matomo.
Thought aloud: „Okay, four plans. But I can only see the tier names right now — I need the actual prices and what's inside each one, mainly whether the engagement scoring and 'why they leave' insights are in the free plan or locked behind a paid tier. That 'including where they beat us' line is genuinely disarming, very few tools admit that. I'll check the plan details first, then maybe peek at that comparison."
Worked: The 'Considering another tool?' section openly admits where competitors beat them — that kind of honesty makes me trust the whole pricing page more
Action: scroll
Step 8/pricingSafety
Read: I'm in the pricing page's comparison table area — I can see checkmarks and dashes but the row labels aren't in view right now. Below that is a FAQ: what counts as an event, no cookie banner needed, hitting event limits just pauses recording with no overage charges, and plans can be switched anytime with prorated billing.
Thought aloud: „Okay, the FAQ is actually answering real questions I'd have — 'no overage charges' is a relief, and switching plans anytime removes the fear of picking wrong. But I still haven't seen WHICH plan has the 'Why do they leave?' stuff — this table is just plus and minus signs without labels in front of me. There's more page below, let me finish reading before I judge."
Worked: The FAQ directly answers practical worries — hitting the event limit just pauses recording with no overage charges, and I can switch plans anytime with automatic prorating. That makes choosing a plan feel low-risk.
Action: scroll
Step 9/pricingSafety
Read: Bottom of the pricing FAQ: hitting the event limit just pauses recording with no overage charges, plans can be switched anytime with automatic proration, all data stays on Hetzner servers in Germany, and a DPA is available via email.
Thought aloud: „Okay, the FAQ actually answers the scary stuff — no surprise bills, I can downgrade whenever, and my readers' data never leaves the EU. As a blogger with European readers that genuinely matters. I've seen enough of the pricing page: the free plan includes the core features, including the engagement scoring I came for. Time to stop reading and see what 'Get started' actually looks like — if signup is quick I'd honestly try this."
Worked: The FAQ kills my billing anxiety — 'no overage charges', instant plan switching, and EU-only data storage with a DPA on request all make it feel safe to commit
Action: click
Step 10/auth/loginSafety
Read: Sign-up/login screen: 'Get started' — enter your email (plus a website field) and they send a login link, or sign in with Google. Notes: free plan, no credit card, 60 seconds, no data shared via Google.
Thought aloud: „Okay, so to actually see the engagement scoring and the 'why do they leave' stuff inside the tool I'd have to create an account — but this works by emailing me a login link, and I can't check an inbox right now. So this is as far as I can go without a real email. To be fair, the page itself is doing everything right: 'Free plan. No credit card. Takes 60 seconds' kills the signup anxiety, and 'we only use Google to verify your email, no data is shared' is a nice trust touch. Since I can't get past this gate, let me go back to the homepage and see if there's a demo, sample report, or docs I can poke at without an account — that would tell me if the insights are actually as simple as they claim."
Worked: 'Free plan. No credit card. Takes 60 seconds' plus 'No data is shared' makes starting feel genuinely low-risk
Action: click 5
Step 11/Capability 2/5Capability
Read: Back at the very top of the homepage — the hero: 'Tracking without the cookie banner', cookieless analytics for European sites, 'find out why they leave', built in Denmark, no credit card, works alongside Google Analytics.
Thought aloud: „Wait... didn't I just click Get started? And now I'm back up here at the top of the homepage — that felt like a loop. Okay, I've got maybe two clicks left in me. I still haven't actually seen HOW the 'why do they leave' thing works — like what the advice actually looks like on screen. And 'See how it works' is sitting right there in the hero. That's exactly the thing I came for."
Friction: Clicking 'Get started' landed me back at the top of the homepage instead of a signup or the tool itself — felt like I went in a circle
Worked: 'See how it works' is right there in the hero — a clearly labelled path to exactly the explanation I came for, no hunting required
Action: click 2
Step 12/Meaning
Read: Pain-point section: consent banners filter your data, visitor data leaves Europe (GDPR risk), and Google Analytics is too complex — 'you just want to know how many visitors you have.'
Thought aloud: „So 'See how it works' dropped me into this 'Sound familiar?' bit... and honestly, yeah, all three of these are me. Especially the last one — events, data streams, BigQuery — I just want to know who actually reads my posts. Okay, there's clearly more below this, let me read the actual 'how it works' explanation before I decide anything."
Worked: The pain points speak my language — 'you just want to know how many visitors you have' nails exactly why GA overwhelms me; feels like they actually get a novice content creator
Read: A page about cookieless analytics for European websites. The headline says 'Tracking without the cookie banner' and emphasizes no cookie banner needed, EU data residency, and works with Google Analytics. There's a prominent 'Add to your site free' button and several 'Get started' links below.
Thought aloud: „Okay, so this is an analytics tool — specifically for tracking website visitors without the cookie banner hassle. That's actually interesting because cookie banners are annoying. The eye-tracking said I'd notice the headline and the 'Add to your site free' button first, and yeah, that makes sense — those are the two things that grab me. The headline is clear: cookieless + no banner. The button is the obvious action. But I'm here to understand how the 'Engagement quality scoring' and 'Why do they leave?' features work, and I need to see if they give me simple, actionable advice. I don't see those features mentioned yet on this first view. Let me scroll down and see what else is on this page before I jump into signing up."
Worked: The headline and opening value proposition are clear and direct — immediately tells me what the product does (cookieless analytics, no banner, EU data) and why it matters. The 'Add to your site free' button is prominent and removes friction by saying 'free' and 'no credit card'.
Action: scroll
Step 2/Meaning
Read: Analytics tool that tracks visitors without cookie banners. Explains problems with Google Analytics (consent filtering, GDPR data transfer, complexity) and promises to show why visitors leave and suggest improvements.
Thought aloud: „Okay, so this is clearly a GDPR-friendly analytics alternative. They're positioning themselves against Google Analytics. I can see several 'Get started' buttons and links, but I'm only 22% through the page. I should scroll down to see what features they actually offer and understand the 'Engagement quality scoring' and 'Why do they leave?' features — those are exactly what I came to test. Let me see the rest of the page first before clicking anything."
Worked: Clear problem statement: explains why I should care (consent banners filtering data, GDPR risk, complexity) and hints at their solution (simulate why they leave, suggest improvements, measure results)
Action: scroll
Step 3/
Read: I can see features like synthetic personas, AI suggestions for search snippets, before/after measurement, pageviews/visitors dashboard, no cookies needed, EU hosting, simple one-script setup, team access, trend comparison, and AI insights. There are multiple 'Get started' buttons and other action links visible.
Thought aloud: „Okay, so I've scrolled through and I'm seeing the main selling points — no cookies, EU-hosted, simple setup. But I still haven't really understood those two specific features I came to test: 'Engagement quality scoring' and 'Why do they leave?'. I see mentions of 'synthetic personas' and 'predict what makes visitors leave' which sounds like it could be the 'Why do they leave?' feature, but I'm not seeing clear labels for 'Engagement quality scoring'. Let me scroll down more to see if there's more detail about these features, or if I need to click into something to understand them better."
Action: scroll
Step 4/Meaning
Read: I can see more features now: WordPress plugin with one-click install, page change tracking with before/after analysis, engagement quality scoring (bounce/skim/engaged/gold), AI agent integration, and a simple 3-step setup process. There are several 'Get started' buttons and other action links visible.
Thought aloud: „Okay, I'm seeing the engagement quality scoring feature mentioned here — that's one of the things I wanted to understand. It says 'Every session is bucketed as bounce, skim, engaged, or gold based on time and scroll depth' and 'Find your most valuable pages — and the gold-traffic ones with weak content.' That sounds useful, but I still haven't actually *seen* what this looks like in practice or how to use it. I also saw 'Why do they leave?' mentioned in my task, but I haven't found that feature yet. Let me scroll down more to see if there's more info, or if I should start exploring the actual tool."
Worked: The engagement quality scoring explanation is clear and directly addresses my need — it explains the four session types (bounce/skim/engaged/gold) and why it matters (finding valuable pages vs. weak content). This is actionable language.
Action: scroll
Step 5/
Read: Pricing section with three tiers (Free, Starter, Growth) and a call-to-action at the bottom saying 'See what you've been missing' with messaging about cookie banners. I'm 86% down the page with more content below.
Thought aloud: „I've been scrolling through this landing page and I can see pricing tiers now, but I still haven't found clear explanations of the two features I'm supposed to test: 'Engagement quality scoring' and 'Why do they leave?'. I saw 'engagement quality scoring' mentioned earlier, but I need to actually understand HOW it works and if it gives me actionable advice. Let me scroll down more to see if there's a demo, feature breakdown, or more detailed explanation below this pricing section."
Action: scroll
Step 6/Meaning
Read: Bottom of landing page showing main value prop: cookie-free analytics, GDPR-friendly, no credit card needed. Multiple 'Get started' buttons visible. I've scrolled through the whole page but haven't found detailed explanations of the two features I need to understand: 'Engagement quality scoring' and 'Why do they leave?'
Thought aloud: „I've been scrolling through this landing page for a while now and I'm at the bottom. I can see the pricing tiers and general features, but I haven't actually found clear, simple explanations of how 'Engagement quality scoring' works or what 'Why do they leave?' tells me. These are the exact things I wanted to understand as a content creator. I think I need to actually get into the tool or find a demo/documentation. Let me try 'See how it works' — that might show me a walkthrough of these specific features."
Worked: The landing page clearly explains the main value prop (no cookies, GDPR-friendly, simple) and has multiple entry points to get started
Action: click 2
Step 7/
Read: I'm on the landing page seeing the main value propositions: no consent banners needed, GDPR-compliant, EU-hosted, simpler than Google Analytics. I can see several 'Get started' buttons below, but I'm still only 13% down the page and haven't found detailed explanations of the specific features I came to learn about — 'Engagement quality scoring' and 'Why do they leave?'
Thought aloud: „I've been clicking around and scrolling, but I haven't actually found the detailed feature explanations yet. The landing page keeps talking about the general benefits, but I need to understand HOW the engagement scoring and leave-reasons features actually work. Should I keep scrolling to see if there's more detail below, or should I click on 'See how it works' to get into the actual product? Let me try 'See how it works' — that sounds like it might show me the features in action."
Action: click 2
Step 8/
Read: I'm on the landing page showing problems with Google Analytics — consent banners, data leaving Europe, complexity. I can see several 'Get started' buttons below and a 'Compare all features' link. I'm only 13% down the page.
Thought aloud: „I've been jumping around clicking things without really understanding what I'm looking for. I came here to understand the 'Engagement quality scoring' and 'Why do they leave?' features — those were mentioned earlier. But I keep scrolling past them or clicking without reading. Let me actually scroll down more carefully and find where those features are explained in detail, instead of just clicking 'Get started' buttons."
Action: scroll
Step 9/
Read: I'm seeing two key features now: 'Why do they leave?' which uses AI personas to predict why visitors abandon pages, and 'Optimise' which suggests concrete improvements. There's also basic analytics (pageviews, visitors, sources) and a no-cookies selling point. Multiple 'Get started' buttons below.
Thought aloud: „Okay, so THIS is what I came to understand — the 'Why do they leave?' feature and how it actually works. It says synthetic personas built from search queries walk through pages and predict what makes people leave. That's... actually interesting and concrete. But I'm still not 100% clear on how the 'Engagement quality scoring' fits in — is that the same thing, or different? I've been scrolling for a while and jumping around. Let me scroll down more to see if there's a clearer breakdown of features, or if I should just try clicking 'See how it works' to get a demo or detailed explanation."
Action: scroll
Step 10/
Read: I'm at 56% down the landing page. I can see feature descriptions now — including 'Engagement quality scoring' which is one of my key interests. It explains that sessions are bucketed as bounce, skim, engaged, or gold based on time and scroll depth. There's also 'Why do they leave?' implied in the AI agent integration section. I see multiple 'Get started' buttons below and a 'Compare all features' link.
Thought aloud: „Okay, I'm seeing the engagement quality scoring feature described here — bounce, skim, engaged, gold based on time and scroll. That's useful, but I still don't have a clear picture of HOW it actually helps me improve my content. And I haven't really understood the 'Why do they leave?' feature in detail yet. I've been bouncing around for a while. Let me scroll down a bit more to see if there's more detail, or if I should just click 'Compare all features' to get a clearer breakdown. I'm running low on patience here — I need to either find the detailed explanations or decide this tool might not be for me."
Action: click 6
Step 11/pricing
Read: A pricing page with four tiers (Free, Starter, Growth, Scale) and a section comparing this tool to Google Analytics, Plausible, Fathom, and Matomo. I'm at the top of the page with more content below.
Thought aloud: „Wait, I'm on the pricing page now, but I came here to understand how the 'Engagement quality scoring' and 'Why do they leave?' features actually work — not to buy. I've been jumping around a lot and clicking 'Get started' buttons without really learning what I need. The pricing page isn't going to explain those features in detail. I should scroll down to see if there's more info on this page, or I need to go back and find a proper feature explanation or documentation page. Let me scroll down first to see what else is here."
Action: scroll
Step 12/pricing
Read: I'm on the pricing page showing three tiers (50/mo, 200/mo, Unlimited) with feature comparisons and FAQs below. I'm 64% down the page with more content below.
Thought aloud: „I keep ending up on the pricing page, but that's not what I came for. I need to understand HOW the 'Engagement quality scoring' and 'Why do they leave?' features actually work — not just see that they exist or how much they cost. The landing page had brief mentions but no real explanation. Let me scroll down here to see if there's more detail about these features in the FAQ or elsewhere on this pricing page, or I need to find a different section — maybe a demo or documentation?"
Action: scroll
Notes
*First glance (~3 sec): where the eye instinctively lands. Says nothing about comprehension — the think-aloud part measures that.
**Note — the two instruments are coupled here. The ranking next to the heatmap was given to the personas as their first impression, so they sense the page in human order rather than the page's code order. This means that when the think-aloud part mentions one of the elements from that ranking, it is not independent confirmation — the persona was told. Only the first turn is guided by that ranking; everything after it is the persona's own.
*** There is no universal target for how much of the first glance should land on an action — compare with your own page before and after a change.