Brevo landing page installation
Add Testimonials to Brevo Landing Pages
Brevo (formerly Sendinblue) builds landing pages with a drag and drop editor that has a Code element, and a Tracking panel in its settings that injects scripts into the head or body of the page. Put the widget div in the first and the script in the second, then publish to see it.
- The div for a Code element
- The script for the Tracking panel
- A one spot version for a single widget
Brevo code
Code for the Code element and the Tracking panel
Fill in the widget id. The usual install is Part 1 plus Part 2. Part 3 is an alternative for a page with one widget, where you would rather keep everything in the Code element.
Part 1 · Code element where testimonials should appear
Landing page editor › drag the Code element onto the page › paste
<div data-storyproof-widget="YOUR_WIDGET_ID"></div>Part 2 · Script for the whole landing page
Settings (bottom left) › Tracking › before the closing body tag
<script src="https://app.storyproof.io/embed.js" async></script>Part 3 · Alternative: both lines in one Code element
Landing page editor › Code element
<!-- Only if this landing page has a single widget and you prefer one spot -->
<div data-storyproof-widget="YOUR_WIDGET_ID"></div>
<script src="https://app.storyproof.io/embed.js" async></script>Brevo says code in the editor can only be tested on published landing pages. Publish, open the page URL in a private window, and check it there.
Typing an id here only rewrites the snippets on this page. It is not stored.
The problem, solved
Brevo landing pages and testimonials: common snags
- Problem 1
I used the email HTML block approach
Brevo’s email editor has its own HTML block, but scripts do not run in most inboxes, so habits from email design do not carry over to pages.
How StoryProof solves it
On a landing page the StoryProof embed is a div and an async script, which fit the Code element and the Tracking panel built for exactly that.
- Problem 2
Two widgets, a script in each
Pasting the full snippet into two Code elements loads the same script twice on one page.
How StoryProof solves it
Load the script once from Tracking and leave only divs in the Code elements. One embed.js fills every StoryProof widget on the page.
- Problem 3
Nothing shows while I edit
The editor does not run custom code, so the Code element looks empty and it is tempting to keep pasting.
How StoryProof solves it
Leave the div in place, publish, and check the live page. Pick a layout in StoryProof that suits the column width you gave the element.
- Problem 4
Event page needs proof from last time
A registration page for a repeat workshop or webinar sells better with words from people who came before, but those comments sit in old replies.
How StoryProof solves it
Share your collection link or QR code with past attendees, approve what comes back, and choose those testimonials for the page’s widget.
In StoryProof
Install it in Brevo
Step 1 of 4
Prepare the widget
In StoryProof, approve testimonials, choose which ones this widget shows and pick a layout for the page’s width.
Step 2 of 4
Place a Code element
Drag the Code element to where proof should sit, select it, and paste Part 1. Brevo documents the element in both its new and classic editors.
Step 3 of 4
Add the script in Tracking
Click Settings in the bottom left corner of the editor, open Tracking, and paste Part 2 into the field for code before the closing body tag. Save.
Step 4 of 4
Publish and test
Publish the page, then load its live URL on desktop and phone. If the Code element is still empty, confirm the script was saved in Tracking for this page.
Which Tracking position for the script?
Before you start
Brevo limits
Paid plans and page counts
Brevo’s pricing lists landing pages from its Standard plan, with a small number included. Check your plan before building several pages.
Publish to test
Code in the editor can only be tested on a published landing page, according to Brevo. Allow time for a publish and check cycle.
Help read through search
Brevo’s help center blocked automated reading on 2026-11-13, so the Code element and Tracking steps rest on search excerpts of its articles. Confirm the labels in your editor.
If the Code element strips scripts
Brevo does not document what the Code element does with script tags, which is one reason Part 2 lives in Tracking. If a page still shows nothing, link to your Wall of Love instead.
Badge, and docs dated 2026-11-13
Widgets show a "Powered by StoryProof" badge until Pro. Steps follow Brevo’s help as found on 2026-11-13 and have not yet been tried on a live Brevo page.
FAQ
Questions people ask
Short answers to what usually comes up next.
Does the script in Tracking affect my other Brevo landing pages?
Tracking is opened from inside the landing page editor, so treat it as a per page setting and add the script to every page that has a StoryProof widget.
Is this the same in the classic landing page editor?
Brevo describes the Code element as available in both the new and classic editors. Menu positions may differ slightly.
Can I show the widget in a Brevo email?
No. Email clients do not run the widget script. Link to your Wall of Love from the email instead.
Is there a Brevo integration that pulls testimonials in?
No. StoryProof reaches Brevo landing pages only through this embed code.
Still have a question? Ask the StoryProof team or book a demo.
Bring real testimonials to your Brevo pages
Collect and approve them in StoryProof, then add one Code element and one Tracking script.
Sources
- Add a Facebook comment section to your landing page (Code element, Tracking settings), Brevo Help Center. Checked 2026-11-13.
- Landing pages, Part 4: Add a form to your landing page and use advanced options, Brevo Help Center. Checked 2026-11-13.
- Brevo pricing (landing pages by plan), Brevo. Checked 2026-11-13.
Last updated 2026-11-13.