Customer Event Sync for Casa Signals

Customer Event Sync for Casa Signals and WooCommerce connects your WordPress/WooCommerce store to Casa Signals, giving you live customer activity tracking, analytics, customer timelines, product insights, attribution, flow automation, broadcasts, and revenue recovery reporting. After you add your Casa Signals API key and explicitly enable tracking, the plugin queues supported store events locally and sends them to Casa Signals in background batches. It can track WooCommerce and WordPress signals such as registrations, logins, logouts, account updates, product views, cart activity, checkout progress, orders placed, payment successes, payment failures, refunds, cancellations, coupons, form submissions, attribution data, customer details, product details, and site health signals. Casa Signals then turns those events into a site-by-site dashboard where store owners can understand customer behavior, diagnose checkout/payment problems, build SMS and email flows, send broadcasts, view customer timelines, and measure recovered revenue.

1.3.6

• Added a setting to include or exclude logged-in WordPress administrator users from behavior tracking.

1.3.5

• Rebuilt the connector with older-PHP-safe syntax around the new browser/location context helpers.

1.3.4

• Added coarse visitor location/browser context for Casa Signals location analytics. The connector does not request precise browser geolocation.

1.3.3

• Added browser user agent context for Casa Signals bot traffic analytics.

1.3.2

• Added admin UI translations for German, French, Italian, Dutch, Polish, Romanian, Bulgarian, Greek, Estonian, Finnish, Croatian, Lithuanian, Latvian, and Russian. Spanish was already shipped in 1.3.0.

1.3.1

• Fixed double URL-encoding of the attribution cookies. Cookie payloads were being rawurlencoded by the plugin and again by PHP's setcookie(), inflating the Cookie header ~40% and pushing some Facebook-sourced visitors past the nginx Cookie size limit (431 Request Header Fields Too Large). Cookies written under earlier versions are detected and migrated in place on the next request.
• Landing-page attribution cookies now drop the query string. Click ids (gclid, fbclid, msclkid, ttclid) and utm_* parameters are already stored as their own touch fields, so no attribution is lost — the redundant URL representation just stops being carried on every subsequent request.

1.3.0

• Renamed every PHP-level identifier (class, options, hooks, transients, AJAX actions, admin page slug, script handles, REST namespace) to a single casasig prefix, addressing the WordPress.org plugin review note about inconsistent prefixes (was a mix of casa_signals_connector_*, casa_signals_*, and the customer-event-sync-casa-signals-* slug).
• Upgrades from 1.2.x automatically migrate option values, queued events, and the cron schedule to the new prefix — no manual reconfiguration required.
• No functional or API changes; same events, same payload shape on the wire.

1.2.0

• New "Casa Signals Import" page under Tools for bulk importing existing products, users, and orders (with optional date range).
• Imports are idempotent — re-running is a no-op (products/users upsert by natural key, orders deduplicated server-side via deterministic event ids).
• Imports are flow-safe — backfilled orders never trigger SMS/email flows or flow recoveries, even when matching active flows exist.
• Resumable — progress survives tab close; click Run to continue from the last imported row.

1.1.0

• Switched event API URL from data-collection-rev-comps.vercel.app to casasignals.com.

1.0.0

• Initial WordPress.org-ready Customer Event Sync for Casa Signals and WooCommerce release.