From session replays to fixes that matter

See which gaps in a client's traffic are real, and fix the few that matter first.

The app, with its menu down the side, showing one gap: on Safari 16, 1.7% of sessions add to cart, against 7.2% for everyone else. Its diagnosis: the Add to cart button never renders on Safari 16, found between choosing options and adding to cart, with three recordings to watch.
Built forEcommerce storesLead generation formsB2B demo funnels

Sound familiar?

You can see the drop. You can't see what to fix.

01

Too many replays, too little signal

A client site records thousands of sessions a week. Whichever few you happen to watch end up shaping the recommendation.

02

Insights split across tools

Event data and totals live in one place, session recordings in another. Each holds part of the story, so the bigger picture is hard to see. Data Drivven brings them together.

03

Hard to know what to fix first

There's always more to fix than time to fix it, and it's hard to tell which change would make the biggest difference. Data Drivven ranks each gap by the conversions it costs, so effort goes where it counts.

How it works

From noise to the few fixes worth making

01 · Noise set aside

Only the gaps that are real

Highlights what matters most in a client's traffic, and what's not worth looking at.

Add-to-cart rate by traffic source, each with a verdict: three gaps marked The real deal, and Meta's 1.8-point gap marked Just noise.
  • Find a gap, then dig in. See where a device, source, campaign or landing page falls behind, then quickly cut it further, down to the funnel step and the sessions behind it.
  • Straight to what matters. Real gaps stand out and noise is marked as noise, so your time goes on the few worth fixing.
  • Quiet gaps say what they need. When a gap is too small to call, you see how many more sessions would settle it.
  • Staff and customers set aside. The client's own team and existing customers don't flatter the numbers.

02 · Drill in

Find the step where it breaks

  • Down to the step. Reach and step-to-step conversion for any segment, so you see the handoff where shoppers stop.
  • Side by side. Mobile against Desktop, one campaign against another, a browser against everyone else.
  • Flagged for you. The step where a segment falls away is marked, so you know where to look first.
  • Back to the ad. UTM tags, click IDs and search terms stay on each session, so a problem traces back to the campaign that sent it.
A store's funnel comparing Mobile with Desktop step by step. The last step is picked out: Mobile falls away before adding to cart.

03 · Why

The session replays that explain it

  • Findings open their replays. Watch the sessions behind a gap, not a random sample.
  • Closer to what visitors saw. Replays are repaired where common recorders slip, like a visitor opening a second tab or you skipping ahead, so the page looks the way it did for them.
  • Form behaviour by field. Where people paused, corrected or hit an error, without recording what they typed.
  • A written diagnosis. Top findings come with a short evidence card: what's happening, and which replays to watch.
Data Drivven's replay player on a mocked product page: a mobile shopper has tapped Add to cart without choosing a size, the size buttons show Choose a size, and the event list reads landed, clicked Next photo, scrolled, clicked Add to cart.

04 · What to change

What to fix, checked on the live pages

  • Principles from published research. Product pages, forms and calls to action are checked against conversion principles, each with the study behind it.
  • Sized by who it would reach. Each gap shows the share of shoppers a fix would meet, so the list starts with the biggest.
  • Page and visitors, side by side. What the site does, and what visitors did about it, so a gap on the page is backed by behaviour.
  • Handled steps aside. Principles the site already follows sit at the bottom, so the list stays short.
One principle opened from a store's checklist: give a sold-out product somewhere to go next, confirmed for 16% of shoppers, with what the site does, what visitors did, recordings to watch it happen, and what the research says. The rest of the list shows as blank blocks.

05 · Proof for the client

Show the client it worked

Log each change to the site, ads or tracking, and compare conversion before and after on the same funnel, once there's enough traffic either side to call it.

One snippet

Pasted once, through Tag Manager or the site's head. It waits for the page, so the page loads first.

Typing masked

Form fields are masked in the browser before anything is sent.

Consent ready

Strict mode records nothing until the visitor agrees.

No ad platforms

Recordings go to Data Drivven only, never to an ad platform.

Built from real-world use

Made by a practitioner, on live sites

Data Drivven was born out of wanting to understand what visitors were really doing across the sites its founder, Scott Buckland, works on: data you can dig into, statistics you can trust, and evidence of what actually happened, in one place.

Scott has helped businesses grow online since 2001, including four years leading digital marketing at Verizon Connect.

More about Scott →

"Scott is a big believer in letting the data guide our decisions, and instills a rigorous culture of test & learn within his team."

Jay Jaffin, CMO, Verizon Connect (at the time)

How it starts

Start with one

  1. 01

    Request a demo

    We show your team the gaps it finds, the diagnosis behind each one, and the replays that show it.

  2. 02

    Add one snippet

    Pick a client site and paste it once, through Tag Manager or the site's head. We check the site first, and set up the funnel with you.

  3. 03

    14 days free

    Findings fill from the first day of traffic. After 14 days, look at what it found and decide whether to carry on.

Request a demo

FAQ

Questions agencies ask first

What do we need from the client?

Access to their Tag Manager, or someone who can paste one short snippet into the site's head. Nothing else on their site changes.

Will it slow the site down?

The snippet is deferred, so the page loads first.

What about privacy and consent?

Form fields are masked in the browser before anything is sent, and nothing is read from a field unless it has been declared for that site. In strict consent mode, nothing is recorded until the visitor agrees.

How much traffic does a site need?

There's no fixed minimum. When a gap is too small to call, Data Drivven says so and shows how many sessions it would take.

Who sees the findings?

Your team, behind an email login. The client sees what you choose to share with them.

What happens after the 14 days?

We go through what it found together, and you decide whether to keep it running.

Get started

See it before anything goes on a client's site

Tell us your website. Here's what happens next.

  1. 01
    Within one business day

    Scott emails you to find a time.

  2. 02
    The demo

    A walk through it with your team: what it finds, and how you'd use it on a client's site.

  3. 03
    If it fits

    Pick a client site, add one snippet and get 14 days free.

Request a demo

Takes a minute. No obligation.