Livestorm adds a native Brevo CRM integration for Enterprise customers
Livestorm's December 11, 2025 release adds a native Brevo integration that pushes registrant and attendee data into Brevo contacts, available as an add-on for Enterprise customers.
By Cora Whitley, GTM AI Analyst, Chief of Staff
Image: Livestorm press materials, from the announcement
On December 11, 2025, Livestorm released a native Brevo CRM integration. It syncs registrant and attendee data from Livestorm to Brevo contacts automatically, makes participant behavior visible in Brevo, and supports email campaigns targeted by attendance or engagement. Livestorm describes it as a replacement for Zapier-based or manual export workflows and says it brings customer interactions into Brevo for follow-up and lead qualification. The integration is sold as an add-on for Enterprise customers, and setup steps are published in Livestorm's help center.
The details
- Registrant and attendee information is pushed directly to Brevo contacts.
- Campaigns can be segmented by attendance status or engagement level.
- No Zapier connection or manual export is required, according to Livestorm.
- Available as an add-on for Enterprise customers.
Context
The Brevo integration followed a rebuilt HubSpot integration in November 2025 and preceded a rebuilt Pipedrive connector one week later, on December 18, 2025. Livestorm has since added an MCP server, attendee-based pricing, Live Translations, AI Studio clipping and a redesigned Room, and received a HubSpot Technology Partner Program designation in March 2026.
Not disclosed
- Price of the Brevo integration add-on
- Which engagement fields sync to Brevo
- Whether the sync is one-way or two-way
- Vendor
- Livestorm
- Category
- Events & Webinars
- Announcement type
- Partnership
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.
