About tags and scripts
Load your tag manager, advertising pixels, and cookie banner into OmniLab experiences, so they behave like the rest of your website.
Make your OmniLab experiences visible to the tools you already run — analytics, advertising, consent — by loading the same tags you use everywhere else. Without this, an experience is a blind spot: traffic arrives, people convert, and none of it reaches your reporting.
A script is a small piece of code that loads with your OmniLab Pages. It is the same code your web team already puts on your website; here you add it once, centrally, instead of page by page.
- 1Your scripts, added once in the Global organisation
- 2They load with every experience that organisation runs
- 3Each campaign's pages, across every campaign
- 4A campaign only picks up a change once it is republished
Added once at the organisation level, loaded into every experience that organisation runs.
What people use them for
| Use | What the script does |
|---|---|
| Tag manager | Loads your container, so your existing tags work here too |
| Analytics | Sends page views and conversions to your analytics platform |
| Advertising pixels | Lets Meta, Google, or TikTok see the traffic, so you can build audiences from it and measure campaigns |
| Cookie banner | Loads your consent tool, so participants get the same choice as on your site |
| Small behavioural tweaks | Adapts what happens based on which organisation the experience belongs to |
Advertising pixels are worth calling out: dropping your pixel here is what lets an ad platform build a lookalike audience from people who engaged with a campaign, and exclude people who already converted.
Where scripts live
Scripts are added once in the Global organisation and apply across campaigns. That is deliberate — a tag manager container belongs to your company, not to one campaign, and nobody should be pasting it into each new campaign by hand.
Each script has two settings that decide when it runs: where the experience is running (standalone, embedded in your site, or both) and what moment it runs at (page load, or after registration). See Where and when a script runs.
A bad script affects live campaigns
These run inside the experience your participants use. A script that throws an error or blocks loading can stop people taking part. Test in staging, and keep a plan for switching one off quickly.
Consent is yours to handle
OmniLab does not decide what your participants consented to. If you need a cookie banner, load your own consent tool as a script here, exactly as you do on your website — and make sure your other scripts respect its answer rather than firing regardless.
That matters most for advertising pixels, which is where consent rules bite hardest.
Who does what
| Task | Who |
|---|---|
| Deciding which tags belong in the experience | Your marketing team |
| Writing or supplying the script code | Your web or analytics team |
| Adding and enabling it in OmniLab | An OmniLab admin |
| Republishing affected campaigns so it takes effect | Whoever owns those campaigns |