Meta — pick where your site lives

Eight ways to send Meta Conversions API events through AdsPing. Pick the card that matches your website and we'll walk you through it step by step.

Before you start

You don't need a developer or a Meta Business representative for any of these paths. Most merchants finish in under 10 minutes. Here is what you'll need handy:

An AdsPing pixel — created from your dashboard. Free to start, no credit card.
Access to your website — either the admin panel (Shopify, WordPress, Wix, etc.) or, for custom sites, the ability to edit the page <head>.
A Meta Pixel ID and Access Token — we'll show you exactly where to find both inside Meta. Or skip the manual lookup by connecting Meta via OAuth on the AdsPing pixel page.

First time wiring AdsPing to Meta at all? Start with the AdsPing — Meta setup guide. That walks you through connecting Meta on the AdsPing side. Come back here once that's done to put the snippet on your site.

Pick your platform

Click the card that matches where your website is built. Every card leads to a step-by-step install — no jargon, no skipped steps.

Shopify

Paste one line into your theme. Works on every Shopify plan, including Plus.

Copy-paste

~5 minStart →

WooCommerce / WordPress

Add the snippet via your theme's header.php or a code-injector plugin.

Copy-paste

~5 minStart →

Wix

Wix Custom Code section — head injection, no coding required.

Copy-paste

~3 minStart →

Squarespace

Settings → Advanced → Code Injection → Header.

Copy-paste

~3 minStart →

Webflow

Project Settings → Custom Code → Head Code.

Copy-paste

~3 minStart →

Custom HTML site

Hand-coded site, static-site generator, or any other build — guided 5-step wizard, no developer required.

Copy-paste

~10 minStart →

React / Next.js / Vue

Add a Script component to your app root or _app/_document — works with any SPA.

Developer

~5 minStart →

Google Tag Manager

Your team already uses GTM — drop pb.js as a Custom HTML tag and you're done.

Copy-paste

~5 minStart →

Which one if you're unsure? If your site is on Shopify, WooCommerce, Wix, Squarespace, or Webflow, pick that card. If you're not sure where it's built but you can edit HTML, pick Custom HTML site. If your team already uses Google Tag Manager, pick GTM.

After install — connect Meta on AdsPing

Every path above ends the same way: a single line of script is on your site. The next step is to tell AdsPing which Meta pixel to forward events to. Two options:

Option A — OAuth (recommended). On your AdsPing pixel page, click Connect Meta. Approve the consent screen. AdsPing lists every Meta pixel your account has access to — pick one. Tokens rotate automatically.
Option B — Manual. Paste your Pixel ID and Access Token. Use this if your Meta account permissions don't allow the OAuth scope, or if you prefer to manage tokens yourself. See the illustrated manual guide for where to find both in Meta Events Manager.

Either way, the Meta card on your pixel turns green when the credentials validate. From that moment on, every conversion event on your site is forwarded to Meta server-side — resilient to ad blockers and iOS Safari ITP.

Advanced — server-to-server (no pb.js)

If you have an engineering team and prefer to fire conversions directly from your backend (e.g. Shopify Functions, a Node.js backend, a Python order worker), you can call AdsPing's REST endpoint instead of using pb.js. The browser snippet is not required for the server-to-server path.

Send the same payload pb.js would have sent — one POST per conversion event — and AdsPing forwards it to Meta's Conversions API with the same dedup, retry, and observability guarantees. See the integrate page for the full per-platform reference and event payload schema.

PreviousCustom events NextCustom website (wizard)