Server-Side Signal Recovery

Overview

Modern web browsers increasingly block or limit client-side tracking pixels through ad blockers, Intelligent Tracking Prevention (ITP), Enhanced Tracking Protection, and privacy-focused browser defaults. This means a significant portion of conversions that happen on your website are never reported back to ad platforms.

Vendo’s server-side conversion sync addresses this by sending conversion data directly from your data warehouse to ad platforms, bypassing client-side limitations entirely.

The Problem: Pixel-Only Tracking Gaps

Client-side pixels fail to capture conversions in several scenarios:

Ad blockers — 30-40% of desktop users run ad blockers that prevent pixel fires
ITP (Safari) — First-party cookies limited to 7 days, third-party cookies blocked entirely
ETP (Firefox) — Known trackers blocked by default
Network issues — Pixels fail on slow connections, page abandonment before pixel fires
Consent management — Users who decline tracking cookies generate no pixel data
Cross-device journeys — Conversions on a different device than the click are lost

Industry research estimates that pixel-only tracking misses 30-50% of actual conversions, depending on your audience demographics, geography, and device mix.

How Server-Side Recovery Works

Vendo’s approach works in three steps:

1. Collect conversion data server-side

When a conversion happens (purchase, signup, form submission), the event is captured by your backend system and stored in your data warehouse (BigQuery). This happens regardless of whether a pixel fired.

2. Match conversions to ad clicks

Vendo’s attribution engine matches each conversion to the original ad click using:

Click IDs (gclid, fbclid, msclkid, ttclid, etc.) captured at landing
First-party cookies that persist the click ID across sessions
Identity resolution linking anonymous sessions to known users

3. Sync to ad platforms

Matched conversions are sent to each ad platform via their server-side conversion APIs:

Google Ads Enhanced Conversions
Meta Conversions API (CAPI)
TikTok Events API
Snap Conversions API
Microsoft UET
LinkedIn Conversions API

Recovery Rate Factors

The actual signal recovery rate depends on several factors:

Factor	Impact
Audience demographics	Younger, tech-savvy audiences have higher ad blocker usage
Geography	European audiences tend to decline cookies more often (GDPR)
Device mix	Mobile apps have fewer ad blocker issues than desktop web
Purchase cycle	Longer cycles = more cross-device conversions lost
Click ID persistence	Better first-party cookie management = higher match rates

Typical recovery rates range from 30-50% more conversions reported compared to pixel-only tracking, with some verticals seeing higher or lower rates.

Deduplication

Vendo deduplicates conversions before sending them to ad platforms. If both the pixel and server-side sync capture the same conversion, the ad platform receives it only once. This is handled through:

Transaction ID matching (order IDs, event IDs)
Timestamp-based deduplication windows
Platform-specific dedup parameters (e.g., order_id for Google, event_id for Meta)

Getting Started

Connect your data source — Set up a source for your conversion data (Shopify, Stripe, or custom events)
Configure attribution — Map click parameters and set lookback windows
Add a conversion destination — Connect Google Ads, Meta Ads, or other platforms
Verify delivery — Check job logs to confirm conversions are being sent

For setup guides, see: