Verified User in Hospital & Health Care
GH
Mid-Market (51-1000 emp.)
"Robust Consent Management, But Data Sync Lags"
4/5
What do you like best about Brevo Customer Data Platform?

What I value most about Brevo Customer Data Platform working at our Boise‑based Snake River Regional Health Network is its intuitive consent‑management dashboard built right inside the main workspace. We operate under strict HIPAA patient‑privacy requirements, and we only have part‑time shared technical support with no dedicated in‑house engineers. Many competing tools force you to rely on API work or outside specialists to adjust opt‑in and opt‑out logic, so having consent controls readily available for my team removes a huge amount of day‑to‑day pressure. Last spring, we rolled out our hypertension‑screening outreach initiative migrated over from our former Optimove environment. I imported thousands of patient records via CSV, and Brevo’s consent dashboard immediately surfaced a batch of profiles missing opt‑in and opt‑out metadata. If we had pushed the campaign live without fixing those records, we could have messaged patients who had formally opted out of non‑urgent notifications and triggered official HIPAA complaints. I cross‑checked those incomplete entries against our EHR source system and repaired their preference flags before activating our reminder workflow. I’m also very fond of its low‑code journey‑builder tool. Our care coordinators are clinical‑focused team members with very little marketing‑automation experience, yet they can build multi‑step patient outreach flows for post‑visit check‑ins and routine wellness prompts without writing any code. This lets them own parts of patient engagement instead of funneling every small campaign request over to me. That said, medical‑related custom‑field support still has real shortcomings; we cannot use chronic‑condition severity fields to create branching rules inside journeys, so I still need to build separate CSV audiences as a workaround. Even with that limitation, its accessible consent controls and no‑code workflow tools help our healthcare team cut down compliance exposure and distribute patient‑engagement work across our clinical group. Review collected by and hosted on G2.com.

What do you dislike about Brevo Customer Data Platform?

There are several real‑world frustrations with Brevo CDP that add heavy manual workload for our 201‑500‑person regional healthcare network. My biggest ongoing headache is poor native reporting support for healthcare‑relevant custom fields. We store vital patient details such as chronic‑condition severity, care‑program enrollment status, and follow‑up priority level within custom fields. Unfortunately, Brevo’s built‑in dashboards and campaign analytics cannot group, filter, or break down results using these medical attributes. After wrapping up our large‑scale diabetes‑screening campaign, which we planned after moving away from Optimove, I wanted to analyze how outreach performed across high‑risk, medium‑risk and low‑risk patient groups. There was no ready‑built report for this. I had to export massive CSV datasets and perform all my comparison work offline in spreadsheets, which burned hours of my time during our busiest preventive‑care outreach window. Another major pain point is the inadequate alerting during bulk CSV import jobs. Not long ago, I ran an import to update patient follow‑up priority flags pulled from our EHR. The platform returned a “completed successfully” status message, yet dozens of high‑risk patient profiles had their follow‑up‑priority custom values wiped to blank. Had I skipped manual spot‑checking, we would have sent low‑priority routine reminders to patients needing urgent clinical follow‑up, which could have created adverse patient outcomes. Brevo offered zero warning about these partial‑field failures, forcing me to go through hundreds of records one‑by‑one to catch the issue. On top of that, audit logging for bulk imports remains too high‑level for HIPAA compliance reviews. It only notes “an import occurred”, without logging which specific patient IDs were modified or overwritten. If a compliance audit requested traceability for patient‑data changes after a CSV upload, we would struggle to produce precise records without extra manual documentation. These gaps mean we cannot treat imports as “set‑it‑and‑forget‑it”; every file upload demands labor‑intensive manual validation from our team. Review collected by and hosted on G2.com.

See what 96 reviewers think of Brevo Customer Data Platform

4.6 out of 5 · Verified reviews from real users

Read all reviews