Funnel scripts
Inject HEAD / BODY_START / BODY_END scripts scoped to a single funnel.
Funnel scripts let you inject arbitrary HTML script tags into every page of a specific funnel. Use this for per-funnel analytics, ad pixels, custom interaction code, or any third-party snippet that should run only within that funnel’s pages.
Injection positions
Each script has one of three positions:
| Position | Where it appears in the document |
|---|---|
HEAD | Inside the <head> element |
BODY_START | Immediately after the opening <body> tag |
BODY_END | Immediately before the closing </body> tag |
Choose the position based on the requirements of the script you are injecting. Most analytics and pixel scripts specify whether they require <head> or end-of-body placement.
Script load order
Funnel scripts are injected after site-level scripts (configured in Settings → Scripts). Within the same position, scripts run in the order set by the order field on each script record.
If both a site script and a funnel script load the same library (for example, the same pixel), both will execute. See Caveats below.
Managing funnel scripts
- Open the funnel detail page.
- Go to the Scripts tab.
- Click Add script.
- Give the script a name, choose the injection position, and paste the script content.
- Save. The script is injected into all pages of the funnel on the next page load.
You can disable a script without deleting it by toggling the Active switch on the script row. Inactive scripts are stored but not injected.
Caveats
- Double-injection. If a site script already loads the same pixel or library that a funnel script also loads, both copies run. This can cause duplicate events in your analytics or ad platform. Check your site scripts before adding a funnel-level pixel.
- No sandboxing. Scripts run with full page access. Injected code can read cookies, modify the DOM, and make network requests. Only inject scripts from sources you trust.
- Inactive scripts are retained. Disabling a script does not delete it. If you want to remove it permanently, use the delete action.