ClickFunnels installation
ClickFunnels Testimonials on Funnel Pages
ClickFunnels shows custom code as a grey placeholder in the editor, so a StoryProof widget will look missing until you preview. Put the div in an HTML/JS element on the step, choose how widely the script should load, and judge the result from the preview.
- Div for the HTML/JS element
- Script for page, funnel or site Footer Code
- Proof matched to each funnel step
Code for ClickFunnels
Split the snippet across element and Footer Code
The div marks where the widget appears, so it goes in an HTML/JS element on the step. The script can live in Footer Code on just that page, on the whole funnel, or on the whole site. Pick one level.
Part 1 · An HTML/JS element on the funnel step
Page editor › Section › Row › + Add New Element › MISC › HTML/JS › Open Code Editor
<div data-storyproof-widget="YOUR_WIDGET_ID"></div>Part 2 · Footer Code for this page only
Page editor › Settings › Show Code › Footer Code
<script src="https://app.storyproof.io/embed.js" async></script>Part 3 · Or Footer Code for every step in the funnel
Funnel settings › Footer Code
<script src="https://app.storyproof.io/embed.js" async></script>Save, then open Preview. The editor canvas only shows a CUSTOM JAVASCRIPT / HTML placeholder, so the preview or the published step is the real test.
Generated in your browser. ClickFunnels and StoryProof receive nothing from this tool.
The problem, solved
Funnel proof problems, and what StoryProof changes
- Problem 1
Every step shows the same three quotes
The opt-in page, the sales page and the order bump each meet a buyer with a different doubt, yet funnels usually recycle one block of praise.
How StoryProof solves it
Tag testimonials by the doubt they answer, then give each funnel step its own widget with the approved stories you chose for it.
- Problem 2
The editor shows a grey box, not my widget
ClickFunnels does not run custom code inside the editor, which makes a working embed look broken.
How StoryProof solves it
The embed is only a div with the widget id and one async script, so if the preview shows nothing, those two short lines are all there is to check.
- Problem 3
Proof on five steps, five script pastes
Copying the full snippet into every step makes the funnel harder to audit and easy to double up.
How StoryProof solves it
Load embed.js once in the funnel’s Footer Code and it fills every StoryProof div on each step it runs on.
- Problem 4
Quote blocks fight my page design
Funnel pages are tightly designed around one call to action, and a tall wall of reviews pushes the button off screen.
How StoryProof solves it
Choose a compact layout such as a strip, badge or single featured review for tight steps, and save walls and grids for long sales pages.
- Problem 5
I need control during a live launch
A launch funnel takes paid traffic from the first minute, so whatever shows on it has to be signed off.
How StoryProof solves it
Nothing goes into a widget until you approve it, so a submission arriving mid-launch waits in your queue.
Which Footer Code level to use
ClickFunnels documents three places for scripts. Use one level for the StoryProof script, not several.
In StoryProof
Install it on a ClickFunnels step
Step 1 of 5
Pick proof for the step
Decide what the visitor on this step doubts, then add approved testimonials that answer it to a StoryProof widget.
Step 2 of 5
Add an HTML/JS element
In the page editor add a section and a row, click the plus or Add New Element, open MISC and choose HTML/JS.
Step 3 of 5
Paste the div
Open the element settings, click Open Code Editor and paste only the div line. Leave out html and body tags, which ClickFunnels warns can break the page.
Step 4 of 5
Add the script at one level
Paste the script line into Footer Code for the page, the funnel or the site, following the table above.
Step 5 of 5
Preview the step
Open Preview and scroll to the element. If the widget renders there, publish; if not, check the script is in Footer Code at the level you chose.
Before you start
ClickFunnels limits
Support will not debug custom code
ClickFunnels Support does not troubleshoot custom code and suggests a developer for complex cases. StoryProof support covers the widget.
No live preview in the editor
The HTML/JS element always appears as a placeholder in the editor. Every check happens in Preview or on the published step.
Not a ClickFunnels app
StoryProof has no ClickFunnels integration; it is an embed like any other. For a link-only option, point a button at your Wall of Love.
One script level only
Putting the script in both page and funnel Footer Code loads it twice on that step. Choose the narrowest level that covers every widget.
Steps drawn from ClickFunnels docs
Menu names here match the ClickFunnels knowledge base on 2026-11-12. They have not been tested on a live funnel, and older Classic accounts may differ.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can I paste both lines into the HTML/JS element?
Yes, that works for a single widget. Splitting the script into Footer Code becomes worth it once two or more steps or elements carry widgets.
Why does the editor show CUSTOM JAVASCRIPT / HTML instead of reviews?
ClickFunnels does not run custom code in the editor. Open Preview to see the widget.
Which steps in a funnel need testimonials most?
Usually the sales page and the order form, where money is asked for. Opt-in pages need less, often a single short line near the button.
Does this work on ClickFunnels Classic?
This guide follows the current ClickFunnels knowledge base. Classic accounts run on an older editor, so follow Classic’s own help pages for the element and menu names.
Still have a question? Ask the StoryProof team or book a demo.
Match proof to every funnel step
Collect and approve testimonials in StoryProof, then drop the right set into each ClickFunnels step.
Sources
- HTML/JS: Insert Custom HTML and JavaScript Code, ClickFunnels Knowledge Base. Checked 2026-11-12.
- Adding JavaScript and Tracking Code for Advanced Features, ClickFunnels Knowledge Base. Checked 2026-11-12.
Last updated 2026-11-12.