Instapage installation
Instapage Testimonials with Custom HTML
Instapage gives every landing page an HTML element for content and a JavaScript setting for page code. Put the StoryProof div in the element, the script in the page footer code, and then judge the result on the published URL, because Instapage says custom code is not built to run in the editor or preview.
- The div for an HTML element, the script for the page footer
- Why a blank box in the builder is normal
- Where proof sits on a paid traffic page
Code generator
Two snippets for an Instapage landing page
Type the widget id once. The first snippet goes into an HTML element you drag onto the canvas; the second goes into the page JavaScript setting, Footer section, so it loads after the page content.
Part 1 · An HTML element on the canvas, where the testimonials belong
Page builder › HTML element in the left toolbar › Edit (or double click the box)
<div data-storyproof-widget="YOUR_WIDGET_ID"></div>Part 2 · The page JavaScript setting, Footer section
Page builder › Settings in the right panel › JavaScript › Footer
<script src="https://app.storyproof.io/embed.js" async></script>Save and publish, then open the published URL in a private window. The HTML element stays an empty grey box in the builder; that is expected and says nothing about the live page.
Built in your browser from the id you type. Nothing is sent.
The problem, solved
What slows social proof down on Instapage, and how StoryProof handles it
- Problem 1
Every A/B variant has its own typed quotes
Duplicating a variant copies the text boxes, so a corrected name or a stronger quote has to be fixed on each variant one at a time.
How StoryProof solves it
The quotes live in StoryProof, not on the canvas. Each variant carries the same small div, and you choose the approved testimonials that widget shows in one place.
- Problem 2
The HTML box stays blank in the builder
People paste code, see nothing, and start trying other snippets, which is how duplicate scripts end up on a campaign page.
How StoryProof solves it
The snippet is just a div and one async script, so there is nothing to tweak. Publish and look at the live URL, where Instapage actually runs custom code.
- Problem 3
Each ad group needs proof for its own audience
A campaign aimed at clinics and one aimed at agencies share a template, but a quote from the wrong kind of buyer weakens both.
How StoryProof solves it
Tag testimonials by audience or offer, then build a widget per campaign from the tagged set and drop its div on that campaign’s page.
- Problem 4
Ad reviewers ask where these quotes came from
A landing page that shows unsourced praise invites questions from compliance and from the ad platform alike.
How StoryProof solves it
Nothing a customer submits reaches a widget until someone on your team approves it, so the page only shows testimonials you have looked at.
- Problem 5
A long page wants proof in two places
One strip under the hero and a fuller block by the final form is common, and it raises the question of a second script.
How StoryProof solves it
Keep a single script in the page footer code. It fills every StoryProof div on that page, so the second HTML element only needs its own div.
In StoryProof
Install it on an Instapage page
Step 1 of 5
Build the campaign widget in StoryProof
Filter by the tag for this audience, add the strongest approved testimonials to a widget, pick its layout, and copy the widget id.
Step 2 of 5
Drop an HTML element on the canvas
In the builder, click HTML in the left toolbar. A placeholder box appears; click Edit or double click it, paste the div, and save. Drag and resize the box to the space the widget should fill.
Step 3 of 5
Add the script to the page footer code
Open Settings in the right panel, choose JavaScript, and paste the script line into the Footer section. One copy is enough for every widget on this page.
Step 4 of 5
Check the mobile layout
Instapage keeps a separate mobile layout. Switch to it, confirm the HTML element sits where you want it, or hide it there with the element’s visibility option if the mobile page is already long.
Step 5 of 5
Publish and test the live URL
Publish, open the live page in a private window on desktop and on a phone, and confirm the widget loads. If you change the code later, clear your browser cache before judging it.
Where proof earns its place on a campaign page
Before you start
Instapage caveats
Custom code runs on the live page only
Instapage’s help center says custom scripts do not execute in the editor and are not meant to work in preview. Some embeds render in preview anyway, but the published URL is the only reliable test.
Instapage support will not debug it
Instapage states its support team cannot troubleshoot third-party code. If the widget does not appear, check the div and script against the generator above before contacting anyone.
No Instapage integration
StoryProof is not an Instapage integration. It installs with embed code. Where custom code is not allowed, link to your hosted Wall of Love instead.
Badge on lower plans
A small "Powered by StoryProof" badge sits under the widget until Pro, which matters on a page built to look like your brand only.
Steps follow the docs as of 2026-11-12
The menu names here come from Instapage’s help center, read on 2026-11-12, and nobody has yet followed them on a real Instapage account. Builders rename panels; check the current docs if a label differs.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can I paste both lines into the HTML element instead?
Usually yes, since the element accepts HTML and scripts. Splitting them keeps one script per page even when you add a second widget, which avoids loading the same file twice.
Why is the HTML element empty in the Instapage builder?
Instapage does not run custom code in the editor. The box is a placeholder until the page is published.
Do A/B variants need their own script?
Each variant is its own page as far as the browser is concerned, so check that the variant you created carries both the div and the footer script before you send traffic to it.
Will the widget count as a conversion goal?
No. Instapage notes that forms embedded with custom code do not count toward its Form submissions goal, and a testimonial widget is not a form at all. Conversion tracking stays on the Instapage form.
Still have a question? Ask the StoryProof team or book a demo.
Give your next campaign page real proof
Collect testimonials, tag them by audience, and place a widget on your Instapage page in a few minutes.
Sources
- Embedding custom HTML or widgets into an Instapage landing page, Instapage Help Center. Checked 2026-11-12.
- Using Custom HTML, Javascript and CSS on Your Page, Instapage Help Center. Checked 2026-11-12.
- Hiding page elements on desktop/mobile, Instapage Help Center. Checked 2026-11-12.
Last updated 2026-11-12.