Integration · Meta Conversions API
Meta Conversions API, without the engineering project.
AdsPing forwards every website and Shopify event to Meta server-side — Purchase, Lead, AddToCart and more — with automatic event_id deduplication against your browser pixel and a match quality score you can actually verify.
Why server-side
The Meta browser pixel fires from the visitor's browser — which means ad blockers (10–20% of desktop traffic) and iOS Safari ITP silently kill a large share of your conversion signals before they reach Meta. Your campaigns still spend, but the algorithm optimizes on incomplete data and your reported ROAS understates reality.
Meta's own answer is the Conversions API: send events server-to-server so nothing in the browser can block them. But wiring CAPI yourself means access tokens, payload hashing, event_id dedup, retry logic, and monitoring — an engineering project most teams never finish properly.
AdsPing runs that pipeline for you. One script tag (or the Shopify app), an OAuth connection to your pixel, and every conversion flows server-side with the browser pixel running in parallel — deduplicated by a shared event_id, so nothing is double-counted.
How it works
- 01
Install pb.js or the Shopify app
One script tag in your site's <head>, or one-click install from the Shopify App Store. Standard events (PageView, AddToCart, Purchase, Lead) are auto-detected.
- 02
Connect your Meta pixel via OAuth
Authorize AdsPing with your Meta account and pick the pixel. No manual access token copying needed — though manual token setup is also supported.
- 03
Events flow server-side, deduplicated
AdsPing forwards each event to the Conversions API with SHA-256-hashed match parameters (email, phone, fbp, fbc, IP, user agent). The auto-injected browser pixel fires in parallel; Meta dedups by event_id.
- 04
Watch match quality climb
The dashboard shows per-event delivery status and an EMQ-style match quality score. AdsPing's identity graph backfills missing match parameters from past sessions to push the score higher.
What you get
Automatic browser-pixel injection
Configure Meta as a destination and AdsPing auto-injects the official browser pixel with the same event_id — one tag covers both channels with automatic deduplication.
Identity graph for higher EMQ
Every source (website, Shopify, CRM) contributes emails, phones, fbp/fbc, IP, and user agent to a per-visitor identity pool. Every CAPI send backfills missing match parameters — higher Event Match Quality, better attribution.
First-party custom domain
Serve the script and collect events through track.yourbrand.com so blocker lists that target third-party tracking domains never see AdsPing.
Delivery health + proactive alerts
Per-pixel delivery status, failure reasons, and dedup coverage in real time. If a token expires or delivery degrades, you get an email with the fix link within minutes.
Shopify checkout coverage
Shopify's checkout runs on checkout.shopify.com where scripts can't reach. The AdsPing Shopify app captures Purchase and Refund via webhooks — server-side, always.
CRM feedback loop
Connect Salesforce, HubSpot, Zoho, or Pipedrive and send qualified-lead and won-deal events back to Meta — so the algorithm optimizes for revenue, not just form fills.
Frequently asked questions
- What is a Meta Conversions API gateway?
- A CAPI gateway is a service that receives events from your website or store and forwards them to Meta's Conversions API server-to-server, handling authentication, hashing, deduplication, and retries. AdsPing is a managed CAPI gateway with delivery monitoring built in.
- Do I still need the Meta browser pixel?
- You don't have to install it — AdsPing auto-injects the official browser pixel when Meta is configured and dedups it against the server-side events by event_id. Running both maximizes attribution coverage.
- Will my conversions be double-counted?
- No. Every event carries a deterministic event_id shared between the browser pixel and the server-side send. Meta deduplicates the two copies automatically.
- How does AdsPing improve Event Match Quality (EMQ)?
- AdsPing sends SHA-256-hashed email, phone, name, and city plus fbp, fbc, IP, and user agent with every event, and its identity graph backfills parameters missing from the current session using data the same visitor provided earlier. More match parameters = higher EMQ = more attributed conversions.
- Does this work with iOS 14.5+ and Safari ITP?
- Yes — that's the point. Server-side events are reported from AdsPing's servers (or your custom domain), so Safari's tracking prevention and ad blockers can't intercept them. ATT still governs in-app tracking, which no web tool can bypass.
Stop losing conversions today.
14-day free trial on every plan. Full feature set from day one.