Dorik installation
Dorik Testimonial Widget with Custom Code
Dorik gives you four places for client side code: a Custom Code element inside any container, header and footer code for one page, header and footer code for the whole site, and raw HTML in the blog editor. All of them need a paid Dorik plan; the free plan has no custom code. Pick the place by how many pages show testimonials, then paste the StoryProof lines.
- Both lines for a Custom Code element
- The script for Site Settings footer code
- A div for raw HTML in a blog post
Dorik code locations
Code for each Dorik location
Enter your widget id. A one page site needs only Snippet 1. A site with testimonials on several pages or posts uses Snippet 2 once in Site Settings, then Snippet 3 in each Custom Code element and Snippet 4 in blog posts.
Part 1 · Snippet 1: one Custom Code element with both lines
+ Add Element or Containers › Elements › Custom Code
<div data-storyproof-widget="YOUR_WIDGET_ID"></div>
<script src="https://app.storyproof.io/embed.js" async></script>Part 2 · Snippet 2: the script for every page
Dashboard › Site Settings › Advanced › Footer Code
<script src="https://app.storyproof.io/embed.js" async></script>Part 3 · Snippet 3: the div in a Custom Code element
+ Add Element or Containers › Elements › Custom Code
<div data-storyproof-widget="YOUR_WIDGET_ID"></div>Part 4 · Snippet 4: the div inside a blog post
Blog editor › raw HTML
<div data-storyproof-widget="YOUR_WIDGET_ID"></div>Save and publish the site, then open a page and a blog post that hold a div, and one that does not. Only the first two should show testimonials.
Generated in your browser. The widget id is not stored or sent.
The problem, solved
Dorik testimonials: the decisions and the StoryProof side
- Problem 1
Custom Code is missing on my site
Dorik says custom code requires a paid plan; its free plan has no header, footer or inline code.
How StoryProof solves it
On a free Dorik site, link a button to your hosted Wall of Love, which every StoryProof plan includes. Move to the widget after upgrading Dorik.
- Problem 2
Testimonials on ten pages, ten scripts
Pasting both lines into every element repeats the same script across the site.
How StoryProof solves it
Put the script once in Site Settings footer code. It fills every StoryProof div on each page that loads.
- Problem 3
My blog posts need proof too
Posts about a service get read by people deciding whether to hire you, with no testimonial in sight.
How StoryProof solves it
Drop a div into the post with the blog editor’s raw HTML, and choose which approved testimonials that widget shows.
- Problem 4
Different services need different quotes
A web design client and an SEO client care about different results, and one shared widget mixes them.
How StoryProof solves it
Tag testimonials by service in StoryProof, which is on every plan, and build a widget per service from the approved ones.
In StoryProof
Install on a Dorik site
Step 1 of 4
Add the site wide script
From the left panel of the site dashboard open Site Settings, go to the Advanced tab and paste Snippet 2 into Footer Code.
Step 2 of 4
Add a Custom Code element
In the editor click + Add Element or Containers in an empty container, choose Elements, then Custom Code, and paste Snippet 3 into its HTML editor.
Step 3 of 4
Add widgets to blog posts
In a post, insert raw HTML in the blog editor and paste Snippet 4 where the testimonials should appear in the text.
Step 4 of 4
Publish and check
Save, publish, and open the live pages. For page specific code instead, Page Settings has the same Advanced tab with header and footer code.
Dorik’s four code places
Before you start
Dorik limits
Steps follow the docs as of 2026-11-14
Menu names come from Dorik’s help articles on the Custom Code element, adding custom code and site settings, and its custom code feature page, read on 2026-11-14. Nobody has tried them on a live Dorik site.
Paid Dorik plan required
Dorik’s feature page says custom code needs a paid plan and that the free plan cannot add header, footer or inline code.
Client side code only
Dorik runs HTML, CSS and JavaScript but not server side languages. The StoryProof embed is client side, so it fits.
Editor behaviour is not documented
Dorik’s Custom Code element article does not say whether scripts run inside the editor. Judge the widget on the published site.
StoryProof badge
Widgets show a "Powered by StoryProof" badge until Pro.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should the script go in Header Code or Footer Code?
Either works because the script is asynchronous. Footer Code keeps it out of the way of the page’s first paint, so this guide uses it.
My Dorik site was built by AI. Does that change anything?
No. An AI generated Dorik site is edited the same way. Replace any placeholder testimonials it wrote with real ones from StoryProof.
What if only my pricing page needs testimonials?
Then skip Site Settings. Put both lines in one Custom Code element on that page, or the script in that page’s own Page Settings and the div in the element.
Does StoryProof connect to Dorik’s forms?
No. Use your StoryProof collection link for testimonials rather than a Dorik form.
Still have a question? Ask the StoryProof team or book a demo.
Put real client praise on your Dorik site
Collect and approve testimonials in StoryProof, then paste them into Dorik once.
Sources
- Custom Code Element, Dorik Help Center. Checked 2026-11-14.
- Add Custom Code, Dorik Help Center. Checked 2026-11-14.
- Site Settings, Dorik Help Center. Checked 2026-11-14.
- Custom Code, Dorik. Checked 2026-11-14.
Last updated 2026-11-14.