The External Tracking Script allows you to record page views and track compatible form submissions on websites that are not hosted inside your account. This includes platforms such as WordPress, Shopify, Wix, Webflow, and custom HTML websites.


By installing the tracking script, you can capture visitor activity, attribute conversions correctly, and trigger automations when submissions occur.


Use this setup if you:

  • Embed a platform form on an external website

  • Use a standard HTML <form> (not iframe-based)

  • Want page views tracked for attribution

  • Want workflows to trigger when forms are submitted


Iframe-based or widget-based third-party forms are not supported.

Forms must exist directly in the page’s DOM and use valid HTML <form> elements.

TABLE OF CONTENTS

What Is the External Tracking Script?


The External Tracking Script is a unique JavaScript snippet generated for your account.


When installed on an external website, it:

  • Records page views

  • Tracks compatible form submissions

  • Captures mapped custom field values

  • Stores anonymous activity before form submission

  • Sends tracked events into your CRM for reporting and automation


It acts as the connection between your external website and your CRM.

Important Behavior Notes


No contact or activity record appears until a form submission occurs.


Here is how it works:

  • Page views are tracked anonymously

  • Anonymous activity is stored in the browser

  • Once a form is submitted:

    • A contact is created or updated

    • Previous activity is attached to that contact


This script does not:

  • Create contacts from iframe-based or widget-based forms

  • Track scroll depth, clicks, or session analytics

  • Capture hidden or disabled fields unless explicitly configured

Why You Need It


Without the tracking script installed, you cannot:

  • Record page views on external websites

  • Attribute leads to campaigns correctly

  • Trigger workflows based on external activity


With the script installed, you can:

  • Track forms hosted on external websites

  • Measure page performance in attribution reporting

  • Trigger automations when visitors submit forms

What It Tracks


The tracking script records:

  • Page views

  • Compatible form submissions

  • Workflow triggers based on those events


It does not track:

  • Scroll behavior

  • Click events

  • Time-on-page

  • Cross-domain session analytics

Before You Start


Before installing the script:

  • Ensure your website domain is connected to your account

  • Confirm your form is:

    • A platform form embed, or

    • A standard HTML <form>


Forms inside iframes, popups, or JavaScript widgets will not be tracked.


Step 1: Get Your Tracking Script

  1. Go to Settings → External Tracking

  2. Click Copy Script


Your snippet will look similar to:

<script   src="https://yourdomain.com/js/external-tracking.js"  data-tracking-id="tk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"> </script>


Do not modify the data-tracking-id. It is unique to your account.


Step 2: Install the Script


Paste the script before the closing </body> tag on your website.


<script   src="https://yourdomain.com/js/external-tracking.js"  data-tracking-id="tk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"> </script> </body> </html>

This works for:

  • Custom HTML websites

  • WordPress

  • Wix

  • Squarespace

  • Shopify

  • Webflow


Installation via Tag Manager


If installing through a tag manager:

  • Use a Custom HTML tag

  • Paste the full script without modifying it

  • Trigger on All Pages

  • Verify that the data-tracking-id attribute remains intact


If the attribute is removed, install the script manually in your site footer.


Step 3: Ensure Your Form Is Compatible


Supported forms:

  • Embedded platform forms

  • Standard HTML forms rendered directly in the DOM


Form Requirements


For tracking to work:

  • A real <form> tag must exist

  • Fields must be visible

  • Fields must include valid name attributes

  • An email field must be present


Not Supported

  • Forms inside iframes

  • Popup-based forms

  • Third-party widgets that do not render real HTML inputs


Custom Field Capture


The tracking script captures more than name and email.


Supported Field Types

  • Text fields

  • Text areas

  • Dropdowns (single and multi-select)

  • Checkboxes

  • Radio buttons

  • Number fields

  • Date pickers

  • Ratings

  • File uploads (metadata only)


Field Capture Rules


Fields are captured only if:

  • They are visible

  • They have a valid name attribute


Hidden or disabled fields are ignored unless configured otherwise.


Field Mapping Logic


Fields are mapped using this priority:

  1. Field name matches a CRM property or custom field key

  2. Field label matches a CRM display name

  3. Field name matches label text (case-insensitive)


If no match is found, the value is stored as unmapped_field.


Step 4: View Submissions


To view tracked submissions:

  1. Go to Sites → Forms → Submissions

  2. Filter by External Form Name


Submissions are tagged as:


external form: {form_name}


Step 5: Workflow Triggers


You can trigger automations based on:


Page View Trigger


Fires when a visitor views a page containing the tracking script. Anonymous activity is stored and linked once the visitor submits a form.


Form Submission Trigger


Fires when a compatible form is submitted.


Available filters include:

  • Domain

  • Page path

  • External form name

  • UTM source

  • UTM medium

  • UTM campaign

Advanced Troubleshooting


Enable Debug Mode


Add data-debug="true" to your script:

<script   src="https://yourdomain.com/js/external-tracking.js"  data-tracking-id="tk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"  data-debug="true"> </script>

Open browser Developer Tools → Console to view tracking logs.


Network Checks

  • Look for successful 2xx responses

  • Ensure no CORS errors appear



Check browser Application → Cookies to confirm a session cookie exists.


If missing, browser privacy settings may be blocking tracking.


Common Issues


No console logs

– Confirm script placement and enable debug mode


Form not tracked

– Confirm a real <form> tag and email input exist


Tracking ID missing

– Verify it was not stripped by a tag manager

Example Form Structure

<form name="signup">  <label>Email</label>  <input type="email" name="email" required />  <label>First Name</label>  <input type="text" name="first_name" />  <button type="submit">Submit</button> </form>

Frequently Asked Questions


Q: Can custom fields be captured from external forms?

Yes. Supported custom field types are captured and mapped automatically when properly configured.


Q: Are third-party forms supported?

Only if they render real HTML inputs directly in the page DOM. Iframe-based forms are not supported.


Q: Are uploaded files stored?

No. Only file metadata is captured.


Q: Will this impact attribution reporting?

Yes. Page views and submissions contribute to attribution reporting and workflow triggers.


Q: Why are page views not visible yet?

Page views are stored anonymously and linked only after a form submission occurs.

Need Help?


If tracking is not functioning correctly:

  • Confirm your script is installed before the closing </body> tag

  • Verify your form uses a real <form> element

  • Ensure an email field exists

  • Confirm your tracking ID has not been modified

  • Use debug mode to review console logs

If issues persist, gather:

  • Your website URL

  • A screenshot of your form HTML

  • A screenshot of your External Tracking settings

  • Console log output (if available)


Then contact Support with these details for faster troubleshooting.