Is Pathmonk not connecting to your website?

If your Pathmonk dashboard shows “Waiting for incoming connection”, it means the Pathmonk SDK snippet hasn’t been detected yet.

Common reasons Pathmonk isn’t connecting:

1. The snippet isn’t installed on every page

Pathmonk needs to load across your entire website to track visitor behavior and display Micro-Experiences. If the snippet is only installed on a few pages or inside a section that doesn’t load site-wide, Pathmonk won’t detect traffic properly. This often happens when the snippet is placed only on the homepage or in a partial template.

✅ Fix: Install the snippet just before the closing </body> tag of your website’s global footer or layout. If your website uses multiple templates, make sure it’s included in all of them so Pathmonk loads everywhere.

2. The snippet was added in the wrong location

If the Pathmonk snippet is placed too high in the page or inside a restricted section (like the header or a tag manager rule that fires late), it might not execute correctly. Some CMS platforms automatically move or sanitize code blocks, which can prevent the script from initializing. As a result, Pathmonk can’t collect data or confirm a connection.

✅ Fix: Always place the snippet as close as possible to the closing </body> tag. If your platform doesn’t let you edit the footer directly, look for a custom code or footer script section (e.g., Webflow → Site settings → Custom code → Footer).

3. The changes haven’t been published yet

Saving your code is not the same as publishing it live. In platforms like GTM, WordPress, or Shopify, edits are often stored in a draft or theme file until you publish or deploy. If the snippet isn’t live yet, Pathmonk will keep showing “Waiting for incoming connection.” This is one of the most common setup oversights.

✅ Fix: After adding the snippet, make sure to publish your changes or push them to production.
If your website uses caching or a CDN (like Cloudflare), clear the cache and reload the page to ensure the code is live.

4. Wrong Google Tag Manager account or container

If you use Google Tag Manager (GTM) to install Pathmonk, ensure the tag was added to the correct GTM container. Sometimes, companies have multiple containers for different domains or subdomains, which can cause the Pathmonk tag to load in the wrong environment. When that happens, the Pathmonk dashboard won’t detect any incoming traffic.

✅ Fix: Compare the GTM container ID (the code starting with “GTM-”) found in your website’s source code with the one in your GTM workspace. If they don’t match, move the Pathmonk tag to the correct container and republish your workspace.

5. Website or browser errors

Certain scripts or security settings can block the Pathmonk SDK from loading properly.
Browser extensions, ad blockers, or custom cookie banners might prevent third-party scripts from running. In some cases, a JavaScript error from another plugin or app can also stop Pathmonk from initializing.

✅ Fix: Open your browser’s developer console (right-click → Inspect → Console tab) and check for errors mentioning “Pathmonk.” Try viewing your website in incognito mode or with ad blockers turned off. If you use a cookie consent tool, confirm that the Pathmonk script isn’t being blocked or delayed.

6. Cached or delayed updates

Some platforms (especially Webflow, WordPress, or those using CDNs) cache the previous version of your website. Even after you publish, it might take a few minutes for the updated version with the Pathmonk snippet to propagate. During that time, Pathmonk won’t detect any connection.

✅ Fix: Clear your website’s cache or CDN cache, then open a few pages in a new browser tab.
Wait a few minutes and refresh your Pathmonk dashboard — the status should update automatically once the script is detected.

7. Content Security Policy (CSP) restrictions

If your website uses a strict Content Security Policy, it may be blocking requests to Pathmonk’s servers.CSP rules control which external domains your website can load scripts and resources from. If Pathmonk’s domains aren’t whitelisted, your browser will block the SDK script entirely, preventing any connection.

✅ Fix: Ask your technical or security team to whitelist the following Pathmonk domains in your Content Security Policy:

apisdk.pathmonk.com
pathmonk-assets.pathmonk.com
pathmonk-lib.pathmonk.com
crm.pathmonk.com
fonts.gstatic.com
fonts.googleapis.com

These are the official Pathmonk domains required for the SDK, visuals, and fonts to load correctly.
If your organization enforces CSP headers and you need to update the allowed domain for your Pathmonk setup, please contact security@pathmonk.com for verification and assistance.

Once it’s working...

Once the connection is established, your Pathmonk dashboard will automatically update and begin collecting behavioral data. This is the screen you will see immediately before you're moved onto the next steps of the onboarding:

Still having trouble?

If you’ve gone through all these steps and Pathmonk is still not connecting:

• Double-check the installation guide to confirm your setup.

• Or contact support@pathmonk.com with a link to your website — our team will help you troubleshoot the installation.