Server-side capture that ad blockers can't touch
The browser pixel is the most fragile link in your stack. Pivolio moves the conversion event to your server, so it fires whether or not the visitor blocks scripts, opts out of ATT, or clears cookies — recovering the conversions your pixel silently drops.
The pixel was built for a web that no longer exists
Client-side pixels depend on a script loading in the visitor's browser, a third-party cookie surviving, and the platform being allowed to track. In 2026, all three assumptions routinely fail — and each failure is a conversion your ad platforms never learn from.
Roughly a third of users run ad blockers that strip the pixel before it fires. Safari's Intelligent Tracking Prevention truncates first-party cookies to seven days, detaching returning customers from the click that drove them. And iOS App Tracking Transparency lets most users opt out of tracking entirely.
The result is a shrinking, biased sample of your real customers — and because ad algorithms optimize toward whatever they can measure, that bias compounds with every optimization cycle.
Three steps from request to captured event
Event fires server-side
Your backend calls the SDK on a real conversion — a purchase, lead, or signup — with no reliance on the browser.
Signals attached
Click IDs, hashed email, IP, and device data ride along so the event can be resolved and scored downstream.
Stored & streamed
The raw event lands in your account and appears in the live debugger within milliseconds.
Watch every event land in real time
A streaming feed shows each captured conversion the moment it fires — with its identity, platform, and delivery status — so you can confirm tracking is working before you trust a single report.
- Live streaming event feed
- Per-event identity and status
- Filter by platform or time window
Four lines in your backend
Install the SDK, initialize with your key, and track a conversion with the signals needed to resolve and score it. That is the entire integration — no tag manager, no data-layer archaeology.
- Backend and edge runtimes
- Simple HTTP endpoint fallback
- Custom events, values, and metadata
import { init, track } from '@pivolio/browser'
init({ writeKey: 'wk_live_9f2a…' })
track('order_completed', {
properties: { revenue: 129.0, currency: 'USD' },
})Everything the pixel can't guarantee
No client dependency
Events don't rely on JavaScript loading, so nothing is lost to blockers or slow pages.
Immune to ITP & ATT
Cookie truncation and app-tracking opt-outs no longer sever conversions from their source.
Deduplicated with your pixel
Run alongside an existing pixel — matched events are merged so platforms never double-count.
Backend & edge SDKs
Fire from any server runtime or the edge, close to where your conversions actually happen.
Custom events & values
Track any conversion with custom values, currencies, and metadata mapped per platform.
Full data ownership
Raw events are stored in your account and exportable at any time — no lock-in.