{"id":323751,"date":"2026-06-15T08:01:47","date_gmt":"2026-06-15T08:01:47","guid":{"rendered":"https:\/\/en-gb.wordpress.org\/plugins\/casa-signals-connector\/"},"modified":"2026-06-22T20:39:48","modified_gmt":"2026-06-22T20:39:48","slug":"casa-signals-connector","status":"publish","type":"plugin","link":"https:\/\/vec.wordpress.org\/plugins\/casa-signals-connector\/","author":23511283,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.3.6","stable_tag":"1.3.6","tested":"7.0","requires":"6.2","requires_php":"7.4","requires_plugins":null,"header_name":"Customer Event Sync for Casa Signals","header_author":"Code Casa Studios","header_description":"Syncs WordPress and WooCommerce customer events to Casa Signals. Replaces the legacy Domain Connections Tracker (post URL switched from data-collection-rev-comps.vercel.app to casasignals.com).","assets_banners_color":"0b1932","last_updated":"2026-06-22 20:39:48","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":83,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0":{"tag":"1.0","author":"sendemailtoday","date":"2026-06-15 08:01:38"},"1.0.0":{"tag":"1.0.0","author":"sendemailtoday","date":"2026-06-15 08:04:10"},"1.3.6":{"tag":"1.3.6","author":"sendemailtoday","date":"2026-06-22 20:39:48"}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3572582,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3572582,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3572582,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3572582,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0","1.0.0","1.3.6"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3572582,"resolution":"1","location":"assets","locale":"","width":4770,"height":2550}},"screenshots":[]},"plugin_section":[],"plugin_tags":[232,9430,29483,711,286],"plugin_category":[36,41,45],"plugin_contributors":[265958],"plugin_business_model":[],"class_list":["post-323751","plugin","type-plugin","status-publish","hentry","plugin_tags-analytics","plugin_tags-cart-abandonment","plugin_tags-customer-data","plugin_tags-sms","plugin_tags-woocommerce","plugin_category-analytics","plugin_category-communication","plugin_category-ecommerce","plugin_contributors-codecasastudios","plugin_committers-sendemailtoday"],"banners":{"banner":"https:\/\/ps.w.org\/casa-signals-connector\/assets\/banner-772x250.png?rev=3572582","banner_2x":"https:\/\/ps.w.org\/casa-signals-connector\/assets\/banner-1544x500.png?rev=3572582","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/casa-signals-connector\/assets\/icon-128x128.png?rev=3572582","icon_2x":"https:\/\/ps.w.org\/casa-signals-connector\/assets\/icon-256x256.png?rev=3572582","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/casa-signals-connector\/assets\/screenshot-1.png?rev=3572582","caption":""}],"raw_content":"<!--section=description-->\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<p>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.<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin connects to Casa Signals, a hosted analytics and automation service provided by Code Casa Studios. The service is required to receive WordPress and WooCommerce events, link them to the configured store domain, display analytics, build customer timelines, and trigger configured SMS or email flows inside the Casa Signals dashboard.<\/p>\n\n<p>When event tracking is enabled by an administrator, the plugin queues events locally and sends them to the Casa Signals events API at <code>https:\/\/casasignals.com\/api\/wordpress\/events<\/code> in background WP-Cron batches. The request includes the configured API key, the configured site domain, plugin version, and the queued event payload.<\/p>\n\n<p>Depending on the event, the payload can include event type, time, page URL\/path\/title\/referrer, visitor\/session identifiers from first-party cookies, browser user agent, coarse browser context such as language\/timezone, coarse location hints supplied by the site's CDN\/proxy headers, WordPress user profile fields, WooCommerce billing and shipping fields, cart details, product details, order totals, order status, payment failure details, coupon details, checkout field progress, attribution query parameters\/referrers, form provider metadata, and site health metadata such as WordPress version, locale, timezone, and plugin context.<\/p>\n\n<p>Data is sent when a supported store action happens, such as user login\/logout\/registration\/password reset\/account update, product view\/search, cart view\/change\/add\/remove, checkout start\/progress, order placed, payment success\/failure, refund\/cancellation, subscription events, coupon events, supported form submissions, and periodic site health reporting. Data is sent only when tracking is enabled and an API key is configured.<\/p>\n\n<p>Casa Signals Terms of Service: https:\/\/casasignals.com\/terms<\/p>\n\n<p>Casa Signals Privacy Policy: https:\/\/casasignals.com\/privacy<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>customer-event-sync-casa-signals<\/code> folder to <code>\/wp-content\/plugins\/<\/code>.<\/li>\n<li>Activate <code>Customer Event Sync for Casa Signals and WooCommerce<\/code> from the Plugins screen.<\/li>\n<li>Use the <code>Settings<\/code> link under the plugin name on the Plugins screen.<\/li>\n<li>Paste the WordPress API key from Casa Signals.<\/li>\n<li>Review the disclosure, then enable event tracking if you want the plugin to send store events to Casa Signals.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20this%20slow%20down%20checkout%20or%20page%20views%3F\"><h3>Does this slow down checkout or page views?<\/h3><\/dt>\n<dd><p>Events are queued locally first and sent to Casa Signals in background batches.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20track%20visitors%20immediately%20after%20activation%3F\"><h3>Does the plugin track visitors immediately after activation?<\/h3><\/dt>\n<dd><p>No. Tracking is off by default. A store administrator must add an API key and enable event tracking in the plugin settings before cookies are set or events are sent.<\/p><\/dd>\n<dt id=\"can%20i%20exclude%20administrator%20users%20from%20analytics%3F\"><h3>Can I exclude administrator users from analytics?<\/h3><\/dt>\n<dd><p>Yes. The plugin settings include an Administrator tracking checkbox. Untick it to stop logged-in WordPress administrators from being included in customer behavior analytics. Site health reports are still sent.<\/p><\/dd>\n<dt id=\"which%20events%20are%20tracked%3F\"><h3>Which events are tracked?<\/h3><\/dt>\n<dd><p>The connector can track user login, logout, registration, reset password, account updates, cart activity, checkout activity, order placed, payment successful, payment failed, refunds, cancellations, subscriptions, product views, product searches, coupons, supported form submissions, and site health signals.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.3.6<\/h4>\n\n<ul>\n<li>Added a setting to include or exclude logged-in WordPress administrator users from behavior tracking.<\/li>\n<\/ul>\n\n<h4>1.3.5<\/h4>\n\n<ul>\n<li>Rebuilt the connector with older-PHP-safe syntax around the new browser\/location context helpers.<\/li>\n<\/ul>\n\n<h4>1.3.4<\/h4>\n\n<ul>\n<li>Added coarse visitor location\/browser context for Casa Signals location analytics. The connector does not request precise browser geolocation.<\/li>\n<\/ul>\n\n<h4>1.3.3<\/h4>\n\n<ul>\n<li>Added browser user agent context for Casa Signals bot traffic analytics.<\/li>\n<\/ul>\n\n<h4>1.3.2<\/h4>\n\n<ul>\n<li>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.<\/li>\n<\/ul>\n\n<h4>1.3.1<\/h4>\n\n<ul>\n<li>Fixed double URL-encoding of the attribution cookies. Cookie payloads were being <code>rawurlencode<\/code>d by the plugin and again by PHP's <code>setcookie()<\/code>, 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.<\/li>\n<li>Landing-page attribution cookies now drop the query string. Click ids (<code>gclid<\/code>, <code>fbclid<\/code>, <code>msclkid<\/code>, <code>ttclid<\/code>) and <code>utm_*<\/code> parameters are already stored as their own touch fields, so no attribution is lost \u2014 the redundant URL representation just stops being carried on every subsequent request.<\/li>\n<\/ul>\n\n<h4>1.3.0<\/h4>\n\n<ul>\n<li>Renamed every PHP-level identifier (class, options, hooks, transients, AJAX actions, admin page slug, script handles, REST namespace) to a single <code>casasig<\/code> prefix, addressing the WordPress.org plugin review note about inconsistent prefixes (was a mix of <code>casa_signals_connector_*<\/code>, <code>casa_signals_*<\/code>, and the <code>customer-event-sync-casa-signals-*<\/code> slug).<\/li>\n<li>Upgrades from 1.2.x automatically migrate option values, queued events, and the cron schedule to the new prefix \u2014 no manual reconfiguration required.<\/li>\n<li>No functional or API changes; same events, same payload shape on the wire.<\/li>\n<\/ul>\n\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>New \"Casa Signals Import\" page under Tools for bulk importing existing products, users, and orders (with optional date range).<\/li>\n<li>Imports are idempotent \u2014 re-running is a no-op (products\/users upsert by natural key, orders deduplicated server-side via deterministic event ids).<\/li>\n<li>Imports are flow-safe \u2014 backfilled orders never trigger SMS\/email flows or flow recoveries, even when matching active flows exist.<\/li>\n<li>Resumable \u2014 progress survives tab close; click Run to continue from the last imported row.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Switched event API URL from data-collection-rev-comps.vercel.app to casasignals.com.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial WordPress.org-ready Customer Event Sync for Casa Signals and WooCommerce release.<\/li>\n<\/ul>","raw_excerpt":"Casa Signals tracks WooCommerce activity, customers &amp; revenue. Send Email &amp; SMS flows &amp; marketing for any scenario in one dashboard.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/323751","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=323751"}],"author":[{"embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/sendemailtoday"}],"wp:attachment":[{"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=323751"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=323751"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=323751"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=323751"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=323751"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/vec.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=323751"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}