Server-Side Pixels

Server-Side Pixels (CAPI — Conversions API) lets you send conversion events directly from your server to advertising platforms including Google Ads, Meta (Facebook), TikTok, Snapchat, Pinterest, and OpenAI ChatGPT Ads.

How It Works

Instead of relying on client-side pixel scripts (which can be blocked by ad blockers), server-side pixels send conversion events directly from your backend:

User Action → Your Server → BuddyStat CAPI → Ad Platform

This provides more reliable conversion tracking and bypasses browser-level tracking restrictions.

Key Features

Multi-Provider Support

Send events to multiple ad platforms simultaneously:

• Google Ads (Google Ads API)
• Meta / Facebook (Conversions API)
• TikTok (Events API)
• Snapchat (Conversions API)
• Pinterest (Conversions API)
• OpenAI ChatGPT Ads (Conversions API) — see OpenAI ChatGPT Ads below

OpenAI ChatGPT Ads (dual-layer)

OpenAI is the one provider that uses a dual-layer approach: a client-side measurement pixel (window.oaiq) plus the server-side CAPI. This is required because the __oppref click-id cookie only exists in the browser — the server cannot read it.

How it works:

1. BuddyStat's tracking script detects the measurement pixel on your site.
2. For each event it generates one shared event_id, dispatches the event to window.oaiq, and relays the event_id + the URL-decoded __oppref to the backend (payload.openai).
3. The server sends the same event_id (plus oppref) to POST https://bzr.openai.com/v1/events — OpenAI deduplicates the browser + server deliveries by event_id.

PII (email, phone, external ID) is SHA-256 hashed (lowercase+trim for email, E.164 for phone) before sending.

To set it up, add an OpenAI ChatGPT Ads pixel on the Pixels page with your OpenAI measurement API key. Load the OpenAI measurement pixel on your site (obs.openaicdn.net/obs-pixel.min.js); BuddyStat's script will detect it automatically.

AES-256 Encryption

Customer data is encrypted using AES-256 encryption before being sent to ad platforms, ensuring PII protection while maintaining match quality for ad optimization.

Event Deduplication

Events are automatically deduplicated using event IDs to prevent double-counting when both client-side and server-side tracking are active for the same conversion.

Automatic Fan-Out

A single server-side event can be automatically fanned out to multiple ad platforms. Configure which platforms receive each event type.

Test Mode

Each pixel can be placed in test mode, allowing you to verify event delivery without affecting ad platform optimization algorithms or campaign reporting.

Daily Cap Enforcement

Configure daily event caps per pixel to control spend and prevent unexpected over-delivery of conversion events to ad platforms.

Setting Up a Pixel

1. Go to Site Settings → Pixels
2. Click Add Pixel
3. Select the provider (Google Ads, Meta, TikTok, etc.)
4. Enter your provider-specific configuration (e.g., Pixel ID, Access Token)
5. Configure event mappings and daily caps
6. Enable the pixel

API Access

Pixel management is available via the server API:

• GET /sites/:siteId/pixels — List all configured pixels
• POST /sites/:siteId/pixels — Create a new pixel
• PUT /sites/:siteId/pixels/:id — Update a pixel
• DELETE /sites/:siteId/pixels/:id — Delete a pixel