LayerSync – Conversion Tracking, Pixel Manager, and Server-Side API
| 开发者 | layersync |
|---|---|
| 更新时间 | 2026年5月18日 03:45 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
event_id so browser and server halves are deduplicated automatically.
What's Included
Nine 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. 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 — Contact Form 7, WPForms, Ninja Forms, Formidable Forms, and WooCommerce checkout forms.
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 9 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 9 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
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.
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
- Sign up at layersynchub.com and create your first site.
- Install and activate LayerSync from the WordPress plugin directory.
- Visit LayerSync → Settings in wp-admin and paste your API key, API secret, and Site ID.
- Click Test connection — once green, configure your platforms (Meta Pixel ID, GA4 Measurement ID, etc.) in the LayerSync dashboard.
- Events start firing within seconds; check the Live Events tab to confirm.
安装:
- Go to Plugins → Add New
- Search for "LayerSync"
- Click Install Now, then Activate
- Download the ZIP from WordPress.org
- Go to Plugins → Add New → Upload Plugin
- Upload the ZIP, install, and activate
- Sign up at layersynchub.com if you haven't already
- Create a site in your LayerSync dashboard and copy your API key, API secret, and Site ID
- Go to LayerSync → Settings in wp-admin
- Paste your credentials and click Test connection
- Once green, configure your ad platforms (Meta Pixel ID, GA4 Measurement ID, etc.) in your LayerSync dashboard
- Events start firing automatically; verify in the Live Events tab
常见问题:
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?
- Install and activate LayerSync
- Sign up at layersynchub.com and create your site
- In your LayerSync dashboard, go to Platforms → Meta and paste your Pixel ID + Conversions API Access Token (both from Meta Events Manager)
- Save and click Test Connection
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
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?
Nine: Meta (Facebook & Instagram), Google Ads, Google Analytics 4, TikTok, Pinterest, Snapchat, LinkedIn, Reddit, and X (Twitter). All nine are server-side, all nine are available on paid plans. The free plan supports browser pixels for all 9 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 9 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 9 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
更新日志:
- One-time backfill: marks every order whose server purchase event was already delivered as "pixel-rendered" so 1.18.1's once-per-order guard takes effect immediately on legacy orders. Without this, each pre-1.18.1 order would cost one stray browser purchase fire on its first thank-you-page revisit before the guard kicked in. Runs asynchronously via WP-Cron in batches of 200 so admin page loads stay snappy on stores with thousands of orders.
- Fixed duplicate purchase events fired by the browser pixel on order-received page revisits. The thank-you page URL is permanent — customers bookmark it, merchants revisit to test, and WC's payment redirect can reload it — so without a guard, every revisit re-fired the same purchase event_id, inflating dashboard funnel and revenue numbers. The pixel now sets a
_layersync_purchase_pixel_renderedorder meta on first render and silently skips on subsequent visits, mirroring the existing server-side_layersync_purchase_sentguard.
- Homepage now fires a
view_contentevent in addition topage_view, so Meta and TikTok have an explicit top-of-funnel signal for cold-start audience optimization. - Click-to-contact CTAs are auto-tracked: clicks on
tel:,sms:,mailto:, WhatsApp (wa.me,api.whatsapp.com), and Messenger links fire acontactevent mapped to MetaContactand TikTokContact. Captures intent signals from off-site CTAs without any merchant setup. - Pixel
firePixelEventnow passescontent_nameandcontent_typethrough to Meta and TikTok for non-product events so Pixel Helper and attribution dashboards label them meaningfully.
- Renamed plugin to better describe what it does: "LayerSync for WooCommerce – Conversion Tracking, Server-Side API, Pixel Manager, GA4".
- Hardened the public events endpoint: same-origin nonce check, per-IP rate limit, body-size cap, and a block on
purchase/refundevents (those flow only through the WooCommerce server hook now). - Refactored every inline
<script>to ship throughwp_add_inline_scriptagainst registered handles, in line with the WordPress Plugin Directory's enqueue-API guideline. - Replaced closure-based
register_setting()sanitize callbacks with named static methods so static-analysis tools can resolve them. - Scoped the "Not connected" admin notice to the Dashboard, Plugins list, and WooCommerce Settings only — no more banner on every admin page.
- CSV queue export now neutralizes leading
=,+,-,@characters to prevent spreadsheet formula injection when an admin opens the file. - Declared
Requires Plugins: woocommerce; bumpedRequires at leastto 6.5.
- Browser pixel injection for 9 ad platforms: Meta (Facebook & Instagram), Google Tag (GA4), Google Ads, TikTok, Snapchat, Pinterest, Reddit, X (Twitter), and LinkedIn.
- Server-side Conversions API forwarding via the LayerSync hub — one connection, every platform.
- Same-origin REST proxy keeps event delivery working through ad-blockers and corporate firewalls.
- Browser-side resilience: events queue locally during outages and drain automatically when connectivity returns.
- Lead-form tracking for Contact Form 7, WPForms, Ninja Forms, and Formidable.
- Privacy-first: per-event consent capture, CMP integration via
window.LayerSync.setConsent({...}), IP anonymization, and SHA-256 PII hashing before any platform handoff. - Catalog sync to LayerSync for one product feed URL consumed by every connected platform.