ActiveCampaign Pages installation
ActiveCampaign Landing Page Testimonials Embed
ActiveCampaign asks you to keep JavaScript out of its page editor. HTML goes in an Embed block; scripts go in the page’s Custom Code settings, which only take effect on the published page. The StoryProof embed splits cleanly along that line.
- The div for an Embed block
- The script for Custom Code, body field
- Why the builder shows an empty block until you publish
Two part embed
One part for the block, one for Page Settings
Enter your widget id. Part 1 is HTML only and goes in an Embed block where the testimonials should appear. Part 2 is the script and goes in the body field of the page’s Custom Code tab.
Part 1 · Embed block in the page layout
Page builder › drag an Embed block › click it › code editor
<div data-storyproof-widget="YOUR_WIDGET_ID"></div>Part 2 · Custom Code for the page, body field
Page Settings › Custom Code tab › <body> › Save
<script src="https://app.storyproof.io/embed.js" async></script>The builder will show an empty Embed block, which is expected. Publish the page and open its live URL to see the widget.
The id only fills the two snippets on screen. Nothing leaves your browser.
The problem, solved
Where testimonial embeds go wrong in ActiveCampaign Pages
- Problem 1
The editor started acting up after pasting
ActiveCampaign warns that third party JavaScript in the editor can collide with its own, breaking image uploads or layout tools.
How StoryProof solves it
The StoryProof embed is an empty div plus a separate script, so the Embed block holds only HTML and the script stays out of the editor.
- Problem 2
The widget is missing in the builder
Code in Page Settings only runs on the live page, so the editor shows a blank Embed block and people assume it failed.
How StoryProof solves it
Judge it on the published URL. In the builder, a blank block holding the StoryProof div is the expected state.
- Problem 3
Proof near the form and further down
A long offer page wants a short strip by the signup form and a fuller set lower down, and that sounds like two scripts.
How StoryProof solves it
Use two Embed blocks with different widget ids. The single script in Custom Code fills both, and each widget can have its own layout and selection.
- Problem 4
Pasted quotes nobody vetted
Copying testimonials into text blocks by hand means old, unchecked or unapproved words end up on a paid traffic page.
How StoryProof solves it
Collect video, audio or written testimonials with one link, approve them in StoryProof, and only approved ones can appear in the widget.
In StoryProof
Install it on an ActiveCampaign page
Step 1 of 4
Build the widget
In StoryProof, choose the approved testimonials and a layout that suits the spot on the page, then copy the widget id.
Step 2 of 4
Drop in an Embed block
In the page builder, drag an Embed block to where proof belongs and click it to open its code editor. Paste Part 1 between the paragraph tags already there.
Step 3 of 4
Add the script in Page Settings
Open the page’s settings, go to the Custom Code tab and paste Part 2 into the body field. Save. One script covers every StoryProof block on the page.
Step 4 of 4
Publish, then check the live URL
Publish the page and open it in a private window. Look at it on a phone too, since landing page traffic is often mobile.
Before you start
ActiveCampaign limits
No preview in the builder
ActiveCampaign states that code added in Page Settings is only visible on the live page. Every check has to happen after publishing.
Per page setup
Custom Code belongs to a single page. A second landing page needs its own Embed block and its own copy of the script.
Help pages read through search
ActiveCampaign’s help center refused automated reading on 2026-11-13, so these steps rest on the search excerpts of its articles. Confirm menu names in your account.
Badge and no native connector
StoryProof connects to ActiveCampaign Pages only through this embed. Widgets show a "Powered by StoryProof" badge until Pro.
Steps as of 2026-11-13
The click path follows ActiveCampaign’s help as found on 2026-11-13 and has not yet been tested on a live ActiveCampaign page.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can I paste both lines into the Embed block?
It may work, but ActiveCampaign recommends keeping JavaScript in Page Settings because scripts in the editor can interfere with it. Splitting the embed follows that advice.
Does this work in ActiveCampaign emails?
No. This is for Pages. Email clients do not run widget scripts, so emails need a different approach.
Where does the head field come in?
It is not needed here. The body field is enough for the StoryProof script, which loads asynchronously.
Can testimonial requests go out from ActiveCampaign?
You can paste your StoryProof collection link into any ActiveCampaign email. StoryProof can also send its own request emails, but it has no direct ActiveCampaign integration.
Still have a question? Ask the StoryProof team or book a demo.
Put approved proof on your ActiveCampaign pages
Collect, approve and embed with one block and one script.
Sources
- Use custom code on your ActiveCampaign page, ActiveCampaign Help Center. Checked 2026-11-13.
- Why do we recommend putting JavaScript in the Landing Page Setting’s Custom Code Section?, ActiveCampaign Help Center. Checked 2026-11-13.
- Add an Embed block to your ActiveCampaign page, ActiveCampaign Help Center. Checked 2026-11-13.
Last updated 2026-11-13.