Which page location does OptiMonk document for BigCommerce Script Manager?

OptiMonk’s guide specifies Header with All pages selected and Script as the script type. After saving, verify the integration on representative storefront pages rather than relying only on the success message.

Add OptiMonk to BigCommerce with Script Manager

OptiMonk still installs on BigCommerce through Script Manager, but the snippet now belongs in the Header, not the Footer. Copy it from Profile → Settings → Insert code, then create a Script on All pages. That is the 3 January 2026 OptiMonk article. Older steps that said "Install OptiMonk" in the bottom left and "Location on page: Footer" are wrong.

Copy the snippet from OptiMonk

Log in at app.optimonk.com/login/en.
Open your Profile, then Settings, bottom left.
Under Account, open Insert code.
Select the domain if you have more than one.
Choose Bigcommerce.
Pick install through BigCommerce (recommended) rather than GTM, after reviewing the appropriate installation method for your store.
Copy the unique JavaScript. It needs to run in the <head> of every page.

Paste it in BigCommerce Script Manager

Log in to the BigCommerce admin.
Storefront → Script Manager.
Create a Script.
Name it (OptiMonk is fine).
Set:

Location on page: Header
Select pages: All pages
Script category: Essential
Script type: Script

The settings above reproduce OptiMonk’s installation instructions. Review the script category against your store’s actual consent configuration; the vendor’s label is not by itself a legal classification.

Paste the OptiMonk code. Save.

You should see "Script created" and the row under Installed Scripts.

Verify the live storefront

A Script Manager success message verifies that the configuration was saved. It does not establish that the intended campaign appears or that its form works. Use a controlled campaign and record the domain, test page and visitor state.

Check	Evidence to inspect
Installation	The saved script uses the intended account code
Page coverage	Representative home, product and category pages load the integration
Campaign eligibility	An active campaign follows the intended audience and trigger
Mobile layout	The campaign fits without covering essential controls
Form submission	A test lead is recorded in OptiMonk
Destination	The expected external system receives the test lead

These are editorial verification steps, not a report of execution in a BigCommerce account. Test with the store’s intended cookie settings rather than changing them just to force a campaign to appear.

If the script is saved but the campaign is missing

Check the domain selected in OptiMonk, the saved script settings and the campaign’s active status separately. Then inspect targeting and trigger conditions. Do not add another copy of the snippet as the first troubleshooting step: first identify whether an installation already exists through a theme, app or tag manager.

If the campaign appears but a signup fails to reach its destination, investigate collection and the campaign integration. Reinstalling the storefront script is not a diagnosis of field-mapping or downstream delivery problems.

Keep the installation maintainable

Give the script a recognizable name and record the account and domain it belongs to. Include the pages tested in your handoff notes. Retest after changing the theme or installation method rather than assuming an earlier preview covers the new setup.

OptiMonk also documents a Google Tag Manager installation route. See OptiMonk with GTM for that workflow and campaign activation for status controls.

Source checked September 6, 2026: OptiMonk’s BigCommerce installation guide.

How to Integrate OptiMonk with BigCommerce