PathmonkHelp
Help/Getting started with Pathmonk/Introduction to Pathmonk/Requirements and supported setups

Requirements and supported setups

CategoryGetting started with Pathmonk › Introduction to Pathmonk
CreatedAug 20, 2026
UpdatedAug 20, 2026

Pathmonk is designed to run on virtually any website with minimal setup: one JavaScript snippet, no development project, and no changes to your existing stack. This page is the pre-flight check — what your website needs, what's supported, and what to have ready before you install.

How much traffic do you need?

There is no minimum traffic requirement. Pathmonk is a full-funnel platform, and a large part of it works regardless of how many visitors your site gets today: content generation, ads creation, competitor intelligence, SEO and AI search visibility all deliver value from day one, even on brand-new or low-traffic websites.

Traffic does matter for the features that learn from visitor behavior — on-site personalization, conversion optimization, and behavioral analytics. The more visitors you have, the faster the AI calibrates and the sooner you see statistically meaningful results there. On lower-traffic sites those features still work; they simply take longer to ramp up. See When will I see results? for how traffic volume affects the timeline.

For planning purposes: plans scale with monthly pageviews (up to 2,000,000+, custom above that), and a pageview is counted every time a visitor loads a page where Pathmonk is active. Multiple pages viewed by the same visitor count as separate pageviews — this differs from sessions in tools like GA4.

Website platforms

Pathmonk works on any website platform. The snippet is added once, just before the closing </body> tag, and loads on every page.

  • Guided installation is available for Google Tag Manager (recommended — the cleanest and most flexible method), Shopify (including revenue tracking), WordPress, Webflow, and Squarespace.
  • Custom-built websites are supported via manual snippet placement.
  • If you'd rather not touch the code yourself, you can send the snippet and instructions to your developer directly from the setup screen.

See Installing Pathmonk on your website for the step-by-step guide.

Domains and subdomains

  • One Pathmonk account covers one primary domain.
  • Up to two subdomains can be added to the same account (for example www.yoursite.com and shop.yoursite.com).
  • If you run more subdomains or multiple separate websites, they need their own accounts — see Adding / whitelisting subdomains and, for agencies managing many sites, Agency portal for marketing agencies & partners.
  • Pathmonk works in all modern browsers on desktop and mobile. Visitors don't need to install or accept anything.
  • Pathmonk's tracking is cookieless and first-party: it doesn't rely on third-party cookies, so it keeps working as browsers phase them out and it isn't blocked by cookie-rejection.

Content Security Policy (CSP)

Most websites don't need to do anything here. If your site enforces a Content Security Policy, allowlist these domains so the Pathmonk SDK can load:

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

If Pathmonk installs but never shows as connected, CSP is one of the usual suspects — see Is Pathmonk not connecting to your website?.

What to have ready

Before you start, make sure you have:

  1. Access to your website or your tag management platform (or a developer who has it).
  2. Your Pathmonk snippet, available from the setup screen after creating your account.
  3. Optional but recommended: admin access to Google Analytics, Google Search Console, and your CRM, so you can connect them as data sources and give the engine the full picture from day one.

That's it — no dev sprint, no design resources, and no cookie-consent changes required for Pathmonk itself.