BigCommerce + Brevo Integration
Illustration · sample data
Sync example
Source
BigCommerce
Connector status: In progress
Destination
Brevo
Connector status: Live
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
customer.email | not_mapped | [email protected] |
marketing_consent | unavailable | unknown |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
BigCommerce + Brevo
Tajo has a BigCommerce connector. It reads customers, orders, products and addresses through the BigCommerce REST API, with your store hash and an API access token. The Tajo team sets up the token with you. There is no self-serve token field yet.
What You Cannot Do Today
A sync of BigCommerce customers into Brevo contacts cannot be published yet. Tajo has no consent policy for BigCommerce, so it cannot show that a customer agreed to marketing. Tajo refuses any rule that writes contacts to Brevo without that proof.
Tajo does not receive BigCommerce webhooks.
What You Can Do
If you need BigCommerce data in Brevo, tell the team where your store records marketing consent. That is the piece a BigCommerce sync is missing.
Doing It Yourself
BigCommerce has an MCP server in beta. It is a storefront server: it searches the catalog, manages carts and hands off to checkout for shoppers. It does not read your customer list, so it cannot feed a sync into Brevo. See BigCommerce’s MCP documentation.
Brevo’s own MCP server is described in Brevo MCP Server.