Server-Side Pixels
Send conversion events to ad platforms via server-side CAPI
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, and Pinterest.
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 PlatformThis 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)
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
- Go to Site Settings → Pixels
- Click Add Pixel
- Select the provider (Google Ads, Meta, TikTok, etc.)
- Enter your provider-specific configuration (e.g., Pixel ID, Access Token)
- Configure event mappings and daily caps
- Enable the pixel
API Access
Pixel management is available via the server API:
GET /sites/:siteId/pixels— List all configured pixelsPOST /sites/:siteId/pixels— Create a new pixelPUT /sites/:siteId/pixels/:id— Update a pixelDELETE /sites/:siteId/pixels/:id— Delete a pixel