Verify your tracking is working

Pipeline On verifies tracking after the ID tag loads on your website and sends a valid pageview.

Quick verification checklist

Confirm the tag is installed on the live website, not only a draft preview.
Visit the public website in a fresh browser tab.
Open at least one page where the tag should be present.
Return to Pipeline On and refresh the install page.

What verified means

Verified means Pipeline On has seen the tag run for that site. It does not guarantee that every visitor will become a recovered lead.

How to manually check the tag

If the dashboard still says the tag is not installed, you can check the live page:

Open the public page where the tag is installed.
Right-click the page and choose Inspect.
Open the Network tab.
Refresh the page.
Search the network requests for the Pipeline On script host shown in your install snippet.

If the script request appears and returns a successful response, the tag is loading. If it does not appear, the tag is missing, blocked, delayed, or only installed on a different page.

Google Tag Manager checks

If you installed with Google Tag Manager:

Confirm the Pipeline On tag uses Custom HTML.
Confirm the trigger fires on every public page where you want tracking.
Publish the GTM container. Preview mode alone does not update the live site.
If you use consent mode or a cookie banner, test both before and after accepting the banner.

The tag should not fire during consent initialization. If your site requires consent, fire the tag after the relevant consent signal is granted.

If the dashboard still says not installed

Check these items:

The website changes were published.
The tag was copied completely.
The tag is not inside a disabled tag manager trigger.
A cookie banner or consent tool is not blocking the tag before consent.
A Content Security Policy is not blocking the script host.
The tag is on the public domain connected to your Pipeline On account.
The tag is not installed twice.
The tag is not only on a staging domain, checkout page, or admin-only page.
The live page is not serving an older cached version without the tag.
Single-page apps fire tracking again after route changes, not only on the first page load.

If the tag verifies but you do not see your own lead

That can be normal. Pipeline On only creates recovered leads when there is enough matching data and confidence. A successful install check proves the tag is running; it does not mean every test visit will turn into a recovered homeowner.

When to contact support

Contact support if the tag is installed on a live page, you have visited that page after publishing, and Pipeline On still has not verified the install.

Include the website domain and the exact page URL where the tag is installed.