Fix common install problems

Fix common install problems

If Pipeline On is not verifying or no activity appears, the cause is usually one of a few setup issues.

The tag was pasted into the wrong place

The ID tag should run on public website pages. If it is pasted into a draft, admin-only page, checkout-only page, or a single landing page with no traffic, verification may not happen.

The tag was changed

Copy the ID tag exactly from Pipeline On. Do not remove attributes, change the script source, or replace the site ID.

The tag was malformed while being shared

Some chat and email tools change code when it is pasted into a message. Common problems include:

• Smart quotes replacing straight quotes.
• Missing quote marks around the script URL.
• A script URL split across multiple lines.
• Extra characters added before or after the tag.
• Nested script tags from a website builder or tag manager.

Fix this by copying the tag again directly from Pipeline On and replacing the full existing tag. If you need to send the tag to a developer, send it in a code block.

Google Tag Manager is not firing it

If you use Google Tag Manager:

1. Use a Custom HTML tag.
2. Fire it on all public pages.
3. Publish the GTM container.
4. Test the live site, not only GTM preview mode.
5. If a consent tool is active, confirm the tag fires after consent is accepted.

The website cache is stale

Some sites use page caching or CDN caching. Clear the cache and reload the live page after publishing.

A cookie banner is blocking the tag

Some consent managers block scripts until the visitor accepts cookies. If your policy requires this, that is expected. If not, update the consent settings so the Pipeline On tag can run according to your privacy policy.

A Content Security Policy is blocking the tag

If your site uses a Content Security Policy, ask your developer to allow the Pipeline On script host shown in your install snippet.

You may see browser console errors that say the page refused to load a script, connect to a URL, or run a resource because of a Content Security Policy directive.

The domain does not match your account

The tag should be installed on the same domain connected to your Pipeline On site. Free audits are limited to one domain per account.

The www and non-www domains are different

Make sure you are testing the same domain where the tag is installed. For example, example.com and www.example.com can serve different site versions.

If the tag is only on one version, install it on the canonical live version your visitors use.

The site is a single-page app

React, Next.js, Angular, Vue, and other single-page apps can change pages without a full browser reload. The tag must load on the first page and continue tracking route changes.

If you only see activity for the first page visited, ask your developer to confirm the tag is loaded globally and page changes are tracked.

The tag is duplicated

Only install one Pipeline On tag for the site. Duplicate tags can create unreliable verification and duplicate activity.

Check the page source, tag manager, theme settings, and plugin settings for old or duplicate copies.

The trial or matching access ended

If your free audit has expired after 7 days or 100 recovered IDs, matching and pixel access may turn off automatically. The tag can still exist on the site, but recovered lead activity may stop until the account is reactivated.