---
title: "Meta conversion tracking for WordPress | Plainrouter"
description: "See which website events Plainrouter accepted and what happened when it sent them to Meta. Connect WordPress through custom browser code and a trusted server-side sender."
canonical: https://plainrouter.com/solutions/wordpress
last_updated: 2026-09-23
---

[All solutions](/solutions)

# Meta conversion tracking for WordPress.

Plan a custom WordPress connection to Plainrouter Signals. Keep collection in the browser, credentials on the server, and purchase events tied to verified business activity.

Custom code or HTTP integration · no native plugin

[Check setup requirements](#is-this-a-fit-for-your-setup) · [Read the Conversion API](https://plainrouter.com/docs/api/conversions)

## From your workflow to Meta

- **Website** — Capture the permitted visitor context
- **Your backend** — Verify the event and preserve its identity
- **Plainrouter** — Inspect receipt and delivery status
- **Meta** — Deliver eligible conversion events

Browser installation, a valid server request, Meta delivery and ad attribution are separate outcomes.

## What Plainrouter adds

### Separate the two jobs

Install website collection once and send server conversions from the system that verifies the transaction. Loading a theme script is not proof that a purchase happened.

### Keep credentials server-side

WordPress can make server HTTP requests. Use that capability in maintained application code; never place the Signals Server secret in a theme’s browser JavaScript.

### Trace one purchase

Preserve the business event ID and original time when a job retries. Follow its receipt and delivery status to distinguish a retry from a second purchase.

## Is this a fit for your setup?

For developers who can maintain WordPress code, integrate the site’s consent system and send authenticated HTTP requests from a trusted backend. Confirm that your hosting plan allows the required custom code.

[Explore Signals](/product/signals)

### When your existing setup is enough

For a WooCommerce store that needs standard Meta conversion sharing, evaluate Meta for WooCommerce first: its documented integration already includes CAPI. A second sender is not automatically an improvement.

[Compare tracking approaches](/library/server-side-tracking-tools)

## How WordPress conversion tracking works

### Inventory installed senders

Check plugins, theme snippets and tag managers for overlapping purchase events. If WooCommerce is present, review its existing Meta integration before adding custom delivery.

### Wire collection and permission

Use a maintained plugin or theme integration to load the generated snippet once. Connect the real consent decision and test both granted and denied states on the published site.

### Send after verification

Map verified website transactions to the documented Conversion API. Retain consent and visitor context, keep the secret on the server, and check the response and destination delivery.

## WordPress conversion tracking FAQ

### Does Plainrouter provide a WordPress plugin?

This setup uses maintained custom code and the HTTP API. It is not a claim of a native Plainrouter WordPress or WooCommerce plugin.

### Can I run it alongside my existing Meta plugin?

Choose one purchase sender or design and validate a migration. Independent integrations do not automatically coordinate their event IDs.

### Does a form submission count as a purchase?

No. Use the event type that matches the verified activity. A submit button or thank-you page does not establish payment or consent for advertising delivery.

## Implementation guides

- [Install the browser snippet](https://plainrouter.com/docs/signals/install-pixel)
- [Read the Conversion API contract](https://plainrouter.com/docs/api/conversions)
- [Investigate missing or duplicate events](/library/meta-capi-missing-duplicate-events)

Reference documentation: [WordPress HTTP requests](https://developer.wordpress.org/reference/functions/wp_remote_post/) · [Meta for WooCommerce](https://woocommerce.com/document/facebook-for-woocommerce/)

[Using automation for backend delivery?](/solutions/automation)

## Have the right setup for a custom integration?

Create your Plainrouter workspace when you have confirmed the browser, consent and server requirements above. Keep your existing purchase sender until you have planned the change.

[Get started](/register) · [See pricing](/pricing)