mrkr vs FullStory.
FullStory is replay built for enterprises, sold by a salesperson, and it needs consent before it records. mrkr is replay bundled into analytics at a published price, cookieless by default.
In short
What is the difference between mrkr and FullStory?
FullStory is enterprise digital experience analytics built around session replay, with retroactive search across every recorded session and automatic frustration signals. mrkr is privacy-first web analytics with session replay included, tied to traffic source and revenue. FullStory is cookie-based and quoted by sales. mrkr is cookieless by default with published pricing.
These tools answer the same first question, what did this person do, and diverge immediately after. FullStory goes deeper into the session. mrkr goes wider around it, into where the visitor came from and whether the visit was worth anything.
Every replay carries its source.
A mrkr recording sits in the same dataset as the traffic, so it knows the referrer, campaign, landing page, country, and any revenue the session produced. That turns replay from a browsing exercise into a query.
Where mrkr is better.
You record everyone
FullStory sets cookies, so consent comes first. In its default cookieless mode mrkr stores nothing persistent on the device.
The price is on the website
Start at $1 for 14 days, see the ceiling, upgrade without a procurement cycle.
One bill, one dataset
Replay and analytics together, so there are no two session counts to reconcile.
It is light
Under 6 kB, with replay capture opt-in per site rather than always on.
Compared
Side by side.
| Feature | mrkr | FullStory |
|---|---|---|
| Category | Privacy analytics with replay | Digital experience analytics |
| Session replay | On every paid plan | Yes |
| Heatmaps | No | Yes |
| Funnels | Yes | Yes |
| Saved cohorts | No | Segments and retention reporting |
| Revenue attribution | Yes | Via conversion and revenue events |
| Cookieless | By default (optional cookie mode) | No |
| Free plan | No, $1 for 14 days | Trial and limited tiers, subject to change |
| Entry paid price | $5/mo, 100K pageviews, session replay included | Quoted by sales, Packaged by session volume, quoted per account |
| Retroactive search across all sessions | No | Yes |
| Rage clicks and frustration signals | No | Yes |
| Replay filtered by traffic source and campaign | Yes | Only with your own instrumentation |
| Published pricing | Yes | No, quoted per account |
| Consent banner in the EU | Not in the default cookieless mode | Yes |
| Start without talking to sales | Yes | No |
FullStory details checked against the vendor's own pricing and feature pages on 2026-08-24. Where a vendor does not publish a fixed list price, this table says how they charge rather than guessing a number. Vendors change packaging often, so confirm before you buy.
Live demo
Watch a real replay. The live demo includes recorded sessions you can play back, filter, and scrub. No signup, no card, no sales call.
Open the live demoWhere FullStory is genuinely better.
Search across every session
Query every session retroactively, even ones recorded before you thought to ask. mrkr cannot.
Automatic frustration signals
Rage, dead, and error clicks surfaced without configuration, so interesting sessions find you.
Enterprise depth
Governance, roles, procurement, account management. mrkr is self-serve with a support inbox.
Scale of recording
Built to index very large session volumes. mrkr replay draws on your event allowance.
FAQ
Is mrkr a FullStory replacement?
For teams who want to watch sessions and understand where traffic came from, yes. For teams whose workflow depends on searching retroactively across every session ever recorded, no. That search index is FullStory's core asset and mrkr does not have an equivalent.
How much does FullStory cost?
FullStory is sold through a sales conversation rather than a published list price, packaged by session volume. That is a real difference in itself: mrkr publishes its pricing, and you can start at $1 for 14 days without a call.
Does FullStory need a cookie banner?
Yes. FullStory identifies visitors with cookies, so in the EU, UK, and California you ask for consent before it records. mrkr in its default cookieless mode writes nothing persistent to the visitor device and records everyone. Turning on cookie mode for a site changes that and brings consent obligations with it.
Does mrkr detect rage clicks and dead clicks?
No. Automatic frustration signals are a FullStory strength and mrkr does not produce them. mrkr surfaces sessions by source, campaign, page, country, device, and revenue instead.
What does mrkr replay actually capture?
DOM mutations via rrweb, played back as a reconstruction of the page rather than a video. Text inputs are masked by default, recordings are stored in object storage and kept for 90 days on every plan.
Can I filter replays by traffic source?
Yes, and this is the main reason to pick mrkr for replay. Every recording carries the referrer, campaign, landing page, and any revenue the session produced, so you can watch only the sessions from a paid campaign that did not convert.
Start with one line of HTML.Your first visitors show up within a minute.