Skip to main content

Synchronize Newsletter Subscribers with Brevo - Article

Map consented Eurekos users to Brevo contacts, understand consent withdrawal and account changes, and verify the resulting marketing audience.
Updated: 14 Nov 2026
4 min read

Summary

Brevo integration can maintain a marketing audience from Eurekos users who have given Newsletter Consent. It reduces repeated contact maintenance while preserving the distinction between optional marketing communication and operational training messages. Configure the target attributes and consent lifecycle before using the synchronized audience for campaigns.

Use this article to:

  • Connect the intended Brevo account and map attributes
  • Understand who is included and what withdrawal changes
  • Verify contact creation, updates and removal
  • Keep marketing synchronization separate from System Emails

Use consented learning relationships for relevant follow-up

A training provider may want to send consenting partners product-learning news or information about relevant advanced offers. The learning platform already holds useful profile context, but having an account or completing mandatory training does not itself establish Newsletter Consent.

The Brevo flow creates a contact for a Eurekos user with Newsletter Consent = True and updates the supported mapped profile values when the user changes. Consent withdrawal removes the corresponding contact through the integration’s background processing. User deletion also triggers contact removal.

This is a marketing-contact synchronization. It does not configure Brevo as the transport for every Eurekos System Email or automatically define a campaign, audience segment or send schedule.

Prepare the target attributes first

Ask Eurekos to confirm integration activation and your configuration access. In Brevo, agree which contact attributes the business actually needs. The supported attribute types are Text, Date, Number and Boolean.

Create those attributes in Brevo before entering their names in Eurekos. Map a profile field to one appropriate target attribute; do not reuse the same attribute for several unrelated source fields. Keep data types compatible, particularly for dates and numbers.

For an illustrative partner program, company, job function and relevant profile information might support useful segmentation. Do not export every available personal field merely because it can be mapped.

Configure the Eurekos connection

Open Settings → Third party integrations → Brevo. Enter the intended account’s API key using the organization’s approved credential process. Expand Mapping of user profile fields to Brevo contact attributes and enter the exact Brevo attribute names for the required fields.

Review the complete mapping before Save. A saved field is not proof that the attribute exists or can accept its source value. The validation can report an invalid attribute while still retaining the entered mapping, so correct the issue and verify the actual contact.

After processing, inspect the target Brevo collection and open a representative contact. Custom attributes can be hidden in the Brevo contact layout; check attribute visibility before concluding that synchronization failed.

Understand the consent and connection lifecycle

ChangeDocumented integration behaviorOperating consequence
A user grants Newsletter ConsentThe contact is queued for creation or updateAllow background processing before checking the audience
A consented user updates mapped profile informationThe contact is queued for updateConfirm the intended source and target values
A user withdraws consent or is deletedThe corresponding contact is queued for removalVerify the downstream removal before treating the audience as current
Newsletter Consent functionality is disabled platform-wideContacts are queued for removal and the create/update queue is clearedTreat this as an audience-wide operational change
The Brevo API key is clearedThe integration is disabled and its local synchronization information is cleared; existing Brevo contacts are not deleted by that actionDisconnection is not the same as withdrawing consent or removing contacts

A connection change can therefore affect the audience differently from a user’s consent change. Plan migrations between Brevo accounts with the integration owner; do not assume that replacing or clearing a key cleans up the previous account.

Coordinate campaigns and operational messages

Use Brevo’s own campaign, segmentation and delivery tools for the marketing communication. Maintain the relevant consent and audience evidence with the people responsible for the program. In Eurekos, System Email schemes and training notifications remain separately configured under Email Sending.

Where the Newsletter Consent report is available, use it to review platform consent status alongside the actual downstream contact state. A platform report and a Brevo audience answer related but different questions; background processing or a mapping failure can explain a difference.

Verify the connection

Scenario or checkExpected result or evidence
A consenting representative userA corresponding contact has the intended mapped attributes
A user who has not consentedThe consent-based flow does not create that marketing contact
A supported profile updateThe target attribute changes after processing
Consent withdrawalThe corresponding contact is removed after processing
A missing displayed attributeContact layout visibility is checked as well as the mapping
A connection is disabledThe team understands that clearing the API key does not remove existing target contacts

Troubleshooting

ProblemWhat to check
A user is absent from BrevoNewsletter Consent, current API key, mapping validity and background processing
A profile value is absentExact attribute name, supported type, source value and contact-layout visibility
The form reports a mapping error but Save appears successfulCorrect the retained invalid mapping and verify a real contact
A withdrawn contact remains presentInvestigate removal processing and the actual connection/account with Support
Old contacts remain after disconnectingClearing the key is not a contact-deletion operation
Training emails appear unaffectedMarketing-contact synchronization and Eurekos System Email delivery are separate

Third Party Integrations

FAQ