Organisation scripts
Connect OmniLab Pages to tools like Google Tag Manager or a tracking pixel, with one script your admins manage centrally.
Connect your OmniLab Pages to outside tools like Google Tag Manager, a tracking pixel, or a custom analytics setup, all from one place your admins control. A script is a small piece of code that loads with your OmniLab Pages and makes that connection.
You add scripts once in the Global organisation, and they apply across campaigns. You choose when each script runs (on page load or after registration) and whether it runs inside an embedded experience, on a standalone page, or both.
Writing the script code is a developer task
This page covers the admin side: adding, enabling, and governing scripts. A developer should write and review the code itself. Share the Writing organisation scripts guide with your developer or IT team before they start.
What you can do with scripts
- Load a tag manager such as Google Tag Manager so it is available across all OmniLab Pages
- Send a tracking event when a participant visits a page or completes a registration
- Adapt behaviour per organisation using values already stored in OmniLab (country, language, region)
How to add a script
Add a new script entry
Click Add Script and fill in the form. Your developer provides the script code, the context (all pages, embedded-only, or standalone-only), and the trigger (page load or registration).

Publish the affected campaign
Changes only take effect after you republish the campaign. Saving the script without republishing leaves the live experience unchanged.
Publish after every script change
If you update a script and only save the Global organisation settings, live campaigns keep running the previous version. Republish the campaign to apply the update.
Enable and test
Enable the script in a staging environment first. Verify that navigation, forms, consent flows, and call-to-action buttons still work before you enable it in production.
Disabling a script
You can disable a script at any time without deleting it. Use this to pause a script quickly if something seems wrong, then re-enable it once the issue is understood.
Related
Writing organisation scripts
Developer guide: script structure, available data, and example code.
Variables at organisation level
Use organisation variables to make one global script adapt to several organisations.
Organisation settings
Review the other shared settings that shape how OmniLab Pages behaves per organisation.
