Conversions

Conversions send your captured leads and purchase events to ad platforms as server-side conversion events — the kind that survive ad blockers, iOS privacy, and cookie deletion.

Without server-side conversions, your ad platforms only see the events that fire from a browser pixel. Roughly 30-50% of those get blocked by ad blockers, iOS Safari’s privacy features, or aggressive browser cookie clearing.

PartialLeads fixes that by sending the same events server-to-server. Your ad campaigns see real outcomes (purchases, completed leads, booked calls), not just page loads.

The three platforms

Send purchase, lead, and booking events to Facebook + Instagram via the Meta Conversion API. Available on all plans.

Why server-side beats browser pixels

Browser pixels are the original way conversion tracking worked: a JavaScript snippet on your thank-you page sends an event to the ad platform when it loads. Simple, fragile, increasingly broken.

What goes wrong:

Ad blockers (uBlock, AdBlock Plus, Brave’s built-in shields) actively prevent pixels from loading
iOS Safari’s Intelligent Tracking Prevention kills the cookies pixels rely on
Chrome’s third-party cookie deprecation is gradually removing the same cookies
Browser back/forward navigation sometimes skips pixel fires entirely

Server-side conversion APIs avoid all of this. PartialLeads receives your purchase events directly from Shopify (or Stripe, or your CRM, or your custom platform), then forwards them to Meta / Google / Pinterest using server-to-server HTTP requests — no browser involvement at all.

How it works at a glance

A purchase or lead happens on your site (or your CRM, or your booking platform)
PartialLeads receives the event server-side via webhook from your integrated platform
We match the event to a visitor session — using email, phone, visitor ID cookie, and identity graph
We fire the matched event to your configured ad platforms via their server APIs
Your ad campaigns optimize against real outcomes, not pixel fires

The matched-session step is the load-bearing part. It’s why PartialLeads connects to your integration (Shopify/WC/GHL/Stripe) AND your ad platform — we need both ends to attribute the purchase back to the original click.

A typical Conversions setup

Most customers configure two or three of these, depending on where they advertise:

Run Meta ads? → set up Meta
Run Google ads? → set up Google
Run Pinterest ads? → set up Pinterest
Run on a network not listed here? → contact support — TikTok, LinkedIn, and Snap CAPIs are on the roadmap

You can configure multiple platforms simultaneously. PartialLeads dispatches each event to every configured destination in parallel.

Pick a platform to configure: Meta · Google · Pinterest.

Webhook Meta