Adding / Whitelisting subdomains

Modified on Tue, 14 Oct at 11:27 AM


⚠️ Note for new users: If you’re currently completing the onboarding process and your conversion goal or thank-you page is hosted on a different subdomain (for example, signup.website.com or thankyou.website.com), you won’t be able to whitelist it until after setup. Continue onboarding using mock data for now — once onboarding is complete, you’ll be able to add the subdomain in your account settings so Pathmonk can track visitors, show micro-experiences, and record conversions correctly.





If your website uses multiple subdomains (for example, a blog, portal, or thank-you page hosted separately), you can add them to your Pathmonk account so that tracking and micro-experiences work correctly across your entire website.


By default, Pathmonk is installed on your main domain (e.g., www.website.com).
Adding subdomains allows Pathmonk to:

  • Track user behavior on those pages

  • Display micro-experiences

  • Record conversions correctly, even if your goal happens on another subdomain



How to whitelist a subdomain



  1. Go to crm.pathmonk.com and log in.

  2. Click Settings in the top right-hand menu.

  3. Select Domains.

  4. Click the green plus (+) button to add a new subdomain.

  5. Enter only the subdomain part (for example, blog if your subdomain is blog.website.com).

  6. Click Save.

  7. (Optional) Repeat to add a second subdomain if needed.


Once saved, Pathmonk will automatically verify the connection. If your Pathmonk snippet is installed on that subdomain, it will begin collecting data immediately, though we always recommend adding the snippet there as well to ensure Pathmonk can track visitors, display micro-experiences, and record conversions correctly.




What counts as a subdomain?

A subdomain is an extension of your main website address. It appears before your main domain and is often used to separate different functions or sections of a site.


Examples:

  • blog.website.com → blog or content section

  • shop.website.com → online store

  • portal.website.com → customer or user login area

  • thankyou.website.com → thank-you page or conversion confirmation


If Pathmonk is installed on your main domain (www.website.com), these additional sections need to be whitelisted so that the Pathmonk snippet can run there as well.




What if my conversion happens on a subdomain?

Some businesses host their thank-you pages, checkout flows, or forms on a different subdomain — for example, signup.website.com or thankyou.website.com.
In these cases, Pathmonk won’t be able to track conversions correctly until that subdomain is whitelisted.


If you’re currently completing the onboarding process and can’t add the subdomain yet, don’t worry:


✅ Continue the onboarding using mock data for your conversion goal and/or tracking setup.
Once onboarding is finished, you’ll be able to whitelist the subdomain in your account settings.

After whitelisting:

  • The Pathmonk snippet will work on that subdomain.

  • Analytics and behavioral data will be collected.

  • Micro-Experiences can appear across domains.

  • Conversions and thank-you events will be properly tracked.




How many subdomains can I add?

Each Pathmonk account can include up to two additional subdomains. This extends Pathmonk’s reach beyond your main domain and ensures consistent personalization across all relevant areas of your site.


If you need to connect more than two subdomains (or special environments like a staging or sandbox domain), please contact support@pathmonk.com — our team will review your case and help with the setup.



⚙️ Best practices and tips

  • Install the snippet on each domain: Whitelisting alone isn’t enough — make sure the Pathmonk snippet is also added to the subdomain’s website code or tag manager.

  • Platform differences: If your subdomain uses a different platform (e.g., your main site is on Webflow but your blog is on WordPress), you’ll need to install the snippet separately there too.

  • Security policies: If your company uses a strict Content Security Policy (CSP), ensure it allows connections to Pathmonk’s official domains (pathmonk-lib.pathmonk.com, apisdk.pathmonk.com, etc.).





Still need help?

If you’re not sure which subdomains to whitelist or your conversions aren’t being tracked properly, our team can help. Reach out via support@pathmonk.com and we’ll make sure Pathmonk runs smoothly across all your domains.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article