Get started

Introduction

Server-side ad-event tracking with identity resolution and multi-destination delivery.

Pivolio collects events from your site or backend, resolves them to a real person, and delivers conversions to your ad platforms’ Conversions APIs — server-side, so they survive ad-blockers, cookie expiry, and Safari’s tracking prevention.

Browser pixels are increasingly unreliable. A conversion that never reaches Meta or Google is one those platforms can’t optimize against, so your campaigns end up bidding on worse data than you actually have. Pivolio moves that delivery to the server, where it isn’t subject to the browser’s restrictions.

How it fits together

your site ──▶ Pivolio collector ──▶ enricher ──▶ dispatcher ──▶ ad platforms
   (SDK)         (write key)         (identity,     (Conversions APIs)
                                      attribution,
                                      PII hashing)

Events arrive authenticated by a write key, get resolved against an identity graph, and are delivered to each destination you’ve connected. Everything is recorded for reporting whether or not delivery succeeds.

Quickstart

Install the SDK and send your first event.

How Pivolio works

What happens to an event at each stage of the pipeline.

Destinations

Connect Meta, Google Ads, TikTok, or Reddit.

SDKs

Browser, React, Next.js, and Shopify.

Two API surfaces

Pivolio exposes two kinds of endpoints, each authenticated differently:

  • Ingestion — send events from a browser or server using a workspace write key (the X-Write-Key header). Write keys can only ingest events, so they’re safe to ship in client-side code.
  • Management — workspaces, destinations, reporting, and account endpoints authenticate with the dashboard session cookie.

See Authentication for details.

Two things worth knowing up front

Pivolio tracks nine ad platforms but delivers to four. Click IDs from Google, Microsoft, Meta, TikTok, LinkedIn, Pinterest, Reddit, Snapchat and X are all captured and used for attribution. Server-side delivery exists for Meta, Google Ads, TikTok and Reddit. See Destinations.

Delivery is the paid part. A workspace without a subscription still tracks, stores and reports every event — it just doesn’t forward them to ad platforms. Nothing is lost while you’re unsubscribed, and connecting a plan later starts delivery from that point on. See Billing.