AdsPing

Introduction

AdsPing is a server-side conversion tracking platform. Drop one script on your site and forward events to Meta, TikTok, Google Ads, and GA4 — bypassing ad blockers and iOS 14.5+ tracking limits.

What is AdsPing?

AdsPing is a server-side conversion tracking platform built for merchants who care about attribution accuracy. You install a single script (pb.js) on your site, configure which destinations to forward to, and AdsPing handles the rest — collecting events, deduplicating browser/server fires, and dispatching to each platform's server-side API with full match quality.

Each event is forwarded through your own backend channel, so ad blockers, iOS 14.5+ tracking restrictions, and third-party cookie deprecation can't silently break your reporting.

New here? Jump to the Quickstart — you'll have a live pixel forwarding events to Meta + TikTok in under five minutes.

Why server-side?

Browser pixels (Meta's fbq, TikTok's ttq, Google's gtag) load JavaScript from the platform's domain. Ad blockers and privacy-focused browsers block those domains by default — Meta's own data shows 30-50% of pixel events get dropped on average. Server- side forwarding bypasses this entirely: events leave your browser through your domain, hit your backend, and get forwarded server-to- server using the platform's API.

Practical benefits

  • Adblocker-immune. pb.js posts to your own domain; ad blockers can't blanket-block it the way they do facebook.com/tr.
  • iOS 14.5+ resilient. Server-side conversions don't depend on the App Tracking Transparency prompt or Safari ITP cookie restrictions.
  • Better match quality. Server-side enrichment adds IP, user agent, and hashed user identifiers (email, phone, FBC, FBP, gclid) the browser pixel often misses.
  • Deduplication. When you keep the browser pixel alongside server-side, AdsPing fires the same event_id from both channels so platforms count it once but with combined match signals.

How it works

Installation is a single <script> tag on your site. After that, the architecture is:

  • pb.js (browser). Captures page views, form submits, ecommerce events, and gtag/fbq/ttq mirror calls. Posts each event to AdsPing's ingest endpoint.
  • AdsPing backend. Receives the event, looks up the configured pipelines for the pixel, and queues a forward job per destination (Meta, TikTok, Google Ads, GA4, GTM Server, custom webhook).
  • Platform APIs. Each pipeline dispatches to the platform's server-side API with the same event_id used in the browser, so deduplication is automatic.

Supported destinations

Meta CAPIServer-side conversions for Facebook + Instagram ads. Auto-injects browser pixel for dedup.TikTok Events APIServer-side conversions for TikTok ads. Auto-injects browser pixel + ttq.track mirror.Google AdsConversions API + gtag fallback. Multi-action setup (Lead, Purchase, etc.).GA4 / GTM ServerMeasurement Protocol + Server-side GTM container support.

Your first five minutes

The fastest path from zero to a working conversion event:

  • Sign up. Create your AdsPing account at adsping.io/signup. The Standard plan has a 14-day trial; no card needed for sign-up.
  • Create a pixel. Each domain gets one pixel. Enter the domain (e.g. acme.com) and pick a plan.
  • Install pb.js. Copy the script tag from the pixel detail page and paste into your site's <head>.
  • Connect a destination. Click "Connect Meta" on the pixel detail page → OAuth → done. Repeat for TikTok and Google Ads.
  • Verify. Open your site, trigger a Lead/Purchase event, and watch it land in Meta Events Manager → Test Events.

Next steps

QuickstartStep-by-step setup walkthrough.Install pb.jsWhere to put the script + framework-specific notes.How it worksArchitecture: pixels, pipelines, and event flow.Test Event CodeRoute events to platform Test Events tabs without affecting production.
NextQuickstart