On This Page
A customer checks the marketing box at Shopify checkout. Their order appears, but their email address is missing from the Brevo list you expected. The next move is to check the connection, the list, and the customer’s consent status, in that order. Re-exporting every customer would hide the actual failure.
Connect Shopify to Brevo
Brevo’s current Shopify route is the Brevo PushOwl app. Its documentation says the app can sync existing and new customers, products, collections, and orders. It also describes onsite tracking and automations for welcome messages, browse abandonment, back-in-stock notices, and abandoned carts. Those are native capabilities; the old claim that the native connection handles contacts and little else was wrong.
If you are starting without a Brevo account, install Brevo PushOwl from the Shopify App Store, accept the requested permissions, and use Enable now in the app to turn on its theme integration. Brevo says data sync begins during this setup. Finish the app’s onboarding before creating a campaign. Already have a Brevo account? Use Brevo’s migration instructions instead of treating this as a fresh installation. That path asks you to select a Brevo list, review how Shopify customer fields map to Brevo attributes, and confirm the historical sync. Brevo warns that historical sync makes Shopify the source of truth for customer data and may overwrite existing Brevo attributes. Decide which system owns each field before you confirm.
Check fields and consent before sending
Pick one test customer whose email marketing choice you can inspect in Shopify. Compare their email address, first name, and any field your campaign needs with the resulting Brevo contact. Then inspect a test order separately. A contact appearing in Brevo does not prove that an order, event, or marketing permission arrived correctly.
Keep the mapping small. Email identifies the contact; name personalizes a message. Add purchase or custom fields only when a specific campaign needs them. For each field, record its source, destination, and conflict rule. Brevo’s migration flow offers a Review mapping step. Use it before the historical sync rather than discovering a wrong destination after it updates your list.
Use this as a review worksheet, not a claim that every field has a configurable setting in the app:
| Data | Check before syncing | Acceptance check |
|---|---|---|
| Which record identifies this customer? | One intended contact, without a duplicate | |
| First name | Should an empty source value clear a saved name? | The chosen rule survives a second sync |
| Marketing permission | Which channel and consent record apply? | A non-subscriber stays out of promotional sends |
| Order event | Which store and event does the automation expect? | The test order reaches the intended trigger once |
Consent needs its own check. Shopify’s marketing guidance distinguishes a customer record from agreement to receive promotional messages. Shopify lets customers opt in through store forms, checkout, or account sign-in; email and SMS have separate settings. Inspect the customer’s relevant marketing status in Shopify and the resulting subscription or blocklist state in Brevo. A purchase alone is no instruction to send a promotion. If you use double opt-in, wait for confirmation before treating the address as subscribed.
Use two test records if you can: one with the relevant marketing consent and one without it. The first should reach the intended audience; the second must stay out of promotional sends. Do not infer permission for SMS or WhatsApp from an email opt-in. Use the consent records and your sending policy when configuring campaigns.
Verify the flow and locate a failure
After setup, check a new subscriber and a new order in both systems. Record the Shopify customer or order identifier, the event time, and the matching Brevo contact or ecommerce record. Brevo documents synced products, orders, and store events. Test only the event your first campaign needs. Do not test unrelated events yet.
If a contact is missing, check that the app is installed and authorized, the intended Brevo list is selected, and the customer meets the subscription conditions you configured. If the contact exists with empty or unexpected attributes, revisit the mapping and source values. If an automation does not fire, inspect whether its trigger event reached Brevo, whether the contact qualifies for the audience, and whether the automation is active. Change one setting at a time and repeat the test.
Before activation, replay the same test input where the chosen route permits a controlled replay. Verify one contact and one intended order outcome, then test an older signup after a later unsubscribe. Preserve the opt-out. Record the source and destination identifiers with each result; a repeated contact write must not become a repeated marketing send.
Do not enable a marketing workflow after only seeing a green connection indicator. Verify a real record, its consent state, and one intended trigger first. Keep the test identifiers to distinguish fresh events from historical data.
When a custom connection earns its place
The objection is reasonable: “If PushOwl already syncs customers and orders, why build another connection?” Usually, you should not. Start with the documented app and test the field and event you need.
A custom path makes sense when a concrete requirement still fails that test: perhaps a field has no suitable mapping, two stores need different ownership rules, or your consent handling needs a reviewed transform. Write the missing source, destination, and acceptance check before choosing software. Then test the proposed mapping and approve it before activation. Our Shopify and Brevo integration docs discuss the data model; the Brevo connector guide covers broader connection choices. If your signup begins outside Shopify, see the Webflow to Brevo guide.
Tajo is in early access, starting with Shopify, Webflow, and Brevo. Bring the field that will not map, the consent rule that must survive, and the record that proves the failure. Ask for a demonstrated test against that requirement before replacing a working native setup.
One verified connection is enough to start.
Frequently Asked Questions
How do I connect Shopify to Brevo?
For a new Brevo setup, install Brevo PushOwl from the Shopify App Store, accept its permissions, enable it in your theme, and complete onboarding. If you already use Brevo, follow Brevo's migration guide before changing the connection.
Will every Shopify customer become a marketing subscriber in Brevo?
Do not assume so. Check the customer's email or SMS marketing consent in Shopify and the resulting status in Brevo before sending a campaign. A customer record and permission to market are separate things.
When would I need a custom Shopify to Brevo connection?
Start with Brevo PushOwl. Consider a custom connection only when a required field, consent rule, or workflow remains unsupported after testing the current app. Document the gap and test the proposed mapping before activation.