PostBeagle for WooCommerce

PostBeagle for WooCommerce seamlessly integrates your WooCommerce store with PostBeagle email marketing platform. Allow customers to opt-in to your email list during checkout and automatically sync their information to PostBeagle.

Features

• Add opt-in checkbox to WooCommerce checkout
• Customize opt-in checkbox text
• Automatically sync opted-in customers to PostBeagle, tagged first-time vs. repeat
• Map WooCommerce order data to PostBeagle custom fields (incl. customer lifetime value and order count)
• One-time bulk import of existing customers with lifetime value
• WooCommerce automations: welcome, first purchase, repeat purchase, product purchased, abandoned cart, and win-back — each can tag the customer and trigger a PostBeagle automation
• Email capture anywhere: [postbeagle_signup] shortcode, Gutenberg block, and Elementor widget
• Form integrations: Contact Form 7, WPForms, Fluent Forms, and Gravity Forms (add contact, apply tags, trigger automations)
• Support for double opt-in workflows
• Abandoned cart recovery, revenue attribution and browsing-behaviour tracking are all off by default — you choose what data leaves your store (see External Services below)
• Comprehensive error logging and debugging
• Secure API key storage
• Never disrupts the checkout process

Requirements

• WordPress 5.8 or higher
• WooCommerce 8.9 or higher
• PHP 7.4 or higher (PHP 7.2+ with the sodium PECL extension, or PHP 7.2+ compiled with –with-sodium)
• PHP sodium extension (libsodium) — included by default in PHP 7.2+; required for secure API key encryption. The plugin will fall back to a weaker encoding method if sodium is unavailable, but this is not recommended.
• PostBeagle account with API access

External Services

This plugin is a client for PostBeagle, a third-party email marketing service. It sends data to https://api.postbeagle.com and does not function without a PostBeagle account.

Nothing is transmitted until you enter an API key and enable the plugin.

Always active once configured

• POST /api/contacts — when a customer ticks the newsletter opt-in checkbox at checkout (unchecked by default). Sends: email, first name, last name, tags, and any custom fields you have mapped (which may include order total, products, categories, lifetime value and order count).
• POST /api/events — automation events you have explicitly enabled (welcome, first purchase, repeat purchase, product purchased, win-back). Sends: email plus the relevant order or product data.
• GET /api/email-lists — retrieves your lists for the settings screen. Sends: no customer data.
• GET /api/suppressions/changes — retrieves unsubscribes so they can be honoured locally. Sends: no customer data.
• POST /api/webhooks/automation/{id} and POST /api/automation-recipes/install — used by the form integrations and the one-click automation setup button. Sends: email and tags.

Failed requests are retried from a local outbox table.

Off by default — you must enable these

• Abandoned cart recovery (Settings → Data Collection). In the recommended “capture during checkout” mode, the shopper’s email address is sent as they type it at checkout, together with their cart contents, before the order is placed. This is how abandoned cart recovery works, and it means personal data is processed before purchase — review your local privacy obligations before enabling. Switch to “only after a completed order” to avoid pre-purchase capture entirely, or turn on Privacy mode to capture only shoppers who ticked the opt-in checkbox. Endpoints: POST /api/events, GET /api/carts/{token}/snapshot.
• Revenue attribution (Settings → Data Collection). Reports every paid order — including orders from customers who did not opt in — so campaigns can be credited with the sales they drove. Sends: billing email, order id and number, total, currency, status, timestamp, coupon codes, and line items (product id, SKU, name, categories, quantity, price).
• Browsing behaviour (Settings → Data Collection). Sets a first-party pb_cid cookie (90 days, HttpOnly) when a subscriber clicks through from a PostBeagle email, so the visit can be credited to the campaign that sent it, and reports the products that visitor views to POST /api/events. Only visitors already identified by that cookie or by being logged in are tracked; anonymous visitors are never tracked. When this setting is off no cookie is written and no product views are sent — this is the plugin’s only use of cookies.

Terms and privacy

• PostBeagle Terms of Service
• PostBeagle Privacy Policy