> ## Documentation Index
> Fetch the complete documentation index at: https://docs.signalbridgedata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Server-side tracking

> Send conversions to platforms via official APIs

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

<Steps>
  <Step title="Capture">
    Your site calls `sb_track(...)` and loads `pixel.js`.
  </Step>

  <Step title="Ingest">
    SignalBridge receives the event and validates required fields.
  </Step>

  <Step title="Enrich">
    We attach attribution fields (UTMs / click IDs) when present.
  </Step>

  <Step title="Forward">
    SignalBridge forwards via platform APIs when browser pixels are blocked.
  </Step>
</Steps>

## Deduplication

To avoid double-counting, use a stable `event_id` on conversion events. Read: [Deduplication](/concepts/deduplication).