Title: Datablow Event Tracker for Meta Conversions API
Author: pralayasimha
Published: <strong>May 31, 2026</strong>
Last modified: May 31, 2026

---

Search plugins

![](https://ps.w.org/datablow-capi-tracker/assets/icon-256x256.png?rev=3555668)

# Datablow Event Tracker for Meta Conversions API

 By [pralayasimha](https://profiles.wordpress.org/pralayasimha/)

[Download](https://downloads.wordpress.org/plugin/datablow-capi-tracker.1.0.2.zip)

 * [Details](https://wordpress.org/plugins/datablow-capi-tracker/#description)
 * [Reviews](https://wordpress.org/plugins/datablow-capi-tracker/#reviews)
 *  [Installation](https://wordpress.org/plugins/datablow-capi-tracker/#installation)
 * [Development](https://wordpress.org/plugins/datablow-capi-tracker/#developers)

 [Support](https://wordpress.org/support/plugin/datablow-capi-tracker/)

## Description

Datablow Event Tracker connects your WordPress site directly to Meta using the Conversions
API (CAPI). It sends events from both the browser and the server side with matching
deduplication keys, so your ad campaigns receive complete and accurate conversion
data.

Traditional browser-only tracking loses 20–30% of event data due to ad-blockers,
iOS privacy protections, and Safari Intelligent Tracking Prevention (ITP). This 
plugin addresses those challenges by acting as a local proxy on your own domain 
and writing cookies server-side.

#### Core Features

 * **PageView Tracking** — Fires PageView events from both the browser pixel and
   the server side.
 * **Deduplication Engine** — Generates matching `event_id` values for browser and
   server events so Meta merges them automatically.
 * **Audit Logger** — Stores the last 50 Conversions API payloads and HTTP response
   codes in your admin dashboard.
 * **Test Simulator** — Manually trigger test CAPI payloads from WordPress to verify
   your configuration.
 * **Ad-Blocker Script Proxy** — Serves the Meta Pixel JavaScript from your own 
   domain endpoint, preventing ad-blockers from blocking the tracker.
 * **Cookie Keeper** — Writes `_fbp` and `_fbc` cookies from PHP (server side), 
   extending their lifespan up to 2 years and bypassing Safari ITP limits.
 * **User Registration** — Sends `CompleteRegistration` events when new users register
   on your site.
 * **URL-to-Event Mapping** — Fire any standard Meta event on specific URL paths
   without writing code.

### External Services

This plugin connects to Meta (Facebook) external services to track web events and
transmit conversion data. Specifically:

 1. **Meta Pixel JavaScript (connect.facebook.net)**
 2.  * The plugin loads the Meta Pixel JavaScript library from `https://connect.facebook.
       net/en_US/fbevents.js` in the visitor’s browser to enable browser-side event
       tracking.
     * When the Ad-Blocker Script Proxy feature is enabled, this script is fetched 
       server-side and cached locally, then served from your own domain to the visitor’s
       browser.
     * **What data is sent:** No user data is sent to this URL directly; it is a JavaScript
       file load only.
     * **When:** On every front-end page load when a Pixel ID is configured.
 3. **Meta Pixel Noscript Fallback (www.facebook.com/tr)**
 4.  * The plugin outputs a 1×1 pixel `<img>` tag inside a `<noscript>` block requesting`
       https://www.facebook.com/tr`.
     * **What data is sent:** Pixel ID and a PageView event signal for visitors who
       have JavaScript disabled.
     * **When:** On every front-end page load when a Pixel ID is configured and JavaScript
       is disabled.
 5. **Meta Graph API / Conversions API (graph.facebook.com)**
 6.  * The plugin sends server-side event data to `https://graph.facebook.com/v19.0/{
       pixel_id}/events`.
     * **What data is sent:** Event name, event time, deduplication event ID, action
       source, hashed user data (SHA-256 hashed email, phone, name, city, state, zip,
       country), client IP address, user agent, and Facebook browser/click cookies (`
       _fbp`, `_fbc`). For purchase events, value and currency are also included.
     * **When:** On PageView (every front-end page load), custom URL-mapped events,
       and user registrations — depending on which features are enabled in settings.
     * **Authentication:** An Access Token stored in WordPress options is appended 
       to each request.

These connections to Meta services are required for the plugin’s core conversion
tracking functionality. The processing occurs on Meta’s external servers.

 * **Service Provider:** Meta Platforms, Inc.
 * **Meta Terms of Service:** https://www.facebook.com/legal/terms
 * **Meta Privacy Policy:** https://www.facebook.com/about/privacy
 * **Meta Conversions API Terms:** https://www.facebook.com/legal/developer_terms
 * **Meta Platform Terms:** https://developers.facebook.com/terms/

No data is transmitted until you configure a valid Meta Pixel ID and Conversions
API Access Token in the plugin settings.

## Installation

 1. Upload the `datablow-capi-tracker` folder to `/wp-content/plugins/`, or install
    directly from the WordPress Plugin Directory.
 2. Activate the plugin through the **Plugins** menu in WordPress.
 3. Go to **Settings  Meta CAPI Tracker**.
 4. Enter your **Meta Pixel ID** and **Conversions API Access Token**.
 5. Enable the tracking events you want (user registration, pageview).
 6. Click **Save Configuration**.

## FAQ

### How do I generate a Conversions API Access Token?

Go to **Meta Events Manager  Settings**  scroll to the Conversions API section  
click **Generate access token**.

### Why do I need to deduplicate events?

When you send both browser (Pixel) and server (CAPI) events, Meta could count the
same conversion twice. The plugin attaches a matching `eventID` to both the browser
and server events. Meta detects the matching IDs and merges them into a single event.

### How do I test the connection?

Go to **Meta Events Manager  Test Events**, copy the Test Event Code, paste it into
the plugin’s **Configuration** panel, then go to the **Test Event Center** tab and
click **Trigger Server-Side Event**.

### Does the plugin store any personal data?

The plugin stores the last 50 CAPI request logs in the WordPress database (`wp_options`),
which include HTTP response codes and Meta API response bodies. No raw user PII (
email, phone, name) is stored — all fields are SHA-256 hashed before transmission
and are not stored in logs.

### Is the plugin GDPR compliant?

The plugin transmits hashed user data and cookies to Meta. You are responsible for
obtaining appropriate user consent under GDPR or other applicable regulations before
enabling tracking. Consider using a cookie consent plugin to gate tracking until
consent is given.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Datablow Event Tracker for Meta Conversions API” is open source software. The following
people have contributed to this plugin.

Contributors

 *   [ pralayasimha ](https://profiles.wordpress.org/pralayasimha/)

[Translate “Datablow Event Tracker for Meta Conversions API” into your language.](https://translate.wordpress.org/projects/wp-plugins/datablow-capi-tracker)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/datablow-capi-tracker/),
check out the [SVN repository](https://plugins.svn.wordpress.org/datablow-capi-tracker/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/datablow-capi-tracker/)
by [RSS](https://plugins.trac.wordpress.org/log/datablow-capi-tracker/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.2

 * Standardized codebase for initial public release.
 * Renamed all function/option/constant prefixes from `meta_capi` to `dataevtr` 
   to avoid conflicts with other plugins.
 * Hooked Cookie Keeper, Script Proxy, and URL Event Scanner — these features now
   activate properly on every page load.
 * Added CompleteRegistration tracking on user registration — no restrictions.
 * Removed all license-gating and pro/free mode UI from the admin settings page.
 * Fixed all unescaped outputs in the admin settings page.
 * Fixed `$_COOKIE`, `$_SERVER`, and `$_GET` inputs now all sanitized and validated
   before use.
 * All inline JavaScript output now uses `wp_add_inline_script()` — no direct `echo'
   <script>'` calls.
 * Used `esc_url()` (not `esc_url_raw`) for URL values in JavaScript string context.
 * Admin JavaScript now loaded via `wp_add_inline_script()` attached to a registered
   script handle.

#### 1.0.1

 * Updated slug to `datablow-capi-tracker`.
 * Fixed readme contributor list.
 * Improved output escaping.

#### 1.0.0

 * Initial release.

## Meta

 *  Version **1.0.2**
 *  Last updated **7 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 5.8 or higher **
 *  Tested up to **7.0**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [Conversions API](https://wordpress.org/plugins/tags/conversions-api/)[Facebook Pixel](https://wordpress.org/plugins/tags/facebook-pixel/)
   [meta capi](https://wordpress.org/plugins/tags/meta-capi/)[Server Side Tracking](https://wordpress.org/plugins/tags/server-side-tracking/)
 *  [Advanced View](https://wordpress.org/plugins/datablow-capi-tracker/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/datablow-capi-tracker/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/datablow-capi-tracker/reviews/)

## Contributors

 *   [ pralayasimha ](https://profiles.wordpress.org/pralayasimha/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/datablow-capi-tracker/)