Logik Labs

🚀 PixelPulse for WooCommerce
Transform your WooCommerce store with PixelPulse – the ultimate analytics plugin for tracking, optimizing, and growing your business. Gain valuable insights and take control of your store’s performance by integrating with Google Analytics, Meta Pixel, and more.
✨ Why Choose PixelPulse?
<ul>
<li>
🎯 All-in-One Tracking Solution 
Say goodbye to juggling multiple tools! PixelPulse brings all your tracking into one powerful, easy-to-use plugin.
</li>
<li>
⏱️ Real-Time Event Tracking 
Stay ahead of the game by monitoring key customer actions instantly, like add-to-cart, checkouts, and purchases.
</li>
<li>
🔮 Future-Ready 
PixelPulse is designed for growth, with upcoming integrations for LinkedIn, Pinterest, Microsoft, TikTok, X, and Clarity.
</li>
</ul>
🌟 Key Features You’ll Love
<ul>
<li>
🌐 Multi-Platform Integration 
Track smarter, not harder. PixelPulse supports Google Analytics and Meta Pixel, with even more platforms coming soon.
</li>
<li>
📈 Real-Time Event Tracking 
Track critical events like add-to-cart, checkout, and purchases as they happen.
</li>
<li>
⚙️ Customizable Settings 
Easily configure tracking codes and toggle events to fit your business needs.
</li>
<li>
📊 Detailed Analytics 
Get to know your customers like never before with deep insights into behavior and marketing performance.
</li>
<li>
💡 User-Friendly Interface 
A streamlined dashboard ensures quick setup so you can focus on what matters most – your store.
</li>
</ul>
💎 What Makes PixelPulse Stand Out?
<ul>
<li>Unmatched Flexibility: Tailored tracking for every store.</li>
<li>Future-Proof Design: New integrations always on the horizon.</li>
<li>Easy to Use: No coding needed – just plug and play!</li>
<li>Real Results: Drive better decisions with actionable data.</li>
</ul>
📥 Ready to Take Control of Your WooCommerce Store? 
Download PixelPulse now and unlock the full potential of your analytics!
<h3>External Services</h3>
PixelPulse integrates with third-party analytics and tracking services to provide comprehensive ecommerce tracking functionality. Below are the details of each service, including the domains accessed, data transmitted, and the specific events triggered.
<h3>1. Google Analytics (via Google Tag Manager)</h3>
<ul>
<li>
Service Purpose: Tracks user behavior and ecommerce events to provide analytics data for store performance insights.
</li>
<li>
Domains Used:
<ul>
<li><code>https://www.googletagmanager.com</code></li>
<li><code>https://www.google-analytics.com</code></li>
</ul>
</li>
<li>
Events and Data Sent:
<ol>
<li>Page Views:</li>
</ol>
<ul>
<li>Triggered: On every page load.</li>
<li>Purpose: Tracks the pages visited by users to monitor site traffic and behavior.
<ol>
<li>Add to Cart:</li>
</ol>
</li>
<li>Triggered: When a product is added to the cart.</li>
<li>Purpose: Tracks product popularity and user purchasing intent.
<ol>
<li>Remove from Cart:</li>
</ol>
</li>
<li>Triggered: When a product is removed from the cart.</li>
<li>Purpose: Helps analyze user decision-making and cart abandonment trends.
<ol>
<li>View Cart:</li>
</ol>
</li>
<li>Triggered: When a user views their shopping cart.</li>
<li>Purpose: Monitors user interaction with the cart page.
<ol>
<li>Purchase Events:</li>
</ol>
</li>
<li>Triggered: After a successful purchase.</li>
<li>Purpose: Tracks completed orders, including customer details and purchased products.
<ol>
<li>Checkout Steps:</li>
</ol>
</li>
<li>Triggered: At each step of the checkout process (e.g., billing, shipping).</li>
<li>Purpose: Monitors checkout flow to identify drop-off points.
<ol>
<li>Cart Abandonment:</li>
</ol>
</li>
<li>Triggered: When a user leaves the site with items in their cart.</li>
<li>Purpose: Identifies potential revenue loss from incomplete purchases.
<ol>
<li>Coupon Usage:</li>
</ol>
</li>
<li>Triggered: When a coupon is applied or removed during checkout.</li>
<li>Purpose: Tracks the effectiveness of promotional campaigns.
<ol>
<li>Dynamic Pricing Events:</li>
</ol>
</li>
<li>Triggered: When a user adjusts product quantities or prices change dynamically.</li>
<li>Purpose: Tracks how users interact with variable pricing features.</li>
</ul>
</li>
<li>
Service Provider: Google LLC
</li>
<li>Terms of Service: <a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms</a></li>
<li>Privacy Policy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy</a></li>
</ul>
<h3>2. Meta (Facebook) Pixel</h3>
<ul>
<li>
Service Purpose: Tracks user behavior for advertising, remarketing, and analytics purposes.
</li>
<li>
Domains Used:
<ul>
<li><code>https://connect.facebook.net</code></li>
<li><code>https://www.facebook.com</code></li>
</ul>
</li>
<li>
Events and Data Sent:
<ol>
<li>Page Views:</li>
</ol>
<ul>
<li>Triggered: On every page load.</li>
<li>Purpose: Tracks user visits and monitors site engagement for ad targeting.
<ol>
<li>Add to Cart:</li>
</ol>
</li>
<li>Triggered: When a product is added to the cart.</li>
<li>Purpose: Identifies users interested in specific products for remarketing.
<ol>
<li>Remove from Cart:</li>
</ol>
</li>
<li>Triggered: When a product is removed from the cart.</li>
<li>Purpose: Monitors changes in purchase intent.
<ol>
<li>Purchase Events:</li>
</ol>
</li>
<li>Triggered: After a successful purchase.</li>
<li>Purpose: Tracks conversions for advertising campaigns and optimizes ad spend.
<ol>
<li>Cart Abandonment:</li>
</ol>
</li>
<li>Triggered: When a user leaves the site with items in their cart.</li>
<li>Purpose: Supports remarketing campaigns to recover lost sales.
<ol>
<li>Coupon Interactions:</li>
</ol>
</li>
<li>Triggered: When a coupon is applied or removed during checkout.</li>
<li>Purpose: Measures the performance and appeal of promotional offers.
<ol>
<li>Dynamic Pricing Events:</li>
</ol>
</li>
<li>Triggered: When a user changes product quantities or interacts with pricing on the product page.</li>
<li>Purpose: Tracks dynamic pricing features for personalized marketing.</li>
</ul>
</li>
<li>
Service Provider: Meta Platforms, Inc.
</li>
<li>Terms of Service: <a href="https://www.facebook.com/terms.php" rel="nofollow ugc">Meta Terms</a></li>
<li>Privacy Policy: <a href="https://www.facebook.com/privacy/policy" rel="nofollow ugc">Meta Privacy</a></li>
</ul>
<ol>
<li>Future Integrations (Coming Soon) 
The following services are planned for future releases:</li>
</ol>
– LinkedIn Pixel 
– Pinterest Pixel 
– Microsoft Advertising 
– TikTok Pixel 
– X (Twitter) Pixel 
– Microsoft Clarity
Note: All data transmission to third-party services occurs only after proper user consent and in compliance with applicable privacy laws. Store owners should ensure they have appropriate privacy policies and cookie consent mechanisms in place when using these tracking features.
Important Privacy Considerations: 
– All tracking includes UTM parameter collection and storage 
– Customer data (email, phone) is only transmitted during specific events like purchase completion 
– Cart abandonment tracking includes a 60-second inactivity timer 
– All tracking respects user consent settings and privacy preferences
<h3>Development Information</h3>
<ul>
<li>🔨 Contributors: LogikLabs – Ensuring PixelPulse meets the highest standards.</li>
<li>🌐 Plugin URI: Visit <a href="https://pixelpulse.logiklabs.tech/" rel="nofollow ugc">PixelPulse</a> for more details.</li>
<li>🏢 Company Website: Learn more about LogikLabs at <a href="https://logiklabs.io/" rel="nofollow ugc">logiklabs.io</a>.</li>
<li>📦 Tags: analytics, tracking, google analytics, facebook pixel, woocommerce, ecommerce, performance.</li>
<li>🧩 Requirements: WordPress 5.0 or higher, PHP 7.4 or higher.</li>
<li>📜 License: Licensed under GPL-2.0-or-later. View <a href="https://www.gnu.org/licenses/gpl-2.0.html" rel="nofollow ugc">License</a>.</li>
</ul>

Pixel Pulse for WooCommerce

🚀 Boost Your WooCommerce Analytics with PixelPulse PixelPulse adds Google Analytics and Meta Pixel tracking to WooCommerce.

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.

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