Layersync Conversion Tracking

<h4>Overview</h4>
LayerSync is server-side conversion tracking for WooCommerce. It captures ecommerce events and forwards them through the LayerSync SaaS to ten ad and analytics platforms via their server-side APIs — Meta (Conversions API), Google Analytics 4 (Measurement Protocol), Google Ads (Enhanced Conversions), TikTok (Events API), Pinterest, Snapchat, LinkedIn, Reddit, X (Twitter), and Microsoft Ads (Bing UET).
Configuration lives in the LayerSync dashboard, so there’s no Google Tag Manager server container, no custom tracking subdomain, no external hosting to manage. The plugin handles WooCommerce; LayerSync handles per-platform delivery.
<h4>Why Server-Side Tracking</h4>
Browser pixels are increasingly blocked by ad-blockers and degraded by Safari/iOS tracking-prevention. Sending the same events server-to-server restores conversion data your ad platforms use to optimize. LayerSync ships WooCommerce events over HMAC-signed HTTPS to the LayerSync hub, which calls each platform’s CAPI with a shared <code>event_id</code> so browser and server halves are deduplicated automatically.
<h4>What’s Included</h4>
Ten ad platforms, one plugin — Meta CAPI, GA4 MP, Google Ads Enhanced Conversions, TikTok Events API, Pinterest CAPI, Snapchat CAPI, LinkedIn CAPI, Reddit CAPI, X CAPI, Microsoft Ads (Bing UET). Browser pixels + server-side CAPI for all of them, with automatic deduplication.
WooCommerce funnel coverage — view item, add to cart, view cart, begin checkout, add payment info, purchase, refund. HPOS-compatible. Triple-fallback purchase capture (<code>payment_complete</code> + <code>checkout_order_processed</code> + <code>woocommerce_thankyou</code>) so custom checkouts still fire.
Lead-form auto-detect — eight form libraries: Contact Form 7, WPForms, Ninja Forms, Formidable Forms, Gravity Forms, Fluent Forms, Elementor Pro Forms, Forminator — plus WooCommerce checkout forms.
Consent & CMP auto-detect — bridges WP Consent API and auto-detects eight CMPs: Complianz, Cookiebot, CookieYes, Borlabs Cookie, iubenda, OneTrust, GDPR Cookie Compliance (Moove), Termly. Strips PII automatically when <code>ad_user_data</code> is denied.
Action Scheduler-backed queue — per-row dispatch via Action Scheduler with WP-Cron fallback. Configurable retention (default 30 days), priority lanes (purchases never evicted), dead-letter UI with operator Replay.
Historical backfill — replay up to 365 days of WooCommerce orders to LayerSync after install or after an outage. Dry-run mode shows what will be queued before any event ships.
Bot & proxy intelligence — multi-signal scoring (datacenter IPs, Apple Private Relay, UA heuristics, velocity, repeated event IDs). Daily-refreshed CIDR list for fresh detection between releases. Operator safe-list overrides.
International phone normalization — 50+ country codes with E.164 canonicalization, dummy-number rejection, and platform-specific hash forms (digits-only for Meta, E.164 for TikTok/Snapchat/Pinterest).
508+ automated tests — PHPUnit coverage on identity, queue retry, encryption, bot scoring, CMP detection, and form adapters. Audit the suite at <code>tests/Unit/</code>.
Browser-side recovery engine — save-first localStorage queue, priority-aware overflow (purchases never dropped), cross-tab serialization, exponential backoff with jitter, multi-day retention (up to 30 days for purchases), <code>sendBeacon</code> on page exit.
Privacy & compliance — per-event consent snapshot, default-denied mode, CMP integration via <code>window.LayerSync.setConsent()</code>, SHA-256 PII hashing, IP anonymization, GDPR / UK ICO / CCPA-aware (Meta Limited Data Use, Do-Not-Sell drop mode).
Operational visibility (via the LayerSync hub) — real-time event status, per-platform delivery success rates, anomaly detection, Slack/PagerDuty/email digest alerts (paid plans).
<h4>Free vs Paid Plans</h4>
Free includes browser pixels for all 10 platforms, server-side CAPI to one platform of your choice, 1 site, 1 team seat, 10,000 events/month, WooCommerce + lead-form auto-tracking, event quality scoring, real-time event log.
Paid plans add: server-side CAPI to all 10 platforms, higher event quotas, multiple sites, team seats, Slack/PagerDuty alerts, anomaly detection, audience builder, ROI dashboard, user journeys, customer profiles, automatic conversion recovery, custom event definitions, white-label (enterprise), custom ingest domain (enterprise).
<a href="https://layersynchub.com/pricing" rel="nofollow ugc">Compare Plans</a>
<h4>For Developers</h4>
LayerSync exposes a JavaScript API, a same-origin REST endpoint, and WordPress hooks for custom event tracking.
JavaScript API:
<pre><code>window.LayerSync.track('lead', {email: 'user@example.com', value: 25.00, currency: 'USD'});
window.LayerSync.setConsent({ad_storage: 'granted', ad_user_data: 'granted'});
</code></pre>
REST endpoint (same-origin, nonce-protected, survives ad-blockers and corporate firewalls):
<pre><code>POST /wp-json/layersync/v1/events
</code></pre>
WordPress filter hooks: <code>layersync_event_payload</code>, <code>layersync_event_before_enqueue</code>, <code>layersync_event_after_delivery</code>, <code>layersync_consent</code>.
Full API documentation: <a href="https://layersynchub.com/docs" rel="nofollow ugc">layersynchub.com/docs</a>.
<h4>Compatibility</h4>
Works alongside Cookiebot, CookieYes, OneTrust, Borlabs Cookie, Complianz, and any CMP that supports a JS consent callback. Compatible with WP Rocket, LiteSpeed Cache, W3 Total Cache, Cloudflare, and other major caching/CDN solutions.
<h4>Getting Started</h4>
<ol>
<li>Sign up at <a href="https://layersynchub.com" rel="nofollow ugc">layersynchub.com</a> and create your first site.</li>
<li>Install and activate LayerSync from the WordPress plugin directory.</li>
<li>Visit LayerSync → Settings in wp-admin and paste your API key, API secret, and Site ID.</li>
<li>Click Test connection — once green, configure your platforms (Meta Pixel ID, GA4 Measurement ID, etc.) in the LayerSync dashboard.</li>
<li>Events start firing within seconds; check the Live Events tab to confirm.</li>
</ol>
<h3>External services</h3>
This plugin connects to external third-party services to provide its functionality. Below is a complete list of all external services, when they are called, what data is transmitted, and links to their terms of service and privacy policies.
LayerSync SaaS Hub (Always Active):
<ul>
<li>Service: LayerSync (https://layersynchub.com)</li>
<li>Purpose: Receives every WooCommerce / form / page event from your site and dispatches matching Conversions API calls to each connected ad platform. Stores the order ledger for conversion recovery, the queue table for outage survivability, and provides the configuration dashboard for your platforms.</li>
<li>What data is sent: Event name, timestamp, hashed user data (email, phone, name SHA-256), product/order data (SKU, value, currency, quantity), browser-side context (page URL, referrer, user agent, IP — IP can be anonymized in settings), <code>event_id</code> for deduplication, consent snapshot</li>
<li>When it’s sent: When a tracked event occurs (page view, product view, add to cart, purchase, refund, lead, etc.). Browser-side: sent via the same-origin REST proxy. Server-side: sent from PHP via WordPress HTTP API.</li>
<li>Service provider: LayerSync</li>
<li>Terms of Service: https://layersynchub.com/terms</li>
<li>Privacy Policy: https://layersynchub.com/privacy</li>
</ul>
When You Enable Meta Pixel / Conversions API:
<ul>
<li>Service: Meta (Facebook) Graph API</li>
<li>Purpose: Send conversion events to Meta for ad optimization</li>
<li>What data is sent: Event name, timestamp, hashed user email/phone, click ID (<code>fbclid</code> / <code>fbp</code> / <code>fbc</code>), product SKU, revenue, IP, user agent, Pixel ID</li>
<li>When it’s sent: Automatically when a tracked event occurs and Meta is enabled in your LayerSync dashboard</li>
<li>Service provider: Meta Platforms, Inc.</li>
<li>Terms of Service: https://www.facebook.com/legal/terms</li>
<li>Privacy Policy: https://www.facebook.com/privacy/policy</li>
</ul>
When Loading Meta Pixel Script (If Enabled):
<ul>
<li>Service: Facebook Connect CDN</li>
<li>Purpose: Load fbevents.js for browser-side Meta Pixel</li>
<li>What data is sent: Standard HTTP request data (IP, user agent, referrer)</li>
<li>When it’s sent: On every page load when Meta browser tracking is enabled</li>
<li>Script URL: https://connect.facebook.net/en_US/fbevents.js</li>
</ul>
When You Enable Google Analytics 4 / Google Ads:
<ul>
<li>Service: Google Analytics 4 Measurement Protocol + Google Ads API</li>
<li>Purpose: Send analytics + conversion events to Google for reporting and ad optimization</li>
<li>What data is sent: Event name, page URL, referrer, session ID, client ID, IP, user agent, device info, hashed user data for Enhanced Conversions</li>
<li>Service provider: Google LLC</li>
<li>Terms of Service: https://marketingplatform.google.com/about/analytics/terms/us/</li>
<li>Privacy Policy: https://policies.google.com/privacy</li>
</ul>
When Loading Google Tag Script (If Enabled):
<ul>
<li>Service: Google Tag Manager CDN</li>
<li>Purpose: Load gtag.js for browser-side GA4 + Google Ads tracking</li>
<li>Script URL: https://www.googletagmanager.com/gtag/js</li>
</ul>
When You Enable TikTok Events API:
<ul>
<li>Service: TikTok Business API</li>
<li>Purpose: Send conversion events to TikTok for ad optimization</li>
<li>Script URL (if browser pixel enabled): https://analytics.tiktok.com/i18n/pixel/events.js</li>
<li>Privacy Policy: https://www.tiktok.com/legal/privacy-policy</li>
</ul>
When You Enable Pinterest Conversions API:
<ul>
<li>Service: Pinterest Tag + Conversions API</li>
<li>Purpose: Send conversion events to Pinterest for ad optimization</li>
<li>Script URL (if browser pixel enabled): https://s.pinimg.com/ct/core.js</li>
<li>Privacy Policy: https://policy.pinterest.com/en/privacy-policy</li>
</ul>
When You Enable Snapchat Conversions API:
<ul>
<li>Service: Snap Pixel + Conversions API</li>
<li>Purpose: Send conversion events to Snapchat for ad optimization</li>
<li>Script URL (if browser pixel enabled): https://sc-static.net/scevent.min.js</li>
<li>Privacy Policy: https://snap.com/en-US/privacy/privacy-policy</li>
</ul>
When You Enable LinkedIn Insight Tag + Conversions API:
<ul>
<li>Service: LinkedIn Marketing API</li>
<li>Purpose: Send conversion events to LinkedIn for ad optimization</li>
<li>Script URL (if browser pixel enabled): https://snap.licdn.com/li.lms-analytics/insight.min.js</li>
<li>Privacy Policy: https://www.linkedin.com/legal/privacy-policy</li>
</ul>
When You Enable Reddit Pixel + Conversion API:
<ul>
<li>Service: Reddit Ads API</li>
<li>Purpose: Send conversion events to Reddit for ad optimization</li>
<li>Script URL (if browser pixel enabled): https://www.redditstatic.com/ads/pixel.js</li>
<li>Privacy Policy: https://www.reddit.com/policies/privacy-policy</li>
</ul>
When You Enable X (Twitter) Pixel + Conversion API:
<ul>
<li>Service: X Ads API</li>
<li>Purpose: Send conversion events to X for ad optimization</li>
<li>Script URL (if browser pixel enabled): https://static.ads-twitter.com/uwt.js</li>
<li>Privacy Policy: https://x.com/en/privacy</li>
</ul>
Important Notes:
<ul>
<li>No automatic data sharing: LayerSync does NOT send any data to ad platforms unless you explicitly enable them in your LayerSync dashboard</li>
<li>Consent-aware: LayerSync respects user consent state via the <code>window.LayerSync.setConsent()</code> API and only fires browser pixels and server events after consent is granted</li>
<li>You control the data: You choose which platforms to enable, what events to track, and what user data to include (emails, phones, etc.)</li>
<li>Required account: This plugin requires a LayerSync account to operate. The plugin alone does not function without API credentials from layersynchub.com.</li>
</ul>
<h3>Privacy Policy</h3>
LayerSync sends the following data to the LayerSync SaaS hub (https://layersynchub.com):
Per-Event Data:
<ul>
<li>Event name (e.g. <code>purchase</code>, <code>add_to_cart</code>)</li>
<li>Timestamp</li>
<li>Page URL and referrer</li>
<li>User agent</li>
<li>IP address (configurable — can be anonymized)</li>
<li><code>event_id</code> for deduplication</li>
<li>Visitor consent snapshot at the moment of the event</li>
<li>LayerSync first-party visitor ID (<code>layersync_uid</code> cookie — UUIDv4, 2-year sliding expiry)</li>
</ul>
For E-Commerce Events:
<ul>
<li>Product SKU, title, category, image URL, price, currency, quantity</li>
<li>Order ID, total, currency (for purchase / refund events)</li>
</ul>
For Lead / Form Events:
<ul>
<li>Form ID, submission ID, field values you’ve configured as trackable</li>
</ul>
Hashed User Data (when available, hashed BEFORE leaving your server):
<ul>
<li>Email (SHA-256)</li>
<li>Phone (SHA-256)</li>
<li>First name (SHA-256)</li>
<li>Last name (SHA-256)</li>
<li>City, state, zip, country (SHA-256)</li>
</ul>
LayerSync hashes PII server-side before forwarding to any ad platform.
External Data Sharing (Only When You Enable Each Platform):
Per-platform data forwarding is documented in the External services section above. No data is sent to any ad platform unless you explicitly enable it in your LayerSync dashboard.
Privacy Controls:
<ul>
<li>IP Anonymization: Available in Settings → Privacy.</li>
<li>Consent Integration: Respects <code>window.LayerSync.setConsent({...})</code> for Cookiebot, CookieYes, OneTrust, Borlabs Cookie, Complianz, and custom consent managers.</li>
<li>Default-denied mode: Treats all visitors as consent-denied until a CMP signals otherwise — suitable for EU/UK traffic.</li>
<li>Right to delete: Send a <code>POST /api/v1/privacy/delete</code> request to LayerSync with the visitor’s <code>external_id</code> (or hashed email / phone) and all matching events, audit rows, customer profile entries, landing signals, and delivery records are removed.</li>
</ul>
Your Responsibilities:
<ul>
<li>Disclose LayerSync’s data flow in your site’s privacy policy</li>
<li>Obtain user consent before tracking, where required by law</li>
<li>Configure data retention and privacy settings appropriately</li>
<li>Honor user data-deletion requests via the LayerSync privacy API</li>
</ul>
<h3>Support</h3>
<ul>
<li><a href="https://layersynchub.com/docs" rel="nofollow ugc">Documentation</a></li>
<li><a href="https://wordpress.org/support/plugin/layersync-conversion-tracking" rel="ugc">Support</a></li>
<li><a href="https://layersynchub.com/contact" rel="nofollow ugc">Contact us</a></li>
</ul>
<h3>Trademarks & Third-Party Services</h3>
LayerSync integrates with various third-party analytics and advertising platforms. All trademarks, service marks, and company names mentioned in this plugin are the property of their respective owners.
Third-Party Platforms:
<ul>
<li>Meta, Facebook, Instagram, and Facebook Pixel are trademarks of Meta Platforms, Inc.</li>
<li>Google, Google Analytics, Google Ads, and GA4 are trademarks of Google LLC.</li>
<li>TikTok is a trademark of ByteDance Ltd.</li>
<li>Pinterest is a trademark of Pinterest, Inc.</li>
<li>Snapchat is a trademark of Snap Inc.</li>
<li>LinkedIn is a trademark of Microsoft Corporation.</li>
<li>X (Twitter) is a trademark of X Corp.</li>
<li>Reddit is a trademark of Reddit, Inc.</li>
<li>WooCommerce is a trademark of Automattic, Inc.</li>
</ul>
Integration Requirements:
<ul>
<li>Users must have active accounts with third-party platforms to use their respective features</li>
<li>API access requires platform-specific credentials and compliance with their terms of service</li>
<li>Data transmission follows each platform’s API specifications and privacy policies</li>
<li>Users are responsible for compliance with each platform’s terms of service</li>
</ul>
LayerSync is an independent plugin and SaaS, and is not officially affiliated with, endorsed by, or sponsored by any of the companies mentioned above. All product names, logos, brands, and trademarks are property of their respective owners.
Data Privacy: LayerSync forwards event data to enabled ad platforms only with user consent. No data is transmitted to any third party unless explicitly configured by the site administrator.

LayerSync – Conversion Tracking, Pixel Manager, and Server-Side API

Conversion tracking for online stores. Pixel injection plus server-side Conversion API delivery, built for WooCommerce.

axitrace

AxiTrace for WooCommerce connects your store to the AxiTrace server-side tracking platform at <a href="https://axitrace.com/" rel="nofollow ugc">axitrace.com</a>. Every purchase, add-to-cart, and begin-checkout event is captured on the server and forwarded to your ad platforms — reaching customers that browser-based pixels miss entirely.
Why server-side tracking?
Browser pixels can be blocked by ad blockers, restricted by iOS Intelligent Tracking Prevention, and refused via cookie consent banners. Server-side events travel directly from your WooCommerce server to Facebook CAPI, TikTok Events API, Google Ads, and Google Analytics 4, so conversions are still recorded when the browser pixel cannot fire.
Deduplication so you never double-count
AxiTrace generates a deterministic UUID v5 event ID for every WooCommerce order. The same event ID is attached to both the browser-side purchase pixel fire and the server-side purchase event. Facebook CAPI, TikTok Events API, and Google Ads use that shared event ID to deduplicate automatically — each conversion is counted exactly once, regardless of how many times the confirmation page loads or how many pixels fire.
Server-side AddToCart events
AxiTrace sends AddToCart events server-side, triggered by the WooCommerce <code>woocommerce_add_to_cart</code> hook. This records add-to-cart activity from the server, so the event is captured even when the browser-side pixel is blocked or restricted.
Asynchronous by design — checkout never blocks
All server-side event transmissions are dispatched via WooCommerce Action Scheduler. The HTTP request to AxiTrace’s ingestion API happens in a background job, decoupled from the order placement flow. Checkout latency is unaffected even if the AxiTrace API is momentarily slow or unavailable.
Platform coverage
One plugin. One workspace key. AxiTrace routes your events to whichever ad platforms you connect in your dashboard:
<ul>
<li>Facebook / Meta — Conversions API (CAPI)</li>
<li>TikTok — Events API (server-side)</li>
<li>Google Ads — Offline Conversion Upload (GCLID-based attribution)</li>
<li>Google Analytics 4 — Measurement Protocol</li>
</ul>
HPOS and Cart/Checkout Blocks compatible
AxiTrace for WooCommerce declares compatibility with WooCommerce High-Performance Order Storage (HPOS) and the modern Cart/Checkout Blocks, so it works correctly on stores that have migrated away from legacy shortcode-based checkout.
WP Consent API support
The plugin detects the <a href="https://wordpress.org/plugins/wp-consent-api/" rel="ugc">WP Consent API</a> and checks the visitor’s consent level before firing events. When no consent framework is present, the plugin fires freely (opt-out model). When a framework is present, the plugin respects the consent status for the <code>statistics</code> and <code>marketing</code> categories. This gives your store a ready compliance path without requiring you to build custom integration.
GDPR personal-data tools built in
AxiTrace registers a WordPress personal-data exporter and eraser (<code>wp_privacy_personal_data_exporters</code> / <code>wp_privacy_personal_data_erasers</code>), enabling your store to fulfill GDPR deletion requests directly from the WordPress Tools > Erase Personal Data screen.
Privacy first
Customer email addresses and phone numbers are transmitted in plain text to AxiTrace’s ingestion API at <code>stat.axitrace.com</code> and are SHA-256 hashed inside AxiTrace before being forwarded to any ad platform. No raw PII leaves the AxiTrace platform. See our Privacy Policy at <a href="https://axitrace.com/privacy/" rel="nofollow ugc">axitrace.com/privacy/</a> and the <code>== External Services ==</code> section below for the complete disclosure.
Free plugin. Paid plans for volume.
The plugin itself is free and open source (GPL v2 or later). An AxiTrace account at <a href="https://axitrace.com/" rel="nofollow ugc">axitrace.com</a> is required. Free workspaces are available. Paid plans unlock higher event volumes, longer data retention, and priority support — see <a href="https://axitrace.com/" rel="nofollow ugc">axitrace.com</a> for current pricing.
Requires an AxiTrace account at <a href="https://axitrace.com/" rel="nofollow ugc">https://axitrace.com/</a>.
<h3>External Services</h3>
This plugin connects to stat.axitrace.com — the AxiTrace event-ingestion API.
<ul>
<li>Service: AxiTrace conversion tracking SaaS.</li>
<li>Endpoint: <code>https://stat.axitrace.com/woocommerce/pixel</code> (POST).</li>
<li>When data is sent: on page views (cart, product, checkout, thank-you), add-to-cart events, begin-checkout events, and order placement / payment completion.</li>
<li>Data transmitted: order ID, plain-text billing email (hashed downstream by AxiTrace), billing phone, billing city/country/zip, order total + currency, line items (SKU, name, quantity, price), user agent, IP address, AxiTrace session/user identifiers, click-attribution cookies (fbc, fbp, gclid, ttclid, msclkid, twclid, epik, li_fat_id, sccid, rdt_cid), UTM parameters, page URL/referrer/title.</li>
<li>Why: to forward the conversion to Facebook CAPI, TikTok Events API, Google Ads, GA4, and other ad platforms configured in your AxiTrace workspace.</li>
<li>Terms of Service: https://axitrace.com/terms/</li>
<li>Privacy Policy: https://axitrace.com/privacy/</li>
</ul>
Optional first-party tracking domain
You may optionally configure a custom first-party subdomain under WooCommerce → Settings → Integrations → AxiTrace → “First-party tracking domain”. When set to e.g. <code>metrics.your-store.com</code> (which you set up in your AxiTrace workspace and verify via CNAME to <code>stat.axitrace.com</code>), the SDK and ingestion endpoint load from your own domain instead of stat.axitrace.com. The data transmitted, the endpoint path (<code>/woocommerce/pixel</code>), and the recipient (AxiTrace) remain identical — only the hostname changes. This is purely a delivery optimization that helps bypass client-side blocking; no third-party service is added.
When this field is empty, the plugin uses the default <code>stat.axitrace.com</code> endpoint described above.
Auto-detect lookup endpoint
When the merchant clicks the “Detect from AxiTrace” button on the settings page, the plugin makes a single server-to-server GET request to <code>https://axitrace.com/api/public/workspace/tracking-domain?key={public_key}</code> (AxiTrace admin host — separate from the ingestion host <code>stat.axitrace.com</code>) to look up the default verified domain registered for that workspace. The request contains only the merchant’s own workspace public key (already exposed in every browser event); no customer or visitor data is sent.

AxiTrace for WooCommerce

Server-side conversion tracking for WooCommerce — Facebook CAPI, TikTok Events API, Google Ads, and GA4 from one plugin.

LayerSync – Conversion Tracking, Pixel Manager, and Server-Side API vs AxiTrace for WooCommerce