Skip to content

First-party data collection

Tracking that tells you when it is wrong

A lightweight first-party pixel and a server Events API feed one deduplicated stream — and an events manager shows what arrived, what was duplicated and what is missing.

  • Pixel and SDK: track, identify, page, consent
  • Server events with secret keys
  • Duplicates removed by event and order ID
Illustrative — sample data

Collection capabilities

A first-party pixel

One script tag or a Google Tag Manager template. Sessions, sources, click IDs and commerce events are recorded and linked to real store orders.

  • Reads common data-layer formats, including GA4 and Enhanced Ecommerce
  • Allowed-domain list and per-workspace public key

Server Events API

Send purchases, leads and custom events from your server with a secret key. A purchase from the server becomes a verified order.

Consent built in

Per-workspace consent policy: consent required, Google Consent Mode, or Global Privacy Control respected.

An events manager

Counts per event, a live log, an event inspector, and lists of missing, broken and duplicate events, with delivery delay per source.

Counted once, whatever the path

A purchase reported by the browser, the server and the store webhook becomes one order and one conversion.

Suspicious purchases held back

A browser-only purchase enters revenue only after plausibility checks; otherwise it is quarantined for review instead of inflating results.

Know before you buy

What to know

  • A browser pixel cannot tell a typed URL from a session that lost its tags, so sessions without evidence are recorded as unknown — never as direct.
  • Browser-only purchases stay "unverified" until a store or server record confirms them.
  • Mobile app SDKs are not available.

Questions, answered plainly

Will the pixel slow down my site?

The script is small, loads asynchronously and is served with caching headers that still let updates through.

Can I use it with Google Tag Manager?

Yes. Install it as a custom tag; the pixel reads purchase events from the data layer formats most stores already push.

Do I need server events?

They are optional, but they make purchases verified and recover conversions that ad blockers or closed tabs would lose.

See your own numbers, labelled honestly

Start a free trial and connect a store and an ad account, or book a walkthrough with our team.