Is Pathmonk not connecting to your website?

You've added the snippet, but onboarding is still waiting for your first pageview — or Pathmonk was working and has gone quiet. Almost every case comes down to one of six things: the snippet isn't really on the page, a cache is serving old HTML, a performance setting is deferring the script, a Content Security Policy or consent tool is blocking it, an ad blocker is stopping it in your browser, or the snippet is on a different domain than the one in your account. This guide finds out which in about a minute.

Start here

One check tells you which half of the problem you have, and saves you from guessing.

1. Open your live site in an incognito/private window with extensions disabled.
2. Open DevTools (F12) → the Network tab.
3. Reload the page, and type pathmonk in the filter box.

You'll see one of three things.

What you see	What it means	Go to
Nothing at all	The snippet never ran on this page.	A — the snippet isn't running
plugin.min.js failing, cancelled, or with a red error	The snippet ran, the SDK was blocked.	B — the SDK is blocked
plugin.min.js returning 200	The install is working. Something else is going on.	C — it loads but nothing happens

While you're there, check the Console tab for errors mentioning pathmonk, a blocked script, or a Content Security Policy violation. They point straight at the cause.

Your own ad blocker is the single most common false alarm

uBlock Origin, AdGuard, Ghostery, Brave's shields, and most privacy extensions block analytics scripts by default — including Pathmonk. If you're the marketer testing your own install, there's a good chance the only browser reporting a problem is yours. Test in an incognito window with extensions off, or on your phone on mobile data. If it connects there, your install is fine. This affects a small share of real visitors too, and it's normal.

A — The snippet isn't running

The snippet isn't in the page at all, or it's there but never executes.

1. Did the change actually publish?

View source (Ctrl/Cmd + U) on the live page and search for pathmonk.

• Not there at all → the edit didn't publish, or a cache is serving old HTML. Go to step 2.
• There in source, but nothing loads → the snippet is in the page but not executing. Go to step 4.

While you have the source open, check the client ID in the snippet against the one on your Pathmonk setup screen. If they don't match, you've pasted a snippet from a different account or a different site — replace it.

Exception: with Google Tag Manager or Wix, the snippet is injected client-side and will never appear in view-source. Use Inspect element (F12 → Elements) and search there instead.

2. Clear every cache, in order

This is the most common cause by a wide margin. Caches stack, and clearing one isn't enough.

1. Your caching plugin — WP Rocket, LiteSpeed, W3 Total Cache, WP Super Cache. Purge all.
2. Your host's cache — Kinsta, WP Engine, SiteGround, Shopify, and most managed hosts run their own layer above the plugin.
3. Your CDN — Cloudflare, Fastly, Bunny. Purge everything. On Cloudflare, Development Mode bypasses the cache for three hours, which is useful while you're testing.
4. Your browser — hard reload (Ctrl/Cmd + Shift + R).

Then reload and check the Network tab again.

3. Is it on this page, or only some pages?

Check your homepage, a blog post, a product or service page, and any landing page. If the snippet is on some and not others, it went into one template instead of the global footer.
Common versions of this:

• Added to footer.php but the landing pages use a different template.
• Added to a page builder's page-level custom code instead of the site-wide setting.
• Added to the theme, then the theme was switched or redesigned. New theme, no snippet.
• WordPress with a separate landing-page plugin that bypasses the theme footer.

4. Is a performance setting deferring or breaking it?

If the snippet is in the source but doesn't run, a JavaScript optimisation feature is usually responsible.
Look for and exclude pathmonk from:

• Delay JavaScript until user interaction (WP Rocket, LiteSpeed, Perfmatters). This is the worst offender — the SDK won't load until the visitor clicks or scrolls, which for many visitors is never.
• Defer all JavaScript.
• Minify / combine JavaScript — combining can corrupt an inline snippet.
• Cloudflare Rocket Loader — turn it off, or add data-cfasync="false" to the snippet tag.
• Shopify speed-optimisation apps that defer third-party scripts.

Every one of these tools has an exclusion list. Add pathmonk to it.

5. Is the snippet in the <head>?

It needs to be immediately before </body>. The snippet attaches its mount point to document.body, so if it runs before the body exists, it throws and nothing installs. Move it.

6. Google Tag Manager specifics

If you installed via GTM and the tag isn't firing:

• Did you Submit and Publish? Saving the tag isn't enough. A tag that works in Preview but not on the live site is almost always an unpublished container.
• Is the trigger set to All Pages? If the tag is on a narrower trigger, Pathmonk only loads where that trigger fires. Check too that no Exception is excluding the pages you're testing.
• Does the container load on every page? Pathmonk inherits GTM's coverage exactly. Checkout pages, landing pages built outside the CMS, and legacy subdomains often don't carry it.
• Is your CMP blocking it? See below.

7. Is the domain registered to your account?

Pathmonk runs on the domains in your account. If you've installed on a staging URL, a www vs. non-www variant, or a subdomain you haven't added, it won't connect. Check the domain settings in your account against the URL you're actually testing — and note the limit of two subdomains per account. See Adding domains and subdomains.

B — The SDK is blocked

The snippet ran, but plugin.min.js never loaded. Check the Network tab (filter: pathmonk) and the Console tab for a blocked-resource error.

Content Security Policy

If your site sends a CSP header, it blocks the SDK silently unless Pathmonk is allowlisted. The console will name the violated directive.
The snippet is an inline script that loads a remote file, so a strict policy needs a nonce or hash — the domain allowlist alone isn't enough:

script-src   https://pathmonk-lib.pathmonk.com   + a nonce or hash for the inline snippet
connect-src  https://apisdk.pathmonk.com
img-src      https://pathmonk-assets.pathmonk.com
media-src    https://pathmonk-assets.pathmonk.com
font-src     https://fonts.gstatic.com
style-src    https://fonts.googleapis.com        + 'unsafe-inline' for injected styles

Test changes with Content-Security-Policy-Report-Only before enforcing. Full detail: Content Security Policy (CSP) configuration.

A consent tool or CMP

Cookiebot, OneTrust, Complianz, Termly, Usercentrics and CookieYes block scripts they haven't been told about — typically by rewriting type="text/javascript" to type="text/plain" until consent is given. View source and check whether your snippet's type attribute has been changed. If it has, your CMP is holding it.
Pathmonk is cookieless and first-party, so it doesn't need consent to run. Classify it accordingly in your CMP rather than leaving it in the blocked-by-default bucket. See Pathmonk's cookieless technology and GDPR.

A firewall, WAF or server-level block

Rare, but it happens on locked-down corporate and government sites. If the request to apisdk.pathmonk.com fails with a network error rather than an HTTP status, ask whoever manages your network to allowlist the Pathmonk domains listed above.

C — It loads but nothing happens

If plugin.min.js returns 200 and the client ID in your snippet matches your account, your install is working. What you're seeing is something else.

• Onboarding still says "waiting for your first pageview". Give it a minute and reload the onboarding screen. If it's still waiting, the pageview that loaded probably came from a browser with an ad blocker, or from a URL that isn't the domain on your account. Try again in incognito, on the exact domain you registered.
• Connected, but no microexperiences on the page. That's expected at first. The engine calibrates before it serves anything, and once it starts, a share of visitors is held back as a permanent control group — so not every visit shows a card. See When will I see results? and How Pathmonk A/B testing works. If you're well past calibration and still seeing nothing, go to Pathmonk isn't showing on my website.
• Connected, but conversions aren't recorded. Different problem — that's goal configuration, not installation. See Conversions aren't being recorded.

It was working, and stopped

Work backwards from what changed:

What changed	What it did
Theme switch or redesign	The snippet lived in the old theme and didn't come across
Site migration or replatform	Same — the snippet rarely survives
New caching or performance plugin	Its default "delay/defer all JS" setting caught Pathmonk
New consent tool	Blocking the snippet by default
New CSP, or a tightened one	Blocking the SDK
Cloudflare turned on, or Rocket Loader enabled	Deferring or rewriting the script
Someone "cleaned up" the theme files	Snippet removed

Then go back to Start here and follow the branch it points to.

Still stuck?

Email support@pathmonk.com with:

• The exact URL you're testing.
• A screenshot of the Network tab filtered for pathmonk.
• A screenshot of any pathmonk-related errors in the Console tab.
• What changed recently, if it used to work.
• Your platform and any caching, performance, consent or CDN tools in front of the site.

That's usually enough for us to tell you the cause on the first reply.