Contact Website Tracker for Contact-Level Activity and Attribution – Propensity

What this is

The Contact Website Tracker provides visibility into contact-level website activity.

Unlike the Account Website Tracker, which aggregates engagement at the company level, the Contact Website Tracker displays individual contacts who have been identified through website activity.

This view allows you to analyze:

Which contacts visited your website
When they visited
What pages they viewed
How they arrived
Whether they are part of ICP accounts
Which campaigns or plays may be associated

Website tracking must be installed before contact-level data appears.

Website Tracking Script

The Website Tracking Script used for Contact Website Tracker includes a required parameter that enables both account-level and contact-level data capture.

When you access the script from the Contact Website Tracker section, the script automatically includes the required configuration to capture contact-level data.

Important:

The script available in the Account Website Tracker section captures account-level data only
To enable contact-level tracking, you must use the script provided within the Contact Website Tracker section
Installing both versions of the script, or installing the account-level script before the contact-level version, may prevent contact-level tracking from functioning correctly
If you are switching from account-level tracking to contact-level tracking, replace the existing script rather than adding a second one
Only one tracking script should be installed at a time

For installation instructions, see How to Set Up the Website Tracker

Passing custom metadata into the tracking script

The Contact Website Tracker also supports passing additional metadata through the tracking script. You will need to add this to your script if you would like to use it.

This code line should be included right above the "</script>" line.

By default, the tracking script includes:

propensity("propensity-000853", true);

An optional third parameter can be added to pass additional metadata into Propensity.

Example:

propensity("propensity-000853", true, {
  "user_id": hs_user_id,
  "company_code": "TEST"
});

Additional metadata may include:

CRM user IDs
HubSpot user IDs
Internal company identifiers
Other JavaScript variables available on the page

This metadata can later be returned alongside website tracking results and sales alerts.

Contact Table

The main section of the Contact Website Tracker displays a detailed contact table.

Each row represents an identified contact.

The table includes the following columns:

First Name - Contact’s first name
Last Name - Contact’s last name
Email - Identified email address
Mobile Phone - Contact’s phone number
Job Title - Reported job title
Company - Associated company
Website - Company domain
ICP Account - Indicates whether the associated company is part of your defined ICP
Visit Time - Timestamp of the website visit
Visit Source - Source of the visit
Page Visited - Specific page accessed
Referrer - Referring source or URL
Device - Device used during the visit
Campaign - Associated ABM campaign
Play Name - Associated play within the campaign
Location - Geographic location of the visit

Data can be exported via CSV or Excel.

Filtering and Search

The Contact Website Tracker includes:

Search functionality
Filtering options

Filters allow you to refine contact-level results based on available criteria.

Date filters impact which visits appear in the table (date range, campaigns).

How this view differs from Account Website Tracker

Account Website Tracker:

Aggregates engagement at the company level
Displays page visit counts per company

Contact Website Tracker:

Displays individual contacts
Shows detailed visit-level information
Includes campaign and play associations when applicable

Both views rely on the same website tracking installation.

Salesforce Contact-Level Website Tracking

CRM Sync Configuration (Salesforce)

To push contact-level website tracking data into Salesforce, you must configure your CRM Sync Settings correctly.

Select: Account update only and Contact upsert

This ensures:

If the Account already exists in Salesforce, Propensity updates the existing Account record
If the Account does not exist, a new Account is created
Associated Contacts are updated accordingly
Contact-level website visits are properly attached

Contact-level website tracking must be associated with an Account in Salesforce in order to sync correctly.

Manually Syncing contacts

When observing your contact website tracker table, you will notice the CRM Links column. If the Salesforce or Hubspot icon is greyed out, that means your contact is not synced to your CRM yet. By clicking one of the icons, you will have the option to search or sync to your selected CRM (depending on which icon you clicked).

Example using Hubspot

Viewing Contact Website Visits in Salesforce

Once synced, contact-level website tracking data is available in Salesforce under:

Account → Related → Website Visits

This related object displays:

Which contacts visited
The specific pages they viewed
Visit-level details associated with the Account

Important considerations

If the Campaign and Play columns are not populated, the visit was not attributed to an ABM campaign. This typically indicates a direct website visit rather than campaign-driven traffic
Contact data appears only after tracking is properly installed
Contact identification depends on available matching data
Date filters affect which visits are displayed