How to track website events with Pathmonk

Web URL goal

What is it?

The Web URL Goal is one of the simplest ways to track conversions. It records an event when a user lands on a specific URL, typically a confirmation or a thank-you page after completing an action.

How it works

1. You define a destination URL as the conversion goal (e.g., https://yourwebsite.com/thank-you).
2. When a visitor lands on this page, Pathmonk automatically registers the event as a conversion.
3. This method works without needing extra code—as long as users reach the designated URL, the conversion is tracked.

Best for:

• Tracking form submissions (e.g., lead generation forms, contact forms).
• Measuring purchases if the checkout process redirects users to a confirmation page.
• Event tracking without coding, making it easy for marketers to set up.

Advantages of using web URL goals

✔ Easy to set up: No need for custom scripts or developer involvement. Simply define the URL, and tracking starts immediately.
✔ Reliable for end-of-funnel conversions: Works well when conversions involve a clear redirect, like a thank-you page.
✔ Works with marketing tools: Can be integrated with ad platforms (e.g., Google Ads, Facebook Ads) to track conversions.
✔ No additional load on website performance: Since it doesn’t rely on JavaScript execution, there’s no risk of slowing down your site.

Limitations to consider

❌ Won’t track events without a page load: If your form submits without redirecting users (e.g., inline AJAX forms), this method won’t work.
❌ Prone to duplicate tracking: If users refresh the thank-you page, the conversion may be counted multiple times unless properly handled.
❌ Doesn’t capture micro-conversions: Actions like button clicks or partial form completions won’t be recorded—only final page loads are tracked.

When to use (and when not to use) web URL goals

Use web URL goals if:

• Your website has a clear thank-you or confirmation page after key actions.
• You need a fast, no-code tracking solution.
• Your funnel naturally includes page redirects (e.g., eCommerce purchases, appointment scheduling, lead forms).

Avoid web URL goals if:

• Your site uses pop-ups or inline form submissions that don’t redirect to a new page.
• You need to track button clicks, downloads, or interactions—in this case, a Visitor Action Pixel would be better.
• Your pages have dynamic URLs (e.g., thank-you?id=12345), which may require more advanced setup.

Page load pixel

What is it?

A Page Load Pixel is a small tracking script that fires when a specific page loads. Unlike a Web URL Goal, which only tracks visits to a static URL, the Page Load Pixel provides more flexibility by capturing page views even on dynamic URLs or single-page applications (SPAs).

How it works

• A tracking pixel (a small piece of code) is embedded on the target page.
• When the page loads, the pixel fires and sends data to Pathmonk, registering the event as a conversion.
• This method works even if the page URL changes dynamically, making it useful for more complex website structures.

Best for:

• Tracking page-specific interactions (e.g., blog post views, landing page engagement).
• Measuring micro-conversions, such as viewing a pricing page or FAQ page.
• More precise tracking than a simple URL goal, especially when URLs include dynamic parameters.

Advantages of using page load pixels

✔ Works with dynamic URLs: Unlike Web URL Goals, this method can track pages with query parameters (e.g., yourwebsite.com/page?id=123).
✔ Captures micro-conversions: Helps track user engagement before they convert (e.g., product page visits).
✔ Ideal for single-page applications (SPAs): Tracks when a new page loads, even if the URL doesn’t change (common in modern web apps).
✔ More control over tracking: Since it’s a pixel-based method, it provides better accuracy in identifying valuable user actions.

Limitations to consider

❌ Requires adding a tracking script: Unlike Web URL Goals, this method requires a developer to install the pixel.
❌ Doesn’t track specific actions on the page: It fires when the page loads, but it won’t track clicks, form fills, or interactions—use a Visitor Action Pixel for that.
❌ Page reloads may cause duplicate tracking: If a user refreshes the page, the event will be triggered again unless filtered properly.

When to use (and when not to use) page load pixels

Use page load pixels if:

• You need to track engagement on pages with dynamic URLs (e.g., product pages with parameters).
• Your website is a single-page application (SPA) where traditional URL tracking won’t work.
• You want to measure soft conversions like pricing page visits or blog reads.

Avoid page load pixels if:

• You need to track button clicks, downloads, or form submissions—a Visitor Action Pixel is better suited for that.
• You want a quick, no-code setup—this method requires installing a pixel on the site.
• Your tracking goal is purely end-of-funnel conversions (e.g., purchases, form submissions)—a Web URL Goal may be simpler and more reliable.

Visitor action pixel

What is it?

A Visitor action pixel tracks specific user interactions on your website, such as button clicks, form submissions, video plays, or downloads. Unlike Web URL Goals or Page Load Pixels, which track page views, this method records engagement-based actions that don’t require a new page to load.

How it works

• The tracking pixel is placed on a specific element (e.g., a signup button, download link, or embedded video).
• When a visitor clicks, submits, or interacts with the element, the pixel fires and logs the event as a conversion.
• The data is sent to Pathmonk in real time, helping track on-page engagement that wouldn’t be captured by traditional tracking methods.

Best for:

• Tracking CTA button clicks (e.g., “Sign Up,” “Request a Demo”).
• Monitoring interactions that do not involve a page reload.
• Measuring engagement in real-time, such as video plays, file downloads, or interactive elements.

Advantages of using visitor action pixels

✔ Tracks interactions beyond page views: Captures clicks, submissions, and engagements, giving a fuller picture of user behavior.
✔ Works without page reloads: Ideal for single-page applications (SPAs) or modern web designs where actions happen dynamically.
✔ Highly customizable: Can track any element on your site, from menu interactions to outbound link clicks.
✔ More precise than URL-based tracking: Ensures you measure actual user engagement rather than just visits to a confirmation page.

Limitations to consider

❌ Requires setup on each specific element: Unlike Web URL Goals, which apply to any visit to a specific page, you must define each action you want to track.
❌ Needs technical implementation: A developer may be needed to install and test the pixel on specific elements.
❌ Doesn’t track passive page views: If you need to track visits to a page without an interaction, use a Page Load Pixel instead.

When to use (and when not to use) visitor action pixels

Use visitor action pixels if:

• You need to track button clicks, form submissions, video plays, or file downloads.
• Your website uses pop-ups, modals, or AJAX forms that don’t trigger a new URL.
• You want to measure user intent and engagement, not just page visits.

Avoid visitor action pixels if:

• Your conversion happens only when a specific page loads—use a Web URL Goal instead.
• You want an easy, no-code tracking solution—this requires adding the pixel to each element manually.
• You need to track entire page views rather than user interactions—use a Page Load Pixel instead.

3rd party tool integration

What is it?

Pathmonk allows you to track conversions using data from third-party tools, such as HubSpot, Shopify, Calendly, or other CRM, eCommerce, and scheduling platforms. Instead of tracking on-site interactions like button clicks or page views, this method pulls external conversion data from platforms where transactions, bookings, or leads are captured.

This is particularly useful for businesses that generate conversions outside their website, such as:

• Ecommerce stores tracking purchases via Shopify or WooCommerce.
• Service-based businesses tracking bookings through Calendly or Acuity Scheduling.
• B2B companies tracking lead form submissions through HubSpot or Salesforce.

How it works

• Pathmonk connects to the third-party tool where conversion data is stored (e.g., HubSpot, Shopify, Calendly).
• When a new conversion occurs (e.g., a lead is registered, a purchase is made, or an appointment is booked), Pathmonk automatically tracks the event as a conversion.
• This enables cross-platform tracking, ensuring conversions from external forms, e-commerce checkouts, or scheduling tools are included in your analytics.

Best for:

• Businesses using CRM, e-commerce, or scheduling platforms to manage conversions.
• Tracking purchases from Shopify, WooCommerce, or other online store platforms.
• Tracking bookings from Calendly, Acuity Scheduling, or similar tools.
• Tracking leads from marketing automation tools, such as HubSpot or Salesforce.
• Integrating multi-channel tracking into a single analytics system, ensuring conversions from all touchpoints are measured.

Advantages of using 3rd party tool integration

✔ Tracks conversions from multiple sources: Captures leads, purchases, and bookings from external platforms that don’t operate directly on your website.
✔ No need for on-site tracking implementation: Since data comes from a connected CRM, eCommerce, or scheduling tool, there’s no need to modify your website’s code.
✔ Improves lead and sales attribution: Helps measure which external channels are driving the most valuable conversions.
✔ Works seamlessly with automation tools: Can be combined with email workflows, sales sequences, and lead nurturing systems for a complete sales funnel view.
✔ Ideal for appointment-based businesses: Perfect for businesses that generate consultations, demo requests, or service bookings via external scheduling tools.

Limitations to consider

❌ Dependent on third-party data accuracy: If the CRM, e-commerce, or scheduling tool doesn’t capture the conversion properly, Pathmonk won’t either.
❌ Might not track full user behavior: This method records conversions after they happen, but won’t provide insight into how visitors interacted with your website beforehand (use other Pathmonk tracking options for that).
❌ Requires integration setup: Some platforms need API access, webhook configuration, or manual connection to sync properly with Pathmonk.

When to use (and when not to use) 3rd party tool integration

Use 3rd party tool integration if:

• You rely on a CRM (e.g., HubSpot, Salesforce) for lead management and need conversion tracking inside Pathmonk.
• You run an eCommerce store (e.g., Shopify, WooCommerce) and need to track completed purchases.
• You generate appointments or service bookings through Calendly, Acuity Scheduling, or other tools.
• You want a centralized view of all conversions, including those happening outside your website.

Avoid 3rd party tool integration if:

• You primarily track website-based conversions (use Web URL Goals, Page Load Pixels, or Visitor Action Pixels instead).
• You need real-time visitor behavior tracking—this method only records conversions after they’re submitted in an external tool.
• You don’t have access to integrations or API connections in your CRM, eCommerce, or scheduling platform.

Pathmonk thank-you page

What is it?

The Pathmonk Thank-You Page is an automated, trackable post-conversion page that confirms a visitor’s action while providing additional engagement opportunities. Instead of manually building and setting up a thank-you page, Pathmonk generates a pre-configured version that acknowledges conversions and helps keep visitors engaged.

How it works

• Pathmonk automatically creates a thank-you page that appears after a visitor completes an action (e.g., submits a form).
• The page confirms the conversion and can display further engagement options, such as:
  • Suggested next steps (e.g., booking a call, exploring product features).
  • Additional content recommendations (e.g., related blog posts, case studies).
  • Upsell or cross-sell opportunities.
• Since the page is generated within Pathmonk, no extra coding or design work is required.

Best for:

• Businesses without dedicated thank-you pages who still want to track conversions.
• Encouraging further interactions post-conversion to keep users engaged.
• Streamlining tracking setup without technical complexity or development work.

Advantages of using Pathmonk thank-you pages

✔ No need to create a separate thank-you page: Pathmonk handles the setup, making tracking easier.
✔ More than just confirmation: Can guide users to take further actions, increasing engagement and potential conversions.
✔ Works without technical setup: No development work required—just enable it in Pathmonk.
✔ Reduces drop-offs after conversion: Instead of ending the user’s journey, the thank-you page keeps them engaged with relevant suggestions.

Limitations to consider

❌ Less customizable than manually built thank-you pages: While Pathmonk’s thank-you pages provide engagement options, they may not be as flexible as a custom-built page.

When to use (and when not to use) Pathmonk thank-you pages

Use Pathmonk thank-you pages if:

• You don’t have a dedicated thank-you page and need a quick, automated way to track conversions.
• You want to boost post-conversion engagement by suggesting further actions.
• You need a fast, no-code solution for tracking and guiding user behavior.

Avoid Pathmonk thank-you pages if:

• You already have a fully designed, custom thank-you page that meets your needs.

Your conversions are tracked primarily through external platforms (e.g., a CRM like HubSpot).