Conversions send server-side to Meta Conversions API, Google's Data Manager API, TikTok's Events API, Microsoft and Snap today, alongside the standard browser pixel on each network — with LinkedIn, Pinterest and Reddit senders joining the same way once those channels go live, not before. Server-side conversion tracking survives what browser pixels increasingly don't: ad blockers, Safari's tracking prevention, and iOS's app tracking limits. One sender per platform shares event IDs between the browser and server events, so a purchase that fires both ways is deduplicated and never counted twice.
Ads and Pixels / Conversion Tracking
Conversion tracking that's verified before you ever launch.
Conversion tracking only matters if it's actually firing, so Ads and Pixels checks that before a conversion-goal campaign is allowed to go live, not after you've already spent the budget finding out. A test event has to reach the vault and the platform first. No exceptions, no "launch now, fix tracking later."
One place. Every screen.Explore below
01 /
Server-side, not just a browser pixel
02 /
One collector, on your own domain
The tracking collector runs on a neutral first-party subdomain of the client's own site — never on adsandpixels.com, and never anywhere with "ads" or "pixel" in the hostname, because ad blockers match those strings by name. The client adds one CNAME record and conversion tracking is live from their own domain, first-party, not a third party's.
03 /
Everything that touches revenue, connected
Google Tag Manager gets full tag install and publish once the client grants publish rights, in one onboarding tap, not by hand-editing container code. GA4 properties, streams and key events are created by API. Search Console gets its sitemap submitted automatically once ownership is verified. Revenue truth comes straight from Shopify, WooCommerce and Stripe, so a platform-reported "purchase" can be checked against what was actually charged. CRM and call systems — HubSpot, GoHighLevel, Salesforce, CallRail, AI Phone 360 — feed closed deals back to the networks, so they optimize toward paying customers instead of form fills that never went anywhere.
04 /
Offline and call conversions count too
Not every sale happens on a website. A call that turns into a booked job, a store visit that ends in a purchase, or a deal that closes three weeks after the lead came in all get sent back to the networks the same way a checkout event does. CallRail and AI Phone 360 report qualifying calls; HubSpot, GoHighLevel and Salesforce report a deal moving to "closed won"; a CSV or a direct CRM stage change covers point-of-sale systems that don't have an API yet. Each of these becomes an offline conversion upload or a matching server-side event, tied back to the same visitor and ad through the identifiers already stored on their visit. A network optimizing on "leads" alone will happily fill your funnel with leads that never buy; feeding it what actually closed is the only way its own bidding starts favoring the customers who pay.
05 /
Set up once per client, not once per network
Every server-side sender, every pixel and every offline-conversion connection is configured once, in the same onboarding flow, and applies to every network that client has connected — not a separate setup screen per platform. Add a sixth network to a client later and it picks up the same events and the same test-event verification step automatically, instead of starting from zero.
06 /
Consent, honored automatically
Every event carries its consent state. Google Consent Mode v2 signals are sent on every hit, and Global Privacy Control is honored automatically — conversion tracking never fires for a visitor who opted out, and that opt-out is recorded, not just assumed.
07 /
What "verified" actually means here
A conversion event counts as verified when a real test event has reached both the vault and the network it's meant to report to, matched on the same event ID, with a value and currency if the goal needs one. Until that happens, the campaign launch button for a conversion goal stays disabled — the app tells you exactly which event is missing, not just that something's wrong.
A little more clarity
Frequently asked questions
Real answers before you make a decision.
Do I need a developer to install conversion tracking?
No. Google Tag Manager, GA4 and the server-side senders are installed through the app once the client grants access in a guided onboarding step, not through manual container or code edits.
What's the difference between the pixel and the Conversions API?
The pixel fires from the visitor's browser and is increasingly blocked or limited by ad blockers, Safari and iOS. The Conversions API sends the same event from our server directly to the network, so it isn't affected by browser-side blocking. We send both, deduplicated with a shared event ID, so you get the fullest picture either method alone would miss.
Can a campaign launch before conversion tracking is verified?
Not for a conversion goal. Calls, leads, purchases, trials, installs, bookings, messages and store-visit goals all require a verified test event before Launch is available. Awareness and video-view goals, which don't optimize on a conversion event, only need creative, audience, budget and page tag in place.
Does this work if my client uses Shopify or WooCommerce instead of a custom site?
Yes. Shopify connects through its GraphQL Admin API and WooCommerce through its own integration, so purchase events and revenue truth flow in without custom development on the client's store.
Is conversion tracking set up per network, or once for the whole account?
Once, in a single onboarding flow — conversion tracking configured for a client applies to every network that client has connected, so adding a network later doesn't mean repeating the setup.
What happens if a visitor declines cookies or opts out under Global Privacy Control?
Nothing fires for that visitor beyond what their consent state allows, and that choice is recorded on the visit itself, not just assumed from a missing cookie. Google Consent Mode v2 signals travel with every hit, so the network knows exactly what it's permitted to use before it receives anything.
Your next move
Get conversion tracking verified before you spend a dollar.
Connect your networks and your site, and see the test-event status for every conversion goal before you ever click Launch.