Azimea

Description

Azimea is an external email marketing service. This free connector sends store events to Azimea; the service runs the email campaigns and customer journeys. An Azimea account and a connected store are required. Service usage is subject to the plan selected in Azimea; installing this plugin does not purchase a subscription.

Developed and supported by AZIMEA LABS S.R.L., Romania. Company details: https://azimea.com/en/about/. Contact: support@azimea.com.

Connect store activity to the campaigns and customer journeys you manage in Azimea. The connector collects cart changes and checkout events that are not available through the WooCommerce REST API, alongside customer and order updates.

What it sends

  • the cart, whenever it changes: products, quantities, prices, images, links, subtotal, total and a checkout link
  • the shopper’s email, the moment it is typed at checkout — on the classic checkout and on the block checkout
  • orders when they are placed and every time their status changes
  • customers when an account is created or updated
  • a marketing opt-in, if you choose to ask for one at checkout

What it does not do

  • no pixel, no third-party scripts, no tracking of people who are just browsing
  • anonymous carts include a cart token, products and totals; an email address is added only when known
  • no native WooCommerce webhooks, which have no retries and switch themselves off after five failures

How it sends

Nothing is sent during a shopper’s page load. Events go into a table of their own and travel on Action Scheduler, the scheduler WooCommerce already ships with, in batches of up to 100. If Azimea cannot be reached, the plugin retries after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours, then stops and says so on the settings screen. Some hosts block the scheduler’s background request to the site itself; if an event has waited more than a minute and a half with no retry pending, the next visit delivers it after the page has been sent (on hosts that cannot release the visitor first, it waits at most three seconds for Azimea and retries later). Every delivery is signed with HMAC-SHA256, so Azimea can tell your store from anyone else’s.

Consent

An email address entered at checkout is separate from marketing consent. In Azimea, the merchant chooses a checkbox, a notice, consent collected through another mechanism, or no marketing. The plugin displays the configured wording and sends the selected preference and the wording shown. A checkbox is never pre-ticked. The merchant must determine the appropriate notices and lawful basis for cart recovery and other emails in the jurisdictions where the store operates.

Checkout wording can be translated through WPML or Polylang. Use {privacy_policy} to link to the store’s privacy policy. For an existing consent field, configure its order metadata key or use the azimea_own_consent filter. Subscription events are associated with a placed order or account creation, rather than the public email-identification request. Configure double opt-in in Azimea where appropriate.

External service and privacy

The plugin connects to the Azimea service at https://t.azimea.com/e/v1. It sends event batches there and checks connectivity and the configured consent policy through /health. Requests also identify the store URL and plugin version. Developers can override the endpoint for a local test environment; the distributed plugin defaults to HTTPS.

Collection and delivery require saved store credentials. Events can include cart tokens, product identifiers, names, quantities, prices, images, links, totals, currency, locale, order identifiers and status, customer identifiers, email addresses and available customer details. Checkout identification can be sent before the shopper submits an order. Anonymous carts still include products and totals. The selected marketing preference and the displayed consent or notice text are included where applicable. The service uses these events for cart recovery, customer journeys and marketing according to the merchant’s settings.

The local queue keeps events until delivery; delivered events are removed. Failed events are eligible for scheduled cleanup after seven days. Cart recovery snapshots contain product selections and an email address when known and are eligible for cleanup 45 days after their last update. Scheduled cleanup must be running. Deactivation retains local data so that the integration can resume. Uninstallation removes the plugin’s local tables, settings and order metadata. It does not erase data already received by Azimea or delete WooCommerce orders and customers.

Review the suggested wording under WordPress Settings Privacy. Adapt your store’s notices and retention policy to its configuration. Handle access and erasure requests in both the store and Azimea; uninstalling this plugin is not a remote erasure request. The plugin does not determine whether a particular message is legally permitted.

For support, use the Support area in your Azimea account. Do not post signing secrets, API credentials or customer information in public support requests.

Installation

  1. Create an account at Azimea and connect your WooCommerce store in Integrations. The WooCommerce REST API consumer key and secret are used for that store connection.
  2. Install and activate this plugin alongside WooCommerce.
  3. Generate the separate plugin store key and signing secret in the Azimea integration screen.
  4. Open WooCommerce Settings Azimea, review the data-sharing description, paste the plugin credentials and save. Saving credentials enables event collection and delivery to Azimea.
  5. Press “Test connection”, then choose and declare your store’s consent method in Azimea. Review your checkout wording and privacy notice.
  6. Place a test order and verify its events in Azimea before enabling customer journeys. A sandbox store key sends events to the Azimea sandbox.

FAQ

Does it work with the block checkout?

Yes. Email capture uses a local script on the classic checkout and Store API hooks with a checkout data-store listener on the block checkout.

Does it work with High-Performance Order Storage?

Yes. The plugin declares compatibility with custom order tables and never reads order data out of wp_postmeta.

Where is the secret stored?

In the options table, and it is never shown again after saving. If you would rather keep it out of the database, define AZIMEA_STORE_KEY and AZIMEA_SECRET in wp-config.php; the settings screen then shows both as locked.

What ends up in the logs?

Codes and counts. No email addresses, no names, no secrets.

What happens when I delete the plugin?

The queue table, every option and the order keys the plugin added are removed.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Azimea” is open source software. The following people have contributed to this plugin.

Contributors

Translate “Azimea” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.2.2

  • Require a session-bound WordPress nonce on the cart recovery confirmation before changing the cart.
  • Escape the marketing notice when rendering it in classic and block checkout.
  • Reuse the existing WooCommerce session cookie when collecting a cart event after page output.
  • Avoid creating an unrepeatable cart token when a new session can no longer set its cookie.

1.2.1

  • Identify AZIMEA LABS S.R.L. as the developer and support provider.
  • Include publisher information and license text in distribution archives.

1.2.0

  • Renamed to Azimea. The plugin folder and text domain are now azimea.

1.1.1

  • Document the external service, transmitted data, account requirements and local retention.
  • Add suggested merchant privacy policy wording to WordPress.
  • Remove translated consent settings and block checkout consent metadata during uninstallation.
  • Bind custom table names through WordPress SQL identifier placeholders.

1.1.0

  • “See my cart” in a recovery email now rebuilds the cart in any browser or device, with the email filled in, and lands on the checkout. The link is signed and lasts 30 days; it carries products only, never an address or a login. The order placed from it closes the original abandoned cart.
  • After an order on the block checkout, no empty cart is announced any more under a new token.

1.0.0

  • First release: cart, contact, order, customer and subscriber events, on both checkouts.