Skip to content

Compare

A Google Analytics alternative without cookies.

How Pulsora compares with Google Analytics 4, Plausible and Fathom on cookies, visitor counting, revenue and price. Every competitor cell comes from that vendor’s own pages, listed below the table.

CriterionPulsoraGoogle Analytics 4PlausibleFathom
CookiesNoneFirst-party _ga and _ga_<container-id>, kept for 2 years by defaultNoneNo analytics cookies
How unique visitors are countedHash of IP, user agent and site with a per-site salt, rotated every 24 hours by default (up to 30 days)The _ga cookieHash with a salt that is rotated and deleted every 24 hoursSHA-256 hash with a salt rotated daily at midnight UTC
RevenueRevenue events from your payment webhook, sent server-side with a secret tokenA purchase event with value, currency and transaction_idMonetary values on custom events, on the Business planEvent values in cents, sent with trackEvent
Starting price$6.99 / month for 10K eventsFree$9 / month for 10k pageviews$15 / month for 100,000 pageviews
Free trial14 days, no cardNot needed, it is free30 days, no card7 days, card required

Last checked 2026-11-03. Spot something out of date? Tell us.

Sources

When to choose

Pick the tool that fits the question.

pulsora

Choose Pulsora

You sell online and want revenue from your payment webhook next to the pages, sources and campaigns of each visit.

ga4

Choose Google Analytics

You want a free tool, already measure purchases with gtag ecommerce events, and are fine with its cookies.

plausible

Choose Plausible

You want simple cookieless numbers, or to host the tool yourself with the free Community Edition.

fathom

Choose Fathom

You want a cookieless dashboard, and event values in cents are enough for tracking purchases.

Switching

Move over in an afternoon.

Run both side by side for a couple of weeks, compare the numbers, then remove gtag.

gtag → pulsora
// before
gtag('event', 'sign_up', { method: 'email' })

// after
pulsora.event('signup', { method: 'email' })
  1. 01
    Add your siteCreate the site in Pulsora and copy its public token.
  2. 02
    Paste the script next to gtagBoth run side by side. Pulsora sets no cookies, so it adds nothing for visitors to accept.
  3. 03
    Map your eventsReplace gtag event calls with pulsora.event(), passing the same properties as an object.
  4. 04
    Connect revenueFrom your payment webhook, post purchases to the ingest API with your secret token and the session ID from checkout.
  5. 05
    Remove gtagOnce the numbers line up, drop the Google tag and the _ga cookies it sets.

Run it next to GA for 14 days.