Salesforce Commerce Cloud + Brevo Integration
Illustration · sample data
Sync example
Source
Salesforce Commerce Cloud
Connector status: Planned
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.
Salesforce Commerce Cloud + Brevo
Tajo has a Salesforce Commerce Cloud (SFCC) connector. It reads products, orders and customers through SFCC’s API, with an access token. The Tajo team sets up the token with you. There is no self-serve sign-in yet.
What You Cannot Do Today
There is no SFCC template and no sync of SFCC customers into Brevo contacts. Tajo has no consent policy for SFCC, 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 SFCC webhooks.
What You Can Do
If you are moving from SFCC to Brevo, or need SFCC data in Brevo, tell the team what you want to send and where your customers’ marketing consent is recorded.
Doing It Yourself
Salesforce publishes an MCP server for B2C Commerce, @salesforce/b2c-dx-mcp. It is a developer tool for building on the platform, not a way to read your customers or orders. See Salesforce’s B2C developer tooling documentation.
Brevo’s own MCP server is described in Brevo MCP Server.