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.
Without your tags, an experience is a blind spot: traffic arrives, people convert, and none of it reaches your reporting. A script here is the same code your web team already puts on your website. You add it once, centrally, and it loads with your campaign pages.
- 1Your scripts, added once in the Global organisation
- 2They load into every organisation's campaigns, not only one centre's
- 3Each campaign's pages, across every campaign
- 4A campaign only picks up a change once it is republished
Added once in the Global organisation, loaded into every organisation's campaigns once republished.
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 |
With your pixel in place, an ad platform can build a lookalike audience from people who engaged with a campaign. It can also exclude people who already converted.
Where scripts live
An admin adds scripts once, in the Global organisation. Every campaign takes them when it's published, whatever its organisation. A tag manager container belongs to your company, not to one campaign, so nobody should paste it into each new campaign by hand.
A pixel for one centre fires on every centre
A script added for one centre loads on every centre's campaigns once they're republished. To keep it to one centre, check the organisation in the script: see One organisation only.
Each script has two settings. One is where the experience runs: standalone, embedded in your site, or both. The other is when the script runs: on the page visit, or at registration. See Where and when a script runs.
Scripts run inside the experience your participants use. One that throws an error or blocks loading can stop people taking part. Test it on one campaign first. Plan how you'd switch it off quickly.
Consent is yours to handle
OmniLab doesn't decide what your participants consented to. If you need a cookie banner, load your own consent tool as a script, as you do on your website. Then make your other scripts respect its answer instead of firing regardless. That matters most for advertising pixels, 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 switching it on in Studio | An admin |
| Publishing the affected campaigns again, so it takes effect | Whoever owns those campaigns |