Brevo Integration

In Brevo, go to your account menu > SMTP & API > API Keys, generate a v3 API key, and paste it into LeadSync when adding Brevo as a destination. LeadSync will pull every list across all your folders so you can pick the right destination for each lead source.

Update. LeadSync uses Brevo's updateEnabled flag, so when the same email submits your lead form twice, the existing contact is updated and re-added to the list. Your contact count stays clean and your reporting is not skewed by re-submissions.

EMAIL, FIRSTNAME, LASTNAME, and SMS map automatically from the standard fields on your lead ad form. PLATFORM and COMPANY are also populated when those fields are present. For any other attribute, use the field mapping screen to point lead form questions at custom Brevo attributes.

Yes. Use contact added to a list as the automation trigger -- every LeadSync-delivered lead is added to the destination list within seconds of form submission, so the automation starts immediately.

Yes. LeadSync cleans the phone number to Brevo's expected format (strips the leading + so it is a plain digit string) and writes it to the SMS attribute. The contact is immediately eligible for SMS campaigns from your Brevo account.

LeadSync mirrors the structure: when picking a destination list, the dropdown groups lists by folder so you can navigate large Brevo accounts without scrolling through hundreds of unsorted lists. The folder is purely for organisation; the contact lands on the list itself.

Use the field mapping screen in LeadSync to point each lead form question at the corresponding custom Brevo attribute. Brevo attributes are case-sensitive, so make sure the attribute name in your mapping matches exactly what you have configured in Brevo.

Yes. LeadSync supports Brevo as a destination for lead forms from Facebook, Instagram, Google Ads, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source becomes its own connection so you can route different ad platforms to different Brevo lists.

Each LeadSync connection points at a single Brevo list, but nothing stops you from creating multiple connections for the same lead source -- one per destination list -- and they will all fire in parallel for each new lead. This is useful when you want a lead to enter both a master audience and a campaign-specific list with different automations triggered by each.

Marketing contacts. LeadSync writes to Brevo's contacts endpoint with explicit list memberships, which puts each new lead in the marketing contact bucket -- the right place for nurture sequences, broadcast campaigns, and segmentation. Transactional emails (order confirmations, password resets) are a separate Brevo flow that does not affect a marketing contact's opt-in status.

No. Adding a phone number to the SMS attribute makes the contact eligible for SMS campaigns, but billing only happens when you actually send an SMS. So you can capture phone numbers from every lead without worrying about per-lead SMS charges.