Add a script

Add a tag or script in the Global organisation, choose when it runs, and republish so it reaches live campaigns.

2 min read

Add a script once and have it apply across your campaigns. The step people miss is the last one — a saved script does nothing until the affected campaigns are republished.

Before you begin

  • You need Admin access. Scripts live in the Global organisation settings.
  • Have the script code from whoever supplied it — your web team, or the tool's own setup screen.
  • Know which context and trigger it needs. See Where and when a script runs.
  • Have a staging campaign to test on. Do not test a new script on a live campaign.

Steps

Open the Scripts settings

Switch to the Global organisation, open General Settings, then select Scripts.

Scripts list in General Settings

Add the script

Select Add Script and fill in the form: a name you will recognise later, the code itself, the context, and the trigger.

Name it for what it does and who owns it — "GTM container (web team)" is findable in a year; "script 3" is not.

Script editor showing name, context, trigger, active flag, and code area

Republish the affected campaigns

A saved script does not reach a live campaign until that campaign is republished.

This is the step that gets missed

If you save the script and stop here, live campaigns keep running without it — and everything looks correct in the settings screen. Republish every campaign that should carry the script.

Test before you enable it widely

Enable it on a staging campaign first. Run the full participant journey and confirm two things: the tag fires as expected, and nothing about the experience broke — navigation, forms, buttons, and the reward step.

Switching a script off

You can disable a script without deleting it. Use this to stop one quickly if something looks wrong, then re-enable it once you understand what happened. Disabling also needs a republish to reach live campaigns, so build that into your rollback plan rather than discovering it during an incident.

If something's blocked

  • The tag does not fire on a live campaign. The campaign has not been republished since the script was added.
  • It fires twice. The experience is embedded in a page that already fires the same tag. Set the script to standalone only.
  • The experience broke after adding a script. Disable the script, republish, and confirm the experience recovers before investigating.
Tags & scriptsWhere and when a script runsChoose the context and trigger.Tags & scriptsScript examplesCode for the common cases.OrganisationsOrganisation scriptsWhere this sits among the other organisation settings.

On this page

Before you beginStepsOpen the Scripts settingsAdd the scriptRepublish the affected campaignsTest before you enable it widelySwitching a script offIf something's blockedRelated