Track Website Visitors and Forms

This page outlines instruction for manual setup of page views and events tracking. For most funnels, the 'Get Code' tab in the Able CDP Dashboard can be used to generate tracking code automatically instead.

Tracking Page Views

Add following code to the website to track website events:

<script type="text/javascript" src=""></script>
window.addEventListener('DOMContentLoaded', function () {
uipe('init', '%%FUNNEL_MARK%%')
uipe('track', 'PageView')

Where %%FUNNEL_MARK%% is the unique code of your Able CDP Funnel.

Able CDP page view tracking doesn't install its own cookies and relies on third-party identifiers such as Google Analytics Client Id to connect customer activity between website pages. Please enable cross-domain measurement in Google Analytics if your landing and lead/order pages are hosted on different domains.

Tracking Lead Forms

When a visitor leaves contact details, such as by submitting a lead form or signing up, send Lead event to associate visitor with the contact details. For example:

 var uipe_form = document.querySelector(`form`)
 if (uipe_form) {
   uipe_form.addEventListener('submit', function () {
     uipe('track', 'Lead', {
       keys: {
         email: uipe_form.elements['email'].value,
         phone: uipe_form.elements['phone'].value,
       lead: {
         firstName: uipe_form.elements['name'].value,
       message: uipe_form.elements['message'].value,

We also have special instructions for tracking Hubspot Forms and Shopify leads and purchases.

The exact way how tracking of leads and sign-ups should be done depends on the implementation of the form you're using to capture leads.

We appreciate that this approach makes it a little harder to install the lead tracking code. We chose to use it as it gives our customers full control over the data that are sent to Able, as well as allows to achieve best in-browser performance. Please contact Able CDP support if you need any help with the form tracking set up.

What else you can do

Send Leads

Send Leads to Google Analytics

The easiest way to attribute leads to Google Analytics user ids is to use Able Customer Data Platform, which does it automatically.

Send Leads to Scoro

Extend form Leads with additional attribution details such as UTM parameters, referrer URL, landing page URL and Google Analytics Click Id and send them to Scoro as Companies and Contacts.

Send Attributed Leads to Salesforce

Being able to keep track of online marketing sources inside Salesforce CRM is a common need. This guide outlines the steps needed to configure Salesforce to store additional fields and instructions to set up visitor tracking necessary for gathering UTM, Landing Page and Referrer URLs along with leads.

Track Purchases

Track Scoro Conversions

In addition to sending attribution details such as UTM parameters, referrer URL and landing page URL to Scoro, Able supports retrieving successful quotes from Scoro, attributing them to website visitors that produced leads and sending Purchase conversions to marketing APIs such as Google Analytics, Facebook Ads Conversion API and Google Ads API.

Track Stripe Invoice Payments

Track Stripe invoice payments by receiving paid invoice web hooks from Stripe and attributing them to the original visitor tracked by Able CDP, allowing to send purchase conversions to Google Analytics and ad platforms such as Google Ads.

Track Salesforce Won Opportunities

Attribute Opportunities Closed Won in Salesforce to the original website visitors that generated the lead and sends successful conversion events to Google Analytics and ad platforms such as Facebook Ads and Google Ads.

Track Clickfunnels Purchases

Adding a server-side integration for tracking and attributing Clickfunnels purchases eliminates missing purchases from Google Analytics, Facebook Ads and Google Ads report, helping to have a precise picture of what campaigns and segments convert.

Send Events Using Webhooks

Events can be sent to Able CDP from custom apps using its inbound webhook. This is convenient to attribute purchases and other conversions that aren't necessarily reflected in the payment system. For example, when the service usage accumulates before being invoiced once a payment threshold is reached or next billing cycle occurs.