Is saving the OptiMonk tag enough to publish the GTM installation?

No. OptiMonk’s guide includes Submit and Publish after saving the tag. Verify the live container version and test the intended site before considering the installation complete.

Install OptiMonk with Google Tag Manager

You still install OptiMonk through Google Tag Manager as a Custom HTML tag on All Pages. The copy-code step now starts on the OptiMonk dashboard embed prompt, not a left-menu Insert code link. OptiMonk's GTM article (3 January 2026) is the source for the steps below.

If the site is Shopify, Magento, WooCommerce or WordPress, use the native app or plugin instead. OptiMonk describes direct integrations as offering additional capabilities such as cart rules. Compare the features your campaign needs before choosing GTM.

Copy the OptiMonk snippet

Log in at app.optimonk.com/login/en.
On the Dashboard, open the step that asks you to embed the OptiMonk code.
Choose Google Tag Manager as the install method (or pick it after you select the domain).
Copy the unique JavaScript.

You can also reach the snippet later from Profile → Settings → Insert code.

Add it in Google Tag Manager

Open GTM and select the container for that site.
Add a new Tag.
Tag Configuration → Custom HTML.
Paste the OptiMonk snippet.
Triggering → All Pages.
Save.
Submit, name the version, Publish.

Saving a new workspace change is not the same as publishing it. Check which container version is live before expecting the new tag to run for visitors.

Verify installation and campaign behavior separately

Use a controlled campaign and record the container, domain, page and published version. The following is an editorial test checklist, not evidence of account-level testing.

Check	Evidence to inspect
Container	The site uses the container you edited
Publication	The intended version includes the OptiMonk tag
Loading	The tag executes under the expected page and visitor conditions
Campaign	The intended active campaign follows its targeting and trigger
Mobile	The campaign is readable and usable on a narrow screen
Submission	A test lead is recorded and reaches its intended destination

Check a representative page from each template you depend on. An All Pages trigger does not prove that the container is installed on every page or that every campaign is eligible everywhere.

Troubleshoot the failed stage

If the tag does not run, investigate the container, version, trigger and applicable consent settings. If the script loads but no campaign appears, inspect campaign activation, domain and targeting separately. Do not treat the presence of a JavaScript object as proof that the whole user journey works.

If a form appears but a lead is missing downstream, inspect collection and integration mapping before reinstalling the tag. Keep one test address through the flow so the result is traceable.

Before adding another copy, check whether OptiMonk already loads through a theme or platform integration. Record the installation method you keep, so future editors do not accidentally create competing setups.

Prepare a maintainable handoff

Use a descriptive tag and version name. Note the account, domain, tested pages and expected campaign behavior. Retest after changing the container or theme rather than relying on a prior preview.

For embedded campaigns, review OptiMonk’s embedded-content requirements before assuming this installation route supports the placement you need. For status controls, see campaign activation.

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

How to Connect OptiMonk with Google Tag Manager