---
title: "WooCommerce + Brevo Integration"
description: "What Tajo can do with WooCommerce and Brevo today. Tajo reads WooCommerce store data, but a customer sync into Brevo cannot be published, because WooCommerce records no marketing opt-in."
url: https://tajo.io/docs/integrations/woocommerce-brevo/
markdown: https://tajo.io/docs/integrations/woocommerce-brevo.md
lang: en-US
---

# WooCommerce + Brevo Integration

| Source field | Destination field | Sample value |
| --- | --- | --- |
| `customer.email` | `not_mapped` | `alex@example.com` |
| `marketing_consent` | `unavailable` | `unknown` |

## WooCommerce + Brevo

Tajo has a WooCommerce connector. It reads customers, orders, products, product categories, coupons, refunds and product reviews through the WooCommerce REST API, with a consumer key and secret. It also receives WooCommerce webhooks, signed with HMAC, for orders, customers, products and coupons. The Tajo team sets up the keys with you. There is no self-serve key field yet.

## What You Cannot Do Today

A sync of WooCommerce customers into Brevo contacts cannot be published. WooCommerce records no marketing opt-in for its customers, so no customer can be shown to have agreed to marketing. Tajo refuses any rule that writes contacts to Brevo without that proof. Tajo does not read plugin data as consent.

## What You Can Do

If your sign-up form runs on Webflow, or your customers also buy on Shopify, those syncs carry consent into Brevo. See [Webflow + Brevo](https://tajo.io/docs/integrations/webflow-brevo) and [Shopify + Brevo](https://tajo.io/docs/integrations/shopify-brevo).

If you need WooCommerce data in Brevo, [tell the team](https://tajo.io/contact) where your store records marketing consent.

## Doing It Yourself

WooCommerce ships its own MCP integration, in developer preview. You turn it on with the `mcp_integration` feature flag, and it authenticates with WordPress application passwords. See WooCommerce’s [MCP documentation](https://developer.woocommerce.com/docs/features/mcp/) for the endpoint and the client setup.

Pair it with Brevo’s MCP server, described in [Brevo MCP Server](https://tajo.io/docs/mcp/brevo-mcp-server). The consent question does not go away in that setup: you are responsible for sending Brevo only people who agreed to marketing.

## Next Steps

- [Shopify + Brevo](https://tajo.io/docs/integrations/shopify-brevo)
- [Webflow + Brevo](https://tajo.io/docs/integrations/webflow-brevo)
- [Understanding data sync](https://tajo.io/resources/help/getting-started/understanding-data-sync/)