> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clientplug.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Meta Conversions API
> Send high-match, server-side conversions from any client's site with one line of code.
The **Conversions API (CAPI)** sends conversions to Meta **server-side**, so you
capture leads that browser pixels miss — the ones lost to ad blockers, iOS
restrictions, and cookie limits. ClientPlug sets it up per client with a single
snippet you paste into their site.
The Conversions API is available on the **Pro** and **Enterprise** plans. See
[Plans & pricing](/plans-and-pricing).
Unlike ClientPlug's other integrations, which only **read** data, the Conversions
API **sends conversion events to Meta on your behalf** for the clients you set it
up on. It never edits or spends on campaigns.
## How it works
Each client gets their own Meta pixel configuration and a universal snippet.
When a visitor completes an action on the client's site, the snippet reports the
conversion to Meta's servers with high-quality match data — improving attribution
and optimization.
## Set up a client
Click **Conversions API** in the sidebar, then **Set up** next to a client.
Paste the client's **Pixel / Dataset ID** and a Meta **access token**.
Optionally add a **test event code** to verify before going live. In-app
links walk you through where to find each in Meta Events Manager.
Pick which customer details the client's form collects — email, phone, name,
ZIP, city, state, country, and more. Signals like IP, user agent, and Meta
click/browser IDs (`fbc` / `fbp`) are captured automatically.
Choose a standard Meta event (e.g. **Lead**, **CompleteRegistration**,
**Purchase**) or a custom one, and how it fires — on **form submit** or when
a **thank-you URL** loads. You can add extra URL-based events and a
conversion value.
Copy the one-line snippet and add it to the `` of the client's site:
```html theme={null}
```
With a test event code set, submit a test lead — ClientPlug watches for it
and confirms events are arriving. When it looks good, click **Go live** so
events count as real conversions.
## Where to paste the snippet
The snippet goes in the site `` on every page with the form (and the
thank-you page for URL events). Common builders:
| Builder | Where |
| ------------------------- | -------------------------------------------------------------------------------------------- |
| **GoHighLevel** | Sites → your funnel/website → Settings → **Head Tracking Code** |
| **WordPress / Elementor** | A header-scripts plugin (e.g. WPCode), or Elementor → Site Settings → Custom Code → `` |
| **Webflow** | Project Settings → Custom Code → **Head Code**, then Publish |
| **Unbounce** | Page → Settings → Javascripts → placement **Head** |
| **Custom HTML** | Just before `` on every page with the form |
Need the details on finding your Dataset ID, access token, or test event code —
or setting up a GoHighLevel webhook? The in-app **Conversions API → Help** pages
cover each step.
## Connection status
Each client shows a status on the Conversions API page:
| Status | Meaning |
| -------------------- | --------------------------------------------------------- |
| **Pending setup** | Configured, no events received yet |
| **Receiving (test)** | Test events arriving, not yet counted as real conversions |
| **Live** | Real conversions flowing to Meta |
## Disconnecting
Click **Disconnect** on a client to stop sending events and remove their pixel
and token configuration. The snippet on their site will stop reporting.