Brevo Analytics and Reporting Limitations (2026)

Brevo sends across a lot of channels well. It reports on them shallowly, and in five different rooms. Email lives in Marketing > Statistics, automations in Automations > Workflows > Activity, transactional in its own Statistics tab, live chat in Conversations, and deals in Sales > Revenue. No single index shows all of it. The deeper analytics, like cohort retention, LTV curves and Purchase Timing Deviation, aren't in those reports at all. They live in the Customer Data Platform, a separately priced, quote-only product. The attribution layer Brevo rebuilt in April 2026 did add a multi-touch model, which is genuine progress. But the lookback windows are fixed per channel with no UI to change them, the model choice is gated to the top two plans, it only ever credits Brevo's own channels, and migrating to it reset the historical conversion data of everyone who moved over.

None of that is a product team failing. It is the shape of an ESP. The center of gravity is getting mail into an inbox, across as many channels as possible. The work that comes after the send, like comparing campaigns, finding patterns, attributing outcomes and deciding what to change next week, is a different product, and not the thing Brevo is built to be.

That's exactly why Sendlens exists: to give the marketer the context to analyze campaigns properly, so the next send is an improvement, not a guess.

The rest of this page walks through how Brevo handles analytics and reporting today, why the gaps aren't going to close from inside the product, and what Sendlens does to fill them without replacing your sender.

Inside Brevo, every campaign you have ever sent is a row in an unstructured list. You can filter by contact list, by segment, by channel, or by date, and depending on the channel the report lives on a different surface entirely. That is the whole grouping story. Nothing captures what each campaign actually was: newsletter or promotional, single-column or carousel, short or long, warm palette or cool, two CTAs or five. That structure does not exist in Brevo's data model.

Sendlens builds that structure at send time. Every email is vision-analyzed across fifteen-plus structured fields, including layout type, tone, CTA strength, density, palette, copy length and hero presence, so every campaign you send is automatically locatable in content-shape space. Similar campaigns cluster together, and performance is reported inside each cluster. That is the only way "this newsletter outperformed" actually means something.

Without that structure, Aura can only summarize what is already in the list. It cannot tell you which layout is winning, which CTA pattern is driving clicks, or which tone is burning out your subscribers, because Brevo does not store any of those attributes in the first place.

The only place inside Brevo where campaigns can be compared against each other is the aggregate Marketing > Statistics page, a date-range roll-up. It supports a period picker and aggregate rates, but it does not show time-series trends, does not support period-over-period comparison, and does not surface benchmarks inline. The numbers are correct. The shape you would actually want to see them in is absent.

The practical consequence: if you want "open rate trending week-by-week across my promotional campaigns only, compared to last quarter," you export a CSV and build it in Sheets. Most teams that need that view eventually stop asking for it.

Summary: Brevo reporting limitations and how Sendlens fills the gap

Brevo's analytics surface is broad at the base and deep only behind a paywall. It sends across more channels than almost anyone, and it reports the basics for each. But the reports are split across five product surfaces, the attribution engine it rebuilt in 2026 is still fixed-window and closed-loop, and the cohort, LTV, and Purchase Timing Deviation analytics live in a quote-only CDP most customers will never buy. Aura now lets you ask your numbers in plain language, but it does not make the numbers themselves any deeper.

If you want to keep using Brevo for what it is good at, and actually understand and improve the campaigns you are sending from it, Sendlens is the layer that makes that possible.

Further reading: the framing piece on why ESPs were never built for post-send understanding, why a sequence is a product, not a list, why you should benchmark against yourself instead of the industry, and why most email A/B tests don't teach you anything.