Title: LayerSync – Conversion Tracking, Pixel Manager, and Server-Side API Author: Layersync Conversion Tracking Published: 15 mai 2026 Last modified: 29 mai 2026 --- Recherche d’extensions ![](https://ps.w.org/layersync-conversion-tracking/assets/banner-772x250.png?rev =3533447) ![](https://ps.w.org/layersync-conversion-tracking/assets/icon-256x256.png?rev=3533447) # LayerSync – Conversion Tracking, Pixel Manager, and Server-Side API Par [Layersync Conversion Tracking](https://profiles.wordpress.org/layersync/) [Télécharger](https://downloads.wordpress.org/plugin/layersync-conversion-tracking.1.29.1.zip) * [Détails](https://fr.wordpress.org/plugins/layersync-conversion-tracking/#description) * [Avis](https://fr.wordpress.org/plugins/layersync-conversion-tracking/#reviews) * [Installation](https://fr.wordpress.org/plugins/layersync-conversion-tracking/#installation) * [Développement](https://fr.wordpress.org/plugins/layersync-conversion-tracking/#developers) [Support](https://wordpress.org/support/plugin/layersync-conversion-tracking/) ## Description #### Overview 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. #### Why Server-Side Tracking 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 `event_id` so browser and server halves are deduplicated automatically. #### What’s Included **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(` payment_complete` + `checkout_order_processed` + `woocommerce_thankyou`) 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 `ad_user_data` 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 `tests/Unit/`. **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), `sendBeacon` on page exit. **Privacy & compliance** — per-event consent snapshot, default-denied mode, CMP integration via `window.LayerSync.setConsent()`, 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). #### Free vs Paid Plans **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). [Compare Plans](https://layersynchub.com/pricing) #### For Developers LayerSync exposes a JavaScript API, a same-origin REST endpoint, and WordPress hooks for custom event tracking. **JavaScript API:** ``` window.LayerSync.track('lead', {email: 'user@example.com', value: 25.00, currency: 'USD'}); window.LayerSync.setConsent({ad_storage: 'granted', ad_user_data: 'granted'}); ``` **REST endpoint** (same-origin, nonce-protected, survives ad-blockers and corporate firewalls): ``` POST /wp-json/layersync/v1/events ``` **WordPress filter hooks:** `layersync_event_payload`, `layersync_event_before_enqueue`,` layersync_event_after_delivery`, `layersync_consent`. Full API documentation: [layersynchub.com/docs](https://layersynchub.com/docs). #### Compatibility 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. #### Getting Started 1. Sign up at [layersynchub.com](https://layersynchub.com) and create your first site. 2. Install and activate LayerSync from the WordPress plugin directory. 3. Visit **LayerSync Settings** in wp-admin and paste your API key, API secret, and Site ID. 4. Click **Test connection** — once green, configure your platforms (Meta Pixel ID, GA4 Measurement ID, etc.) in the LayerSync dashboard. 5. Events start firing within seconds; check the **Live Events** tab to confirm. ### External services 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):** * **Service:** LayerSync (https://layersynchub.com) * **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. * **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),` event_id` for deduplication, consent snapshot * **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. * **Service provider:** LayerSync * **Terms of Service:** https://layersynchub.com/terms * **Privacy Policy:** https://layersynchub.com/privacy **When You Enable Meta Pixel / Conversions API:** * **Service:** Meta (Facebook) Graph API * **Purpose:** Send conversion events to Meta for ad optimization * **What data is sent:** Event name, timestamp, hashed user email/phone, click ID (`fbclid` / `fbp` / `fbc`), product SKU, revenue, IP, user agent, Pixel ID * **When it’s sent:** Automatically when a tracked event occurs and Meta is enabled in your LayerSync dashboard * **Service provider:** Meta Platforms, Inc. * **Terms of Service:** https://www.facebook.com/legal/terms * **Privacy Policy:** https://www.facebook.com/privacy/policy **When Loading Meta Pixel Script (If Enabled):** * **Service:** Facebook Connect CDN * **Purpose:** Load fbevents.js for browser-side Meta Pixel * **What data is sent:** Standard HTTP request data (IP, user agent, referrer) * **When it’s sent:** On every page load when Meta browser tracking is enabled * **Script URL:** https://connect.facebook.net/en_US/fbevents.js **When You Enable Google Analytics 4 / Google Ads:** * **Service:** Google Analytics 4 Measurement Protocol + Google Ads API * **Purpose:** Send analytics + conversion events to Google for reporting and ad optimization * **What data is sent:** Event name, page URL, referrer, session ID, client ID, IP, user agent, device info, hashed user data for Enhanced Conversions * **Service provider:** Google LLC * **Terms of Service:** https://marketingplatform.google.com/about/analytics/terms/ us/ * **Privacy Policy:** https://policies.google.com/privacy **When Loading Google Tag Script (If Enabled):** * **Service:** Google Tag Manager CDN * **Purpose:** Load gtag.js for browser-side GA4 + Google Ads tracking * **Script URL:** https://www.googletagmanager.com/gtag/js **When You Enable TikTok Events API:** * **Service:** TikTok Business API * **Purpose:** Send conversion events to TikTok for ad optimization * **Script URL (if browser pixel enabled):** https://analytics.tiktok.com/i18n/ pixel/events.js * **Privacy Policy:** https://www.tiktok.com/legal/privacy-policy **When You Enable Pinterest Conversions API:** * **Service:** Pinterest Tag + Conversions API * **Purpose:** Send conversion events to Pinterest for ad optimization * **Script URL (if browser pixel enabled):** https://s.pinimg.com/ct/core.js * **Privacy Policy:** https://policy.pinterest.com/en/privacy-policy **When You Enable Snapchat Conversions API:** * **Service:** Snap Pixel + Conversions API * **Purpose:** Send conversion events to Snapchat for ad optimization * **Script URL (if browser pixel enabled):** https://sc-static.net/scevent.min. js * **Privacy Policy:** https://snap.com/en-US/privacy/privacy-policy **When You Enable LinkedIn Insight Tag + Conversions API:** * **Service:** LinkedIn Marketing API * **Purpose:** Send conversion events to LinkedIn for ad optimization * **Script URL (if browser pixel enabled):** https://snap.licdn.com/li.lms-analytics/ insight.min.js * **Privacy Policy:** https://www.linkedin.com/legal/privacy-policy **When You Enable Reddit Pixel + Conversion API:** * **Service:** Reddit Ads API * **Purpose:** Send conversion events to Reddit for ad optimization * **Script URL (if browser pixel enabled):** https://www.redditstatic.com/ads/pixel. js * **Privacy Policy:** https://www.reddit.com/policies/privacy-policy **When You Enable X (Twitter) Pixel + Conversion API:** * **Service:** X Ads API * **Purpose:** Send conversion events to X for ad optimization * **Script URL (if browser pixel enabled):** https://static.ads-twitter.com/uwt. js * **Privacy Policy:** https://x.com/en/privacy **Important Notes:** * **No automatic data sharing:** LayerSync does NOT send any data to ad platforms unless you explicitly enable them in your LayerSync dashboard * **Consent-aware:** LayerSync respects user consent state via the `window.LayerSync. setConsent()` API and only fires browser pixels and server events after consent is granted * **You control the data:** You choose which platforms to enable, what events to track, and what user data to include (emails, phones, etc.) * **Required account:** This plugin requires a LayerSync account to operate. The plugin alone does not function without API credentials from layersynchub.com. ### Privacy Policy LayerSync sends the following data to the LayerSync SaaS hub (https://layersynchub. com): **Per-Event Data:** * Event name (e.g. `purchase`, `add_to_cart`) * Timestamp * Page URL and referrer * User agent * IP address (configurable — can be anonymized) * `event_id` for deduplication * Visitor consent snapshot at the moment of the event * LayerSync first-party visitor ID (`layersync_uid` cookie — UUIDv4, 2-year sliding expiry) **For E-Commerce Events:** * Product SKU, title, category, image URL, price, currency, quantity * Order ID, total, currency (for purchase / refund events) **For Lead / Form Events:** * Form ID, submission ID, field values you’ve configured as trackable **Hashed User Data (when available, hashed BEFORE leaving your server):** * Email (SHA-256) * Phone (SHA-256) * First name (SHA-256) * Last name (SHA-256) * City, state, zip, country (SHA-256) 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:** * **IP Anonymization:** Available in Settings Privacy. * **Consent Integration:** Respects `window.LayerSync.setConsent({...})` for Cookiebot, CookieYes, OneTrust, Borlabs Cookie, Complianz, and custom consent managers. * **Default-denied mode:** Treats all visitors as consent-denied until a CMP signals otherwise — suitable for EU/UK traffic. * **Right to delete:** Send a `POST /api/v1/privacy/delete` request to LayerSync with the visitor’s `external_id` (or hashed email / phone) and all matching events, audit rows, customer profile entries, landing signals, and delivery records are removed. **Your Responsibilities:** * Disclose LayerSync’s data flow in your site’s privacy policy * Obtain user consent before tracking, where required by law * Configure data retention and privacy settings appropriately * Honor user data-deletion requests via the LayerSync privacy API ### Support * [Documentation](https://layersynchub.com/docs) * [Support](https://wordpress.org/support/plugin/layersync-conversion-tracking) * [Contact us](https://layersynchub.com/contact) ### Trademarks & Third-Party Services 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:** * Meta, Facebook, Instagram, and Facebook Pixel are trademarks of Meta Platforms, Inc. * Google, Google Analytics, Google Ads, and GA4 are trademarks of Google LLC. * TikTok is a trademark of ByteDance Ltd. * Pinterest is a trademark of Pinterest, Inc. * Snapchat is a trademark of Snap Inc. * LinkedIn is a trademark of Microsoft Corporation. * X (Twitter) is a trademark of X Corp. * Reddit is a trademark of Reddit, Inc. * WooCommerce is a trademark of Automattic, Inc. **Integration Requirements:** * Users must have active accounts with third-party platforms to use their respective features * API access requires platform-specific credentials and compliance with their terms of service * Data transmission follows each platform’s API specifications and privacy policies * Users are responsible for compliance with each platform’s terms of service 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. ## Installation #### From WordPress Admin 1. Go to **Plugins Add New** 2. Search for **« LayerSync »** 3. Click **Install Now**, then **Activate** #### Manual Upload 1. Download the ZIP from WordPress.org 2. Go to **Plugins Add New Upload Plugin** 3. Upload the ZIP, install, and activate #### After Activation 1. Sign up at [layersynchub.com](https://layersynchub.com) if you haven’t already 2. Create a site in your LayerSync dashboard and copy your API key, API secret, and Site ID 3. Go to **LayerSync Settings** in wp-admin 4. Paste your credentials and click **Test connection** 5. Once green, configure your ad platforms (Meta Pixel ID, GA4 Measurement ID, etc.) in your LayerSync dashboard 6. Events start firing automatically; verify in the **Live Events** tab WooCommerce is recommended but not required — without WC, the plugin runs in pixel- only mode (no add-to-cart / purchase hooks, but browser pixels still fire and lead- form tracking works). ## FAQ ### How does LayerSync improve ROAS and lower CPA? When browser-side pixels miss conversions (due to iOS 14+, ad blockers, or cookie restrictions), ad platforms optimize on incomplete data and your cost-per-acquisition rises. LayerSync fixes this by sending conversion events **server-to-server** to every connected platform via their respective Conversions API. Browser and server events are deduplicated automatically using a shared `event_id`, so platforms see more of your real conversions without double-counting. More complete data means better optimization and improved Return on Ad Spend. ### How do I set up Meta Pixel with server-side tracking? 1. Install and activate LayerSync 2. Sign up at [layersynchub.com](https://layersynchub.com) and create your site 3. In your LayerSync dashboard, go to **Platforms Meta** and paste your Pixel ID + Conversions API Access Token (both from Meta Events Manager) 4. Save and click **Test Connection** LayerSync automatically fires both the browser Meta Pixel and Meta Conversions API events server-to-server. They’re deduplicated using a shared `event_id`. User data( email, phone, name, address) is SHA-256 hashed and sent as Advanced Matching parameters for maximum Event Match Quality (EMQ). No Google Tag Manager server container required. ### What is server-side tracking and why do I need it? Server-side tracking sends conversion events directly from your server to ad platforms— instead of relying only on browser JavaScript pixels. This matters because: * **Ad blockers** block ~40% of browser tracking pixels * **iOS 14+ App Tracking Transparency** reduced Meta Pixel reported conversions by 30–40% * **Safari ITP** limits first-party cookies to 7 days, causing session data loss * **Browser privacy features** increasingly restrict third-party tracking With server-side tracking, your conversion data bypasses all browser restrictions. Ad platforms see your real sales, optimize better, and your ROAS improves. ### Do I need a LayerSync account? Yes. This plugin connects WordPress to the LayerSync SaaS, which performs the actual server-to-server dispatch to each ad platform. The LayerSync account is what configures which platforms are enabled, stores your API credentials encrypted, and runs the queue + recovery worker. A free plan is available. ### How many ad platforms does LayerSync support? Ten: Meta (Facebook & Instagram), Google Ads, Google Analytics 4, TikTok, Pinterest, Snapchat, LinkedIn, Reddit, X (Twitter), and Microsoft Ads (Bing UET). All ten are server-side, all ten are available on paid plans. The free plan supports browser pixels for all 10 and server-side CAPI for one of your choice. ### Does LayerSync work with WooCommerce? Yes. LayerSync automatically tracks the full WooCommerce funnel: product view add to cart view cart begin checkout add payment info purchase refund. Order metadata( value, SKU, currency, quantity, category) is captured automatically. HPOS-compatible. Triple-fallback purchase hook (payment_complete + checkout_processed + thankyou) ensures no transaction is missed. ### What about Easy Digital Downloads, SureCart, MemberPress? The current release covers WooCommerce and any custom integration via the JavaScript/ REST APIs. Support for additional ecommerce platforms is on the roadmap. ### Does LayerSync slow down my website? No. The browser tracking script loads asynchronously (non-blocking), events are batched server-side, the same-origin REST proxy is lightweight, and the plugin uses indexed database tables. Compatible with WP Rocket, LiteSpeed Cache, W3 Total Cache, Cloudflare, and other caching/CDN solutions. The browser-side recovery queue uses localStorage with strict size limits — no measurable impact on page load. ### Does LayerSync work with High-Performance Order Storage (HPOS)? Yes. LayerSync is fully compatible with WooCommerce HPOS. WC order data is read via the standard `wc_get_order()` API which abstracts over both storage modes. ### Is LayerSync GDPR and CCPA compliant? Yes. The plugin captures per-event consent state and respects it during retries. There’s an admin toggle for « default to denied until consent » suitable for EU/ UK traffic. CMPs integrate via `window.LayerSync.setConsent({ad_storage: 'granted', ad_user_data: 'granted', ad_personalization: 'granted'})`. PII (email, phone, name, address) is SHA-256 hashed server-side before any platform handoff. IP anonymization is supported. ### Does LayerSync support Google Consent Mode v2? Yes — via the `setConsent()` API. Pass the v2 fields (`ad_user_data`, `ad_personalization`) and LayerSync forwards them to Google’s gtag in the correct shape. ### Does LayerSync support Meta Limited Data Use (LDU) for California traffic? Yes. The Privacy tab has an LDU toggle. When enabled, every Meta server event ships with `data_processing_options: ['LDU']` so California-resident traffic is CCPA-compliant. ### What happens if LayerSync’s SaaS goes down? Browser pixels keep firing directly to ad platforms (they’re independent of the LayerSync hub). Server-side events queue in your WordPress database for up to 30 days for critical events (purchases, refunds), 7 days for high-value funnel events( add-to-cart, begin-checkout, lead), and shorter windows for behavioral events. When LayerSync recovers, the queue drains automatically without intervention. ### Can I track custom events? Yes. Use the JavaScript API: ``` window.LayerSync.track('button_click', {button_name: 'Download PDF', value: 0}); ``` Or the REST endpoint from your own PHP code: ``` POST /wp-json/layersync/v1/events ``` Custom event definitions per site (with per-platform name mapping) are available on paid plans. ### Can I export my data? Yes. Every report in the LayerSync dashboard has a CSV export. You can also pull data programmatically via the REST API on paid plans. ### Does LayerSync replace my existing pixel plugins? Yes. The plugin loads each platform’s pixel SDK directly from the platform CDN with hashed Advanced Matching set at init time. You can disable any other Meta/Google/ TikTok pixel plugins. Don’t run two plugins that load the same pixel — both will fire, doubling your conversion counts. ### Can I use LayerSync on client sites / agency white-label? Yes. The free WordPress plugin can be installed on unlimited sites. Each site connects to one LayerSync account. Agencies running multiple client stores use the Growth or Enterprise tiers, which include white-label branding, custom ingest domain, and multi-site management from a single dashboard. ### What’s the difference between Free and Paid plans? **Free** includes: browser pixels for all 10 platforms, server-side CAPI to one platform of your choice, 1 site, 1 team seat, 10K 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). [Compare Plans](https://layersynchub.com/pricing) ## Avis ![](https://secure.gravatar.com/avatar/43f071b54e5784a837ba6df21001c0d95587ea7b7559e0dc73939cbc6783cce7? s=60&d=retro&r=g) ### 󠀁[Reliable conversion tracking setup for WooCommerce](https://wordpress.org/support/topic/reliable-conversion-tracking-setup-for-woocommerce/)󠁿 [askpluskwt](https://profiles.wordpress.org/askpluskwt/) 15 mai 2026 LayerSync helped us improve our WooCommerce conversion tracking setup by making key ecommerce events more consistent across browser and server-side tracking. The plugin is useful for stores that rely on Meta, Google, TikTok, and other ad platforms because it focuses on cleaner event data, deduplication, and API-based delivery instead of only basic pixel installation. The setup was clear, and the product direction is very strong. More platform-specific guides would make it even better, but overall LayerSync is a valuable plugin for ecommerce tracking and attribution. [ Lire l’avis ](https://wordpress.org/support/plugin/layersync-conversion-tracking/reviews/) ## Contributeurs/contributrices & développeurs/développeuses « LayerSync – Conversion Tracking, Pixel Manager, and Server-Side API » est un logiciel libre. Les personnes suivantes ont contribué à cette extension. Contributeurs * [ Layersync Conversion Tracking ](https://profiles.wordpress.org/layersync/) [Traduisez « LayerSync – Conversion Tracking, Pixel Manager, and Server-Side API » dans votre langue.](https://translate.wordpress.org/projects/wp-plugins/layersync-conversion-tracking) ### Le développement vous intéresse ? [Parcourir le code](https://plugins.trac.wordpress.org/browser/layersync-conversion-tracking/), consulter le [SVN dépôt](https://plugins.svn.wordpress.org/layersync-conversion-tracking/), ou s’inscrire au [journal de développement](https://plugins.trac.wordpress.org/log/layersync-conversion-tracking/) par [RSS](https://plugins.trac.wordpress.org/log/layersync-conversion-tracking/?limit=100&mode=stop_on_copy&format=rss). ## Journal des modifications #### 1.29.1 * Fix: catalog « Sync now » records the last-sync time, so the « catalog never synced » tip clears after a successful sync. #### 1.29.0 * Fix: view_item browser + server now share one event_id (dedupe as matched). * Performance: legacy queue / audit options no longer autoloaded on every request. #### 1.28.4 * Fix: begin_checkout event_id shared on WooCommerce Blocks checkout. #### 1.28.3 * Fix: begin_checkout now fires server-side on WooCommerce Blocks checkout. #### 1.28.2 * Fix: ship rebuilt minified bundle containing the 1.28.1 Snap PAGE_VIEW fix. #### 1.28.1 * Fix: Snap uuid_c1 (_scid) reaches the pixel on the first page view. #### 1.27.7 * New: popup conversion goal (Lead / Subscribe / Promo / none). #### 1.27.6 * Improve: Contacts list shows real order total + currency. #### 1.27.5 * Improve: clearer « Import existing customers » wording. #### 1.27.4 * Improve: rename backfill to « Import existing customers »; dedupe orders by email. #### 1.27.3 * New: Subscriptions / Contacts module (backfill, form dual-write, consent capture). * Improve: popup email validation + inline feedback; popup events carry click IDs. #### 1.27.2 * Fix: capture msclkid (Microsoft Ads) server-side. #### 1.27.1 * Fix: purchase value uses order total (includes fees), not line-item sum. #### 1.27.0 * New: popup leads flow to ad platforms as lead events; Popup leads tab. #### 1.26.9 * Improve: remove Recovery & Revenue from sidebar (now in the SaaS dashboard). #### 1.26.8 * Improve: per-column help tooltips across admin tables. #### 1.26.7 * Fix: duplicate native tooltip on help icons. #### 1.26.6 * New: Signal Doctor per-column help tooltips. #### 1.26.5 * Fix: Signal Doctor reads the real event payload; table-header alignment. #### 1.26.4 * Improve: Platforms page read-only (credentials managed in the SaaS dashboard). #### 1.26.3 * Fix: identifier-coverage reports showing 0% (payload shape mismatch). #### 1.26.2 * Housekeeping: metadata-only bump, no functional change. #### 1.26.0 * New: phone normalization for 100 country codes. * New: Termly CMP + Forminator form adapter. * New: subscription_renewal event for WooCommerce Subscriptions. * Improve: bot detection (Apple Private Relay CIDR refresh; human-proof tokens). #### 1.25.1 * Fix: double-count of popup CTA clicks in the dismissal report. #### 1.25.0 * New: deterministic event_id (schema v1) for purchase + sign-up. * Security: strict consent — full suppression on ad_storage=denied. #### 1.24.1 * New: HPOS (High-Performance Order Storage) compatibility. #### 1.24.0 * New: admin redesign into 11 native submenus. * New: Action Scheduler queue (dead-letter, replay, retention, audit log). * New: Microsoft Ads (Bing UET), GA4 reconciliation, WP Consent API bridge. * New: Signal Doctor, Platform Overclaim Shield, Consent-Recovery Graph. * New: bot detection, historical backfill, Safe External Scripts manager. * Improve: accessibility (ARIA tablist, focus styles, breadcrumbs). #### 1.22.1 * Fix: popup events returning 403 for logged-in users (nonce context). #### 1.22.0 * New: lightweight browser-side bot probe (passive signals only). #### 1.21.0 * New: X (Twitter) pixel + Conversion API. * Improve: GA4 ecommerce accuracy; lead / form tracking. * Fix: duplicate guards (add_payment_info, add_shipping_info); X / Snap pixel fixes. #### 1.20.3 * Fix: popups targeting Home / Blog never showing. #### 1.20.2 * Security: hardening + uninstall cleanup; queue retry reliability. #### 1.20.1 * New: GA4 campaign attribution (first / last / last-paid touch). * Security: sanitize landing URLs + referrers (strip PII + order keys). #### 1.20.0 * New: GA4 Direct Browser Mode + full funnel coverage + consent mode. #### 1.19.0 * New: popup builder (modal / slide / bar, audience + trigger targeting, WhatsApp CTA). #### 1.18.2 * Fix: backfill the purchase pixel-rendered guard onto legacy orders. #### 1.18.1 * Fix: duplicate purchase events on thank-you page revisits. #### 1.18.0 * New: homepage view_content; click-to-contact tracking (tel / mailto / WhatsApp). #### 1.17.0 * Security: harden public events endpoint (nonce, rate limit, body cap). * Improve: rename plugin; inline scripts moved to enqueue API; CSV injection guard. #### 1.16.0 Initial public release. * New: browser pixel for 9 ad platforms + server-side Conversions API. * New: lead-form tracking, consent capture, SHA-256 PII hashing. ## Méta * Version **1.29.1** * Dernière mise à jour **il y a 8 heures** * Installations actives **Moins de 10** * Version de WordPress ** 6.5 ou plus ** * Testé jusqu’à **6.9.4** * Version de PHP ** 8.0 ou plus ** * Langue * [English (US)](https://wordpress.org/plugins/layersync-conversion-tracking/) * Étiquettes * [conversion tracking](https://fr.wordpress.org/plugins/tags/conversion-tracking/) [Facebook Pixel](https://fr.wordpress.org/plugins/tags/facebook-pixel/)[google ads](https://fr.wordpress.org/plugins/tags/google-ads/) [google analytics](https://fr.wordpress.org/plugins/tags/google-analytics/)[woocommerce](https://fr.wordpress.org/plugins/tags/woocommerce/) * [Vue avancée](https://fr.wordpress.org/plugins/layersync-conversion-tracking/advanced/) ## Évaluations 5 sur 5 étoiles. * [ 1 avis à 5 étoile ](https://wordpress.org/support/plugin/layersync-conversion-tracking/reviews/?filter=5) * [ 0 avis à 4 étoile ](https://wordpress.org/support/plugin/layersync-conversion-tracking/reviews/?filter=4) * [ 0 avis à 3 étoile ](https://wordpress.org/support/plugin/layersync-conversion-tracking/reviews/?filter=3) * [ 0 avis à 2 étoile ](https://wordpress.org/support/plugin/layersync-conversion-tracking/reviews/?filter=2) * [ 0 avis à 1 étoile ](https://wordpress.org/support/plugin/layersync-conversion-tracking/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/layersync-conversion-tracking/reviews/#new-post) [Voir tous les avis](https://wordpress.org/support/plugin/layersync-conversion-tracking/reviews/) ## Contributeurs * [ Layersync Conversion Tracking ](https://profiles.wordpress.org/layersync/) ## Support Quelque chose à dire ? Besoin d’aide ? [Voir le forum de support](https://wordpress.org/support/plugin/layersync-conversion-tracking/)