Delvaro for WooCommerce

Delvaro for WooCommerce connects your WooCommerce store to Delvaro’s powerful marketing automation platform. Automatically track customer behavior and trigger personalized email campaigns based on real shopping activity.

Key Features

• Automatic Event Tracking – Product views, cart additions, checkout starts, and order completions are tracked automatically
• Server-Side Order Tracking – Reliable order tracking that works even when customers close their browser
• Customer Identification – Links anonymous browsing activity to customer profiles when they purchase
• Easy Setup – Just enter your API keys and you’re ready to go
• WooCommerce Native – Integrates seamlessly with WooCommerce settings

Tracked Events

Client-Side Events (Browser):
* page_view – Every page visit on your store
* view_product – When a customer views a product page
* add_to_cart – When items are added to the cart
* started_checkout – When a customer begins the checkout process

Server-Side Events (Reliable):
* placed_order – When an order is placed
* fulfilled_order – When an order is marked as completed
* refunded_order – When an order is refunded
* cancelled_order – When an order is cancelled

Use Cases

• Abandoned Cart Recovery – Automatically email customers who leave items in their cart
• Post-Purchase Follow-ups – Send review requests or cross-sell recommendations after purchase
• Browse Abandonment – Re-engage customers who viewed products but didn’t add to cart
• Customer Segmentation – Build segments based on purchase history and browsing behavior

Requirements

• WordPress 6.0 or higher
• WooCommerce 8.0 or higher
• PHP 7.4 or higher
• A Delvaro account (Sign up free)

External services

This plugin connects your store to Delvaro, a marketing automation service. A Delvaro account is required, and the plugin does nothing until you connect one. All five endpoints below belong to Delvaro and are covered by the same Terms of Service and Privacy Policy.

1. Event tracking (https://t.delvaro.ai)

Receives the shopping events that drive your automations. Sent from your server when an order is placed, fulfilled, refunded, or cancelled, and from the visitor’s browser on page and product views, cart additions, and checkout starts. Browser events follow the visitor’s cookie consent; see Privacy & consent below.

Data sent: page URLs visited, product details (ID, name, price, category), cart contents, order details (order total, items purchased, currency, and for fulfilled orders the carrier, tracking number and tracking link), and the customer’s email address and billing details so the order can be matched to a contact. Payment card details are never transmitted.

2. Tracking script (https://cdn.delvaro.ai)

Serves delvaro-loader.js, the browser tag that records the client-side events above. It is loaded from Delvaro’s CDN rather than bundled with the plugin because it is the service’s own tag: it is versioned and updated server-side in step with the tracking API, and a stale bundled copy would send events the API can no longer accept. It is only enqueued once you have entered a public API key.

Data sent: the standard information any browser request carries (IP address, user agent, referring page) plus your public API key, which identifies which workspace the events belong to.

3. Reviews configuration (https://b.delvaro.ai)

Fetched by your server to find out whether the Reviews add-on is active for your workspace and how review widgets should be displayed. Requested when a page containing reviews is rendered, and cached.

Data sent: your public API key only. No customer or order data.

4. Workspace API (https://api.delvaro.ai)

Used for five operations, each triggered by a specific action:

• /lists – fetches your subscriber lists so you can pick one in the settings screen. Requested when you open the Delvaro integration settings.
• /products/trigger-sync – asks Delvaro to fetch your product catalog. Requested once after you connect your store.
• /v1/products – sends updated product details (price, stock status, title and URL) when a product’s stock status or price changes, so back-in-stock and price-drop flows start promptly.
• /reviews/summary – retrieves review counts and average ratings so they can be added to product schema. Requested when a product page is rendered, and cached.
• /contact/register – registers a customer who opted in to marketing at checkout. Requested only when the consent checkbox is enabled and a customer ticks it: when they place the order, or, if they ticked it themselves, when they leave the checkout page without ordering. In that second case your server also sends a checkout event with their cart to the event tracking endpoint above.

Data sent: your API key and store URL on every request. /contact/register additionally sends that customer’s email address, name, phone number and billing country, and their consent audit trail – the exact checkbox text they agreed to, the timestamp, and their IP address – which is retained as proof of consent for GDPR, CAN-SPAM, and CASL purposes. The other four endpoints send no customer or order data.

5. Account connection (https://delvaro.com)

Handles the OAuth handshake that links your store to a Delvaro workspace, via /api/oauth/authorize, /api/oauth/token, and /api/oauth/revoke. Used when you click “Connect to Delvaro” in the settings screen, and when you disconnect.

Data sent: your store URL and the OAuth authorization code. No customer, order, or product data.

Privacy & consent

Once you have connected a Delvaro account, the tracking script stores the following in the visitor’s browser. Everything is first-party, set on your store’s own domain:

• delvaro_uid and delvaro_user_id (cookies, 1 year, marketing) – random visitor IDs that connect page views, product views and cart activity from the same browser, for store analytics and marketing automation.
• delvaro_identity (cookie, 90 days, marketing) – an encrypted token from a Delvaro email or SMS link, so the visit can be attributed to the subscriber who clicked it.
• delvaro_email (cookie, 1 year, marketing) – the email address the shopper signed in or checked out with, used to trigger messages such as abandoned-cart reminders.
• delvaro_form_* (local storage, marketing) – which Delvaro sign-up forms and popups were shown, closed or submitted, so they are not shown again too often.
• delvaro_consent_v1 (local storage, functional) – the visitor’s tracking consent choice, so it is respected on later visits.
• delvaro_marketing_consent (cookie, 1 hour, functional) – only when the checkout opt-in box is enabled; remembers whether it is ticked so the choice is saved with the order.

With a consent plugin

The plugin supports the WP Consent API, which is used by Complianz, CookieYes, Cookiebot, Borlabs and other consent plugins. With the WP Consent API and a compatible consent plugin installed:

• The storage listed above is registered with your consent plugin for its cookie banner and cookie policy.
• Each visitor’s statistics and marketing choices are passed to the tracking script. Because the same events feed your reports and your marketing automation, a visitor is only tracked when they allow both; withdrawing either stops tracking and removes Delvaro’s tracking cookies. Changes made in the banner apply straight away, without reloading the page.
• Without marketing consent, the plugin also stops passing the signed-in customer’s email address to the tracking script and does not link orders to the browser’s visitor ID.

Without a consent plugin

The plugin sends no consent signal, and the tracking script applies its own privacy defaults: it honours Global Privacy Control and, where present, IAB TCF or Google Consent Mode signals from other consent tools, and otherwise waits for consent in regions that require it (such as the EU, EEA, UK and Switzerland). If you sell to visitors in the EU or UK, install a consent plugin that supports the WP Consent API.

Server-side data

Order events (placed, fulfilled, refunded, cancelled) are sent from your server to Delvaro as described under External services. They do not read or store anything in the visitor’s browser, so cookie consent does not affect them; they are covered by your store’s privacy policy, which should name Delvaro as a service provider. A customer is only added to a subscriber list when they tick the marketing opt-in box at checkout.