Complete Guide to Brevo Integration with Tajo

Integrating Brevo with Tajo connects your customer data layer to your marketing and messaging platform.

Brevo is where many teams build email campaigns, SMS, WhatsApp messages, transactional messages, CRM workflows, lists, segments, and marketing automations. Tajo helps when those campaigns need current customer, order, product, loyalty, and engagement context from Shopify or other commerce systems.

The integration is valuable because marketing automation depends on clean, timely data. A welcome series can run from a basic email signup. A high-performing lifecycle program needs more context: first purchase date, order count, lifetime value, last product viewed, cart value, loyalty tier, consent status, support issues, and campaign engagement.

This guide explains how to plan, connect, test, and operate a Brevo integration with Tajo.

Quick Answer

Use this sequence:

1. Confirm the workflow you want to power in Brevo.
2. Decide the source of truth for contacts, orders, consent, product data, and loyalty fields.
3. Generate and secure the Brevo API key.
4. Connect Brevo in Tajo.
5. Select the objects and events to sync.
6. Map Tajo fields to Brevo contact attributes, lists, events, and ecommerce data.
7. Test with a small segment.
8. Build the first Brevo automations.
9. Validate consent, suppression, and unsubscribe behavior.
10. Monitor sync errors, duplicate contacts, and campaign performance.

Do not start by connecting every possible field. Start with the data needed for your first three workflows.

When to Use Each Integration Path

There are three common ways to connect Brevo with the rest of the stack.

Integration path	Best for	Watch-outs
Brevo native integration or plugin	Simple contact sync, basic ecommerce connection, quick setup	May not expose all data, events, or lifecycle logic needed for advanced segmentation
Tajo + Brevo	Shopify or customer-data-driven marketing, lifecycle automation, loyalty, segmentation, ecommerce triggers	Requires deciding field mappings, event rules, and workflow ownership
Custom Brevo API integration	Unique app logic, proprietary data model, custom events, internal systems	Needs engineering, monitoring, retries, security review, and maintenance

Use Tajo when you need Brevo to act on customer context, not just store contacts.

Examples:

• A Shopify customer places a second order and moves into a loyalty tier.
• A high-value customer abandons a cart after viewing a product category.
• A lapsed buyer should enter a win-back flow only if there is no open support issue.
• A post-purchase flow should change based on product category and order count.
• A VIP segment should receive a WhatsApp message only if channel consent exists.
• A customer should be removed from a nurture sequence after purchase.

Those workflows require synced data, event timing, consent, and suppression logic.

What Tajo Can Sync to Brevo

The exact configuration depends on your account, storefront, and integration setup, but the useful data categories are consistent.

Data category	Examples	Brevo use
Contact identity	Email, first name, last name, phone, external ID	Contact profile, deduplication, personalization
Consent	Email opt-in, SMS opt-in, WhatsApp consent, unsubscribe state	Compliance, suppression, channel eligibility
Customer lifecycle	New, active, repeat, VIP, at-risk, lapsed	Segmentation and journey routing
Ecommerce orders	Order ID, date, total, currency, products, categories	Post-purchase, replenishment, win-back, LTV segments
Product catalog	Product ID, name, category, price, status	Recommendations, product-specific messages
Cart and browse events	Cart value, product viewed, checkout started	Abandoned cart and browse abandonment
Loyalty data	Points, tier, rewards, expiry, milestones	Loyalty campaigns and tier-upgrade messages
Engagement data	Campaign opens, clicks, replies, events	Suppression, scoring, engagement segmentation
Custom attributes	Store-specific fields, tags, preferences	Advanced personalization and routing

Start with identity, consent, lifecycle, order history, and the events required for your first workflows. Add more fields only when they support a clear campaign or operational need.

Prerequisites

Before you connect Brevo and Tajo, confirm:

• You have a Tajo account with the relevant store or customer data source connected.
• You have a Brevo account with permission to create or use API keys.
• You know which Brevo lists, attributes, and templates will be used.
• You know the source of truth for email, phone, consent, and customer ID.
• You have admin access to Shopify or the commerce platform if ecommerce events are involved.
• You have a test contact and test order you can safely use.
• You know who owns the integration after launch.

Also define the first three workflows.

Good first workflows:

• Welcome series for new subscribers or customers.
• Abandoned cart recovery.
• Post-purchase education.
• Review request.
• Loyalty tier upgrade.
• Win-back or reactivation.
• VIP customer campaign.

Step 1: Define the Source of Truth

A source of truth is the system that wins when two systems disagree.

Define it before syncing.

Field or object	Recommended source of truth
Email address	Ecommerce platform or CRM, depending on acquisition path
Phone number	System where SMS consent was collected
Email consent	Consent collection source or preference center
SMS/WhatsApp consent	Consent collection source, never inferred from phone presence
Order history	Ecommerce platform
Product catalog	Ecommerce platform
Loyalty tier and points	Tajo or loyalty system
Campaign engagement	Brevo
Support status	Helpdesk or customer data layer

This prevents sync loops and data conflicts.

Example: if a customer updates their phone number in Shopify, Tajo can update Brevo. If Brevo has an older phone number, it should not overwrite the current commerce record unless you explicitly allow that direction.

Step 2: Generate a Brevo API Key

In Brevo:

1. Open account settings.
2. Go to API keys.
3. Generate a key for the Tajo integration.
4. Name it clearly, such as Tajo production sync.
5. Store it securely.
6. Do not paste the key into docs, spreadsheets, chat, tickets, or public code.

Use separate keys for production and testing when possible.

Recommended key practices:

• Limit access to admins who need it.
• Rotate keys after team changes or suspected exposure.
• Keep test and production credentials separate.
• Document who owns the integration.
• Revoke unused keys.

Step 3: Connect Brevo in Tajo

In Tajo:

1. Open integrations.
2. Select Brevo.
3. Add the Brevo API key.
4. Choose the store, CRM, or customer data source to sync.
5. Select the objects to sync.
6. Configure direction: Tajo to Brevo, Brevo to Tajo, or bidirectional for approved fields.
7. Save the connection.
8. Run a test sync.

Start with a limited set of test contacts. Confirm the data in Brevo before enabling full sync.

Step 4: Map Fields

Field mapping controls whether Brevo can segment and personalize correctly.

A practical starting map:

Tajo or store field	Brevo field or object	Notes
Customer email	EMAIL	Primary identity field
First name	FIRSTNAME	Used in personalization
Last name	LASTNAME	Used in personalization and CRM
Phone	SMS or phone attribute	Use only when consent and format are valid
Customer ID	External ID or custom attribute	Helps deduplicate and reconcile
Email opt-in	Email consent or list membership	Never assume consent from contact existence
SMS opt-in	SMS consent or custom attribute	Required before SMS campaigns
Order count	ORDER_COUNT	Useful for new vs repeat buyer segments
Lifetime value	TOTAL_SPENT or LTV attribute	Useful for VIP and suppression rules
Last order date	LAST_ORDER_DATE	Useful for replenishment and win-back
Loyalty points	LOYALTY_POINTS	Useful for reward reminders
Loyalty tier	LOYALTY_TIER	Useful for VIP and tier campaigns
Last product category	LAST_CATEGORY	Useful for recommendations
Customer lifecycle	LIFECYCLE_STAGE	Useful for journey routing

Use consistent naming. Avoid creating multiple attributes for the same idea, such as total_spent, TOTAL_SPENT, and LTV.

Step 5: Configure Events and Triggers

Campaign automation depends on events.

Common events:

• Contact created.
• Newsletter subscribed.
• Cart abandoned.
• Checkout started.
• Order completed.
• Order cancelled.
• Refund issued.
• Product viewed.
• Loyalty tier changed.
• Points earned.
• Reward redeemed.
• Customer became inactive.
• Support ticket opened.

For each event, define:

Event field	Why it matters
Event name	Used by Brevo workflow triggers
Customer identifier	Connects event to the right contact
Timestamp	Controls timing and delay logic
Properties	Adds order, product, loyalty, or cart context
Deduplication key	Prevents duplicate triggers
Consent state	Decides whether the event can trigger a message
Source	Helps debug where the event came from

Do not trigger campaigns from events until you verify that test events appear once, with the right contact and properties.

Step 6: Build the First Brevo Workflows

Welcome Series

Trigger: new subscriber, new account, or first customer sync.

Suggested flow:

1. Immediate welcome.
2. Brand story or value proposition.
3. Product, service, or loyalty explanation.
4. Social proof.
5. First purchase or next-step prompt.

Use Tajo data for:

• Customer source.
• Signup date.
• First product interest.
• Loyalty signup status.
• Channel consent.

Abandoned Cart Recovery

Trigger: cart abandoned or checkout started without order.

Suggested flow:

1. Email reminder after a short delay.
2. SMS reminder only if SMS consent exists.
3. Product-specific email with cart contents.
4. Final nudge or incentive if margin allows.

Use Tajo data for:

• Cart value.
• Product names.
• Product categories.
• Checkout link.
• Customer value.
• Prior purchase count.

For Shopify-specific implementation, read Brevo Shopify Integration and Shopify Abandoned Cart Email.

Post-Purchase Flow

Trigger: order completed.

Suggested flow:

1. Transactional confirmation.
2. Product education or care instructions.
3. Review request.
4. Cross-sell or replenishment reminder.
5. Loyalty points update.

Use Tajo data for:

• Product category.
• Order count.
• Loyalty tier.
• Points earned.
• Customer lifetime value.
• Support status.

Loyalty Tier Upgrade

Trigger: loyalty tier changed.

Suggested flow:

1. Congratulate the customer.
2. Explain new benefits.
3. Show current points or rewards.
4. Recommend the next action.
5. Suppress if customer has an open support issue.

Win-Back Flow

Trigger: customer inactive for a defined period.

Suggested flow:

1. Helpful check-in.
2. Recommendation based on past category.
3. Offer if margin allows.
4. Preference update.
5. Suppression if no response.

Use Tajo data for:

• Last order date.
• Last product category.
• Engagement status.
• Customer value.
• Recent support status.

QA Checklist Before Launch

Use this checklist before activating production workflows.

QA item	Pass condition
Contact sync	Test contact appears once in Brevo
Attribute mapping	All required fields populate correctly
Consent	Email, SMS, and WhatsApp eligibility is correct
Unsubscribe	Unsubscribed contacts are suppressed
Event delivery	Each test event arrives once
Event properties	Order, cart, product, and loyalty fields are present
Workflow trigger	Correct workflow starts from the test event
Exit rules	Customers exit after purchase or disqualifying condition
Suppression	Open support issues, refunds, and unsubscribes are respected
Personalization	Template variables render correctly
Links	Checkout, product, and preference links work
Reporting	Campaign and workflow metrics are visible
Error handling	Sync errors are logged and owned

Do not skip QA. Integration bugs create embarrassing customer experiences quickly.

Troubleshooting Common Issues

Duplicate Contacts

Common causes:

• Different identifiers are used in different systems.
• A phone-only contact later gets an email.
• Imports created contacts before sync was configured.
• Email normalization is inconsistent.

Fix:

• Pick a primary identifier.
• Normalize email casing.
• Use external IDs when available.
• Merge or suppress duplicates before large sends.

Missing Data in Brevo

Common causes:

• Field is not mapped.
• Source data is blank.
• API key lacks access.
• Sync job failed.
• The field type is incompatible.

Fix:

• Check the source record in Tajo or Shopify.
• Confirm the mapping exists.
• Confirm the Brevo attribute exists.
• Run a test sync.
• Check sync logs.

Workflow Does Not Trigger

Common causes:

• Event name mismatch.
• Contact does not exist yet.
• Event properties are missing.
• Workflow conditions are too strict.
• Delay or entry rules are blocking the contact.

Fix:

• Verify the exact event name.
• Send a test event.
• Check workflow enrollment.
• Temporarily simplify conditions.
• Confirm consent and suppression state.

SMS or WhatsApp Does Not Send

Common causes:

• No channel consent.
• Phone format is invalid.
• Country or sender rules are not configured.
• Contact is suppressed.
• Channel credits or account settings need review.

Fix:

• Validate phone format.
• Confirm consent source.
• Test with an internal number.
• Review Brevo channel settings.
• Confirm fallback email path exists.

Sync Delays

Common causes:

• Batch sync mode.
• API rate limits.
• Webhook delivery delay.
• Temporary vendor status issue.
• Large backfill job in progress.

Fix:

• Check sync status.
• Review rate limits.
• Confirm webhook delivery.
• Prioritize high-value events.
• Use batch sync for historical backfills and event sync for real-time campaigns.

Security and Compliance

Treat the integration as customer-data infrastructure.

Minimum controls:

• Store API keys securely.
• Limit admin access.
• Use separate test and production credentials.
• Respect email, SMS, and WhatsApp consent.
• Keep unsubscribe state synchronized.
• Avoid syncing unnecessary sensitive fields.
• Log sync failures.
• Document field ownership.
• Define who can create or activate workflows.

Do not pass customer data into campaigns just because it is available. Sync only data that supports a real workflow.

Metrics to Monitor

After launch, monitor both integration health and campaign results.

Integration health:

• Sync success rate.
• Sync error count.
• Duplicate contact rate.
• Event delivery latency.
• Failed webhook count.
• Unmapped field count.
• API error rate.

Campaign performance:

• Workflow enrollment.
• Email delivery.
• Open and click rates.
• SMS or WhatsApp response.
• Conversion rate.
• Revenue per workflow.
• Unsubscribes.
• Complaint rate.
• Repeat purchase rate.
• Loyalty engagement.

If campaign performance is weak, do not only rewrite copy. Check data quality, trigger timing, audience, consent, offer, and suppression logic.

Implementation Plan

Week 1: Plan and Connect

• Define first workflows.
• Choose source of truth.
• Create Brevo API key.
• Connect Brevo in Tajo.
• Map core contact fields.
• Run test sync.

Week 2: Add Events and Segments

• Configure order and cart events.
• Add lifecycle fields.
• Add loyalty fields if needed.
• Create test segments.
• Validate consent and suppression.

Week 3: Build Workflows

• Build welcome series.
• Build abandoned cart or lead recovery.
• Build post-purchase or loyalty flow.
• Test template variables.
• QA links and exit rules.

Week 4: Launch and Monitor

• Launch to a limited audience.
• Review sync logs daily.
• Check campaign metrics.
• Fix mapping issues.
• Expand audience after stability.

Final Recommendation

The best Brevo integration with Tajo is built around workflows, not fields.

Start with the customer journeys that matter most: welcome, cart recovery, post-purchase, loyalty, and win-back. Sync the data required for those journeys. Test carefully. Respect consent. Monitor errors. Then expand into richer segmentation and multi-channel automation.

Tajo is most valuable when Brevo needs more than a contact list. It gives Brevo campaigns the customer, ecommerce, loyalty, and lifecycle context needed to make automation timely, specific, and measurable.

Related Articles

• Brevo Shopify Integration
• Brevo Pricing 2026: Complete Plans, Features & Cost Breakdown
• Brevo Free Plan: Complete Guide to Getting Started
• Brevo Review 2026: Features, Pricing & Performance
• Brevo CRM: Complete Guide to Free Sales & Marketing CRM
• What is Brevo? Complete Guide to Brevo Email Marketing Platform