Skip to main content

BigCommerce installation

BigCommerce Testimonials with Script Manager

BigCommerce keeps storefront code and page content apart. Script Manager adds the StoryProof script to the footer of your storefront pages, and Page Builder’s HTML widget places the div in a region of the homepage, a product page or a web page. Both pieces are needed, and the theme has to print footer scripts.

  • A Script Manager entry for the footer
  • The div for a Page Builder HTML widget
  • Why checkout is not the place for it
Use the free toolStart free (opens in a new tab)
BigCommerce · A Script Manager script, placed in the footer on storefront pages

Control panel › Storefront › Script Manager › Create a Script

<script src="https://app.storyproof.io/embed.js" async></script>

2 places to paste in BigCommerce. Your widget id goes in once.

Free tool, no sign-upTry it below

Code generator

Your Script Manager entry and Page Builder div

Add your widget id. Part 1 is created once in Script Manager. Part 2 goes into an HTML widget wherever a widget should appear, and can be repeated across pages.

Shown in StoryProof when you copy a widget’s embed code.

Part 1 · A Script Manager script, placed in the footer on storefront pages

Control panel › Storefront › Script Manager › Create a Script

<script src="https://app.storyproof.io/embed.js" async></script>

Part 2 · An HTML widget in a Page Builder region

Storefront › Page Builder › drag HTML into a region › Save HTML

<div data-storyproof-widget="YOUR_WIDGET_ID"></div>

Publish the Page Builder changes, then visit the storefront page in a private window. If the region is empty, check that the theme prints footer scripts on that template.

Your id fills the code here in the browser and is not sent.

The problem, solved

Store testimonial gaps on BigCommerce, solved with StoryProof

  • Problem 1

    No native spot for store testimonials

    Product reviews cover items, but the homepage and about content have nothing that collects and shows praise for the store itself.

  • Problem 2

    Scripts pasted into widgets get duplicated

    Putting the full snippet in every HTML widget means several copies of the same script on pages with more than one region filled.

  • Problem 3

    Category pages need category proof

    A buyer browsing tools does not care about a quote praising the gift wrapping.

  • Problem 4

    Nobody asks customers after delivery

    Requests sent by hand depend on someone remembering, and the widget stops getting new material.

In StoryProof

Install it on a BigCommerce storefront

Step 1 of 4

Create the script in Script Manager

Go to Storefront, Script Manager, Create a Script. Give it a clear name, choose Footer as the placement, storefront pages as the location, and Script as the type, then paste Part 1 and save. Multi-storefront stores open Script Manager from the channel instead.

Script Manager location for a testimonial widget

Location names as listed in BigCommerce documentation on 2026-11-12.
Location optionUse it?Reason
Storefront pagesYesCovers the pages Page Builder edits, without touching checkout
All pagesOnly if neededAlso reaches cart and checkout, where a widget rarely belongs
CheckoutNoNot a place for testimonials, and it needs extra permissions
Order confirmationNoA thank-you moment better used for a request than for proof

Before you start

BigCommerce limits

  • The theme must print footer scripts

    BigCommerce documents that Stencil templates need the footer scripts expression for footer scripts to render. Custom or heavily edited themes sometimes drop it on some templates.

  • Not every page has Page Builder regions

    Page Builder works on the homepage, product, category, brand, web, blog post, search and cart pages, but some themes need template edits before a page accepts widgets.

  • Catalyst storefronts differ

    BigCommerce notes that Catalyst storefronts load only scripts set to all pages or storefront pages. The Page Builder steps here are written for Stencil, so on Catalyst a developer places the div.

  • No BigCommerce app

    StoryProof is not in the BigCommerce App Marketplace; it is installed with code. The "Powered by StoryProof" badge stays on widgets until Pro.

  • Checked against the docs on 2026-11-12

    Menu names follow BigCommerce’s help center and developer documentation as read on 2026-11-12. Nobody has run these steps on a live store yet.

FAQ

Questions people ask

Short answers to what usually comes up next.

Why not paste both lines into the HTML widget?

It may work, but BigCommerce’s intended home for scripts is Script Manager, where staff can see and remove them in one list. It also stops the script being loaded twice when a page has two widgets.

Does the widget show on checkout?

Not if you choose storefront pages as the location. Checkout is better left to the payment steps.

Is there a cookie consent setting I should pick?

Script Manager asks for a script category for consent. Choose the category your store policy uses for third-party content, and check the widget with consent both accepted and declined.

Can a developer add the div to theme files instead?

Yes. On a Stencil theme a developer can put the div straight into a template. Page Builder is simply the route that needs no theme edit.

Still have a question? Ask the StoryProof team or book a demo.

Give your BigCommerce store its own testimonials

Collect and approve store testimonials, add one Script Manager entry and place widgets with Page Builder.

Start free (opens in a new tab)Book a demo (opens in a new tab)

Sources

  1. Scripts API (Script Manager scopes and Stencil script expressions), BigCommerce Developer Documentation. Checked 2026-11-12.
  2. Page Builder, BigCommerce Help Center. Checked 2026-11-12.
  3. Google Ads Conversion Tracking Scripts (Script Manager fields), BigCommerce Help Center. Checked 2026-11-12.
  4. Install Scripts in Catalyst, BigCommerce Developer Documentation. Checked 2026-11-12.

Last updated 2026-11-12.