Datablow Event Tracker for Meta Conversions API

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)

   • 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.

2. Meta Pixel Noscript Fallback (www.facebook.com/tr)

   • 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.

3. Meta Graph API / Conversions API (graph.facebook.com)

   • 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.