Connect your WooCommerce site to Casa Signals

How the connection works

Casa Signals connects to WooCommerce through the Customer Event Sync for Casa Signals WordPress plugin. The plugin tracks important WordPress and WooCommerce activity, queues the events inside WordPress, and sends them to Casa Signals in background batches.

The connection is authenticated with a site-specific API key. Each Casa Signals site has its own key, so the key must come from the same site record as the WooCommerce domain you are connecting.

Tracking is opt-in. Installing the plugin is not enough by itself. The API key must be saved, the site domain must be correct, and Enable event tracking must be switched on.

• Casa Signals site exists.
• WordPress plugin is installed and active.
• API key is pasted into the plugin.
• Event tracking is enabled.
• Recent activity appears in Casa Signals.

1. Add the WooCommerce site in Casa Signals

1. Open the Casa Signals dashboard

   Sign in to Casa Signals and open the dashboard. If this is the first store on the account, the dashboard will show the Add domain form.

2. Enter the store name

   Use a name your team will recognise, for example Example Store. This name is used throughout the dashboard and can appear in SMS previews when no approved Sender ID is active.

3. Enter the web domain

   Enter the live customer-facing domain, for example example.com. Do not include a checkout path, product path, wp-admin path, or tracking parameters.

   Use the same domain that customers use to browse and buy. If the store redirects from www to non-www, or the other way around, use the final public domain you want Casa Signals to treat as the store.

4. Save the domain

   Click Add domain. The site card will appear in the dashboard with links for Analytics, Customers, Products, Broadcasts, Flows, and Settings.

2. Generate the WordPress Plugin API key

1. Open the site settings

   From the Casa Signals dashboard, open the site card for the WooCommerce store and click Settings.

2. Find the WordPress Plugin panel

   In Settings, look for the Connection section named WordPress Plugin. This panel shows whether the store is connected, lets you generate or regenerate the API key, and includes the plugin download.

3. Generate the key

   Click Generate key. Casa Signals creates a new API key for this site. If a key already exists and you click Regenerate key, the old active key for that site is replaced.

4. Copy the key

   Click Copy and keep the key ready for WordPress. Treat it like a password. Anyone with the key can submit events for that Casa Signals site.

   • The copied key came from the same Casa Signals site as the WooCommerce store.
   • The site status shows Connected or an API key is visible.
   • The user has not copied a key from another domain.

3. Download and install the WordPress plugin

1. Download the connector

   In the same WordPress Plugin panel, click Download plugin. The file is named customer-event-sync-casa-signals.zip.

2. Upload it to WordPress

   In WordPress, go to Plugins -> Add New Plugin -> Upload Plugin. Choose customer-event-sync-casa-signals.zip, then click Install Now.

3. Activate the plugin

   After WordPress installs the plugin, click Activate Plugin. The plugin name is Customer Event Sync for Casa Signals.

4. Open the plugin settings

   From the WordPress Plugins screen, click the Settings link under Customer Event Sync for Casa Signals.

4. Configure the plugin in WordPress

1. Paste the API key

   In the API key field, paste the key copied from Casa Signals. If a key is already saved, WordPress shows a masked placeholder so the real key is not exposed in the settings form.

2. Confirm the site domain

   In Site domain, enter the same domain that was saved in Casa Signals. This is how incoming events are linked back to the correct site.

3. Enable event tracking

   Tick Enable event tracking. The plugin does not track or send customer events until this option is enabled.

4. Save changes

   Click Save Changes. From this point on, the plugin can set first-party visitor and session cookies, queue customer and store events locally, and send them to Casa Signals in the background.

   • Enable event tracking is checked.
   • API key is present.
   • Site domain matches the Casa Signals site.
   • WooCommerce is active.

5. Test the connection

1. Create a fresh customer event

   Open the storefront in a private browser window or a different browser. View a product, add it to the cart, view the cart, then start checkout.

   If possible, enter an email address and phone number at checkout. Customer SMS flows need a phone number on the event, and email flows need an email address.

2. Return to Casa Signals

   Open the site dashboard in Casa Signals. New activity can appear in analytics, customer timelines, product analytics, and live site activity.

3. Wait for background delivery

   The plugin queues events locally and sends them using WordPress background processing. A short delay is normal, especially if the site has low traffic or WP-Cron only runs when pages are visited.

4. Check the WordPress debug panel if needed

   If events do not appear, return to the WordPress plugin settings, enable Debug mode, save, perform another storefront action, then inspect the tracking queue and last background API response on the settings page.

6. Optional: import historical data

After the live connection is working, WordPress administrators can open Tools -> Casa Signals Import to import existing catalogue, user, and order data.

Imports are designed to be idempotent, so re-running an import should not duplicate the same historical records. Historical order events are marked as backfill and do not trigger SMS or email flows.

• Configure the API key first.
• Enable event tracking first.
• Run products, users, and orders imports when the store has enough time to process them.
• Do not use the import tool as a live-event test because imported events intentionally skip automations.

What Casa Signals starts tracking

Once enabled, the plugin can track product views, product searches, cart views, add-to-cart events, remove-from-cart events, cart quantity changes, checkout starts, checkout contact capture, checkout address updates, selected payment and shipping methods, order placement, successful payments, failed payments, refunds, cancellations, coupon activity, account registrations, logins, logouts, password resets, account updates, subscriptions, form submissions, attribution, and site health.

Casa Signals uses those events for analytics, customer timelines, product reporting, broadcasts, flow triggers, suppression checks, and revenue recovery attribution.

Best practices after connecting

• Make a real test purchase or payment test in your normal WooCommerce payment gateway test mode if available.
• Keep the API key private and regenerate it if it was shared outside your team.
• Check Analytics after the first day to confirm product, cart, checkout, and order events are arriving.
• Add a main domain email address in Settings before using email flows or broadcasts.
• Request an SMS Sender ID if you want customer SMS messages to show your brand name instead of the default sender.
• Create a cart abandonment flow only after add-to-cart or checkout events are visible.