Meta Conversions API setup for WordPress
WordPress Meta setups accumulate pixels. The theme has one, a plugin has one, the page builder has a field for one, and someone pasted one into a widget. Four paths, four event IDs, four conversions for one lead.
Free30 minutesNo obligation
WordPress + Meta CAPI · what breaks
What goes wrong on WordPress
- 01
Forms submitting over AJAX
No navigation, so a thank-you-page trigger can never fire.
- 02
Caching plugins serving stale pages
Including a stale data layer, which looks exactly like a broken tag.
- 03
Optimisation plugins deferring the container
So it loads after the event it was supposed to catch.
- 04
Several pixels from several sources
Theme, plugin, builder field, pasted widget.
WordPress + Meta CAPI · the fix
What changes — WordPress + Meta CAPI
Events bound to the plugin's real success hook
Not to a navigation that doesn't happen.
One tracking path
After a full inventory of what's installed.
Caching and deferral accounted for
Rather than blamed on the tag.
WordPress + Meta CAPI · architecture
How Meta tracking behaves on WordPress
Count the pixels before you build anything on WordPress.
- 1
Full pixel inventory first
Theme options, plugins, builder settings, widgets, container.
- 2
One path retained
The rest removed, not disabled and forgotten.
- 3
A lead ID as event_id
Generated at submission, written to both paths.
- 4
Customer data from the submission
Normalized then hashed server-side.
- 5
fbclid captured on landing
Into a hidden field, so fbc exists at all.
WordPress + Meta CAPI · diagnose
Where WordPress tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Submit a form and watch the URL
No change means a page-view trigger can never fire.
- 02
List every plugin with a tracking field
Including SEO, security and builder plugins.
- 03
Disable optimisation temporarily and retest
Deferred JavaScript is a common invisible cause.
- 04
Check whether the confirmation page is cached
A cached page can carry another visitor's values.
- 05
Reconcile submissions against CRM records
For a closed month.
WordPress + Meta CAPI · prove
The QA evidence — WordPress + Meta CAPI
Run on WordPress specifically, on a live conversion rather than in preview mode.
Source of truth
your CRM or form submission records
- A live form submission captured with the payload read, not previewed.
- Trigger confirmed firing on the form's real success state.
- Only one pixel path confirmed active after inventory.
- Click identifiers confirmed present in the submitted data.
- Submissions reconciled against CRM records for a closed month.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
WordPress + Meta CAPI · free audit
What we check in the free audit
- Submit a form and watch the URL
- List every plugin with a tracking field
- Disable optimisation temporarily and retest
- Check whether the confirmation page is cached
- Reconcile submissions against CRM records
Checked against
your CRM or form submission records
Free30 minutesNo obligation
WordPress + Meta CAPI · when not to buy
When you don't need this on WordPress
Worth reading before you buy anything, from us or anyone.
- If your form conversions fire reliably and your counts reconcile against your CRM, the WordPress plugin lottery hasn't bitten you and there's nothing here to buy.
- Most of this is inventory work you can do yourself in an afternoon: list the plugins, submit a test form, watch what fires.
- If you run WooCommerce, the ecommerce side has its own page and different failure modes — this one is about WordPress as a lead-generation site.
- Server-side matters most here when caching or optimisation plugins are interfering. If neither is installed, browser-side may be perfectly adequate.
WordPress + Meta CAPI · what we deliver
What gets built for Meta on WordPress
A shared event ID on both paths
A lead ID generated at submission and written into both the browser event and the CRM record.
Standard event names, exactly cased
Meta matches on name and ID together, so a case difference alone produces two events.
Customer data normalized then hashed
Lowercase and trimmed email, phone in E.164. This is where nearly every low match quality score comes from.
fbc and fbp forwarded from the browser
fbc only exists if fbclid was captured on landing — a very common gap.
Written guarantee
95%+ tracking accuracy
Measured against your CRM or form submission records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
WordPress + Meta CAPI questions, answered
Because there are so many places to paste one — theme options, plugin settings, builder fields, widgets. Nobody removes the old one.
A lead ID generated at submission and written into both the browser event and the CRM record.
Capture fbclid on landing and write it into a hidden field. Without that capture, fbc never exists.
Remove them. Disabled-and-forgotten has a habit of being re-enabled by an update or by whoever inherits the site.
Free · 30 min
Get Pixel and CAPI counting once on WordPress
WhatsAppFree30 minutesNo obligation
