Skip to main content
Server-side tracking means your conversions are sent from a trusted backend (SignalBridge) to ad platforms using their official server APIs.

​
Why it matters

  • Higher reliability than browser pixels
  • Works when pixels are blocked
  • Better match quality when you provide user_data

​
How SignalBridge sends events

1

Capture

Your site calls sb_track(...) and loads pixel.js.
2

Ingest

SignalBridge receives the event and validates required fields.
3

Enrich

We attach attribution fields (UTMs / click IDs) when present.
4

Forward

SignalBridge forwards via platform APIs when browser pixels are blocked.

​
Deduplication

To avoid double-counting, use a stable event_id on conversion events. Read: Deduplication.