LayerSync – Conversion Tracking, Pixel Manager, and Server-Side API
Changelog
1.37.4
New: guided first-run setup — create your account and connect your site in one step, nothing to copy.
Fix: more reliable connection and consent handling.
1.37.3
Fix: the “Default consent state” checkbox on Settings → Privacy now reflects the effective state. Previously a fresh install fell back to “denied” (privacy-safe default) while the checkbox showed unchecked — so browser pixels were silently suppressed with no visible cause. The box now shows checked whenever consent is defaulting to denied, and the description explains how to grant-by-default. No behavior change to consent resolution itself.
1.37.2
Fix: phone Lead-First now only hashes explicitly-international numbers (+CC / 00CC) client-side and emits both phone hashes (digits + E.164). Local-format numbers are deferred to the purchase event, where the country code is applied server-side — preventing a mismatched phone hash on lead events. Raw phone is never sent on a lead.
1.37.1
Maintenance: removed unused legacy files from the plugin package, reducing the download size. No change to functionality.
1.37.0
New: store owners can now control which LayerSync admin menu items appear, rename them, mark them “Soon”, reorder them, or add new links — managed centrally from the LayerSync dashboard.
New: on-page behavior signals (rage clicks, dead clicks, form errors, page speed) for Exit Doctor are now on by default, and only ever captured when the visitor has granted analytics consent.
Improve: “Sync customers” now shows a clear confirmation message when it finishes and a progress state while it runs, so it no longer looks like nothing happened. The optional website-activity sync also waits longer before timing out on a busy connection.
Improve: the plugin admin home no longer shows “all healthy” reassurance messages when nothing is wrong — status notices appear only when something needs attention.
Fix: when the plugin is reinstalled, a clear notice now explains if browser pixels are paused because consent defaults to denied, instead of failing silently.
1.36.0
Fix: external_id (WordPress user ID, SHA-256 hashed) is now sent with every server-side conversion event across Meta, TikTok, Pinterest, Microsoft, and all other connected CAPI platforms. Previously, the advanced-matching builder collected email, phone, name, and address but never emitted external_id, disabling cross-session matching and audience suppression for all logged-in users.
1.35.0
Performance: pages now load faster — the plugin no longer makes a blocking request for custom-tag and popup settings while your page renders. It serves a cached copy instantly and refreshes it in the background.
Performance: the popup script is now minified (about half the previous size) and only loads on your storefront when you actually have an active popup.
Accessibility: the plugin settings sub-tabs are now fully keyboard-navigable.
Admin: features that aren’t available yet are clearly labelled “Soon”.
1.34.1
Fix: Snapchat pixel advanced matching now sends the pre-hashed email/phone under the correct keys, so Snapchat no longer hashes them a second time — this restores Snapchat Pixel match rate, which was reading 0%.
New: the Reddit pixel now also sends the customer’s phone number for matching, improving Reddit match coverage.
1.34.0
New: custom tags and scripts you create in the LayerSync dashboard now run on your site automatically.
New: a “Managed in LayerSync” panel under Scripts lets you see, enable, disable, or delete those tags from WordPress (full editing stays in the dashboard; raw scripts still require LayerSync review before they go live).
Fix: the popup cart lookup no longer fails on sites installed in a subdirectory.
1.33.1
Fix: the popup no longer shows a “critical error” when a submission can’t be saved — it now shows a clear, friendly message instead.
1.33.0
Fix: more reliable event tracking — events are no longer occasionally dropped.
Fix: cookie-banner “Deny” choice is now respected on every event.
Fix: every completed order (including Block checkout and cash on delivery) records exactly one sale — no missed or double-counted purchases.
New: cart additions now show whether they were intentional or link-driven.
1.32.1
Fix: better customer matching on server-side purchases.
1.32.0
Improvement: stronger customer matching for ad platforms — especially guest and delayed orders. No extra personal data is stored.
1.31.12
Privacy fix: more personal details are removed when a visitor denies consent.
1.31.11
Fix: the Overview screen no longer appears twice.
1.31.10
Improvement: more stable admin pages — one error no longer breaks the whole screen.
1.31.9
Fix: better Google and Microsoft Ads tracking on iPhones.
1.31.8
Fix: Snapchat no longer double-counts page views.
1.31.7
Fix: Pinterest no longer double-counts events; better Google Ads matching.
1.31.6
Fix: Snapchat no longer double-counts add-to-cart and purchases.