Set Up Website Visitor Tracking

Last updated Sep 18th, 2024

Overview

Website visitor tracking allows you to gain rich signal by understanding who is viewing your website and documentation. This guide will walk you through the process of setting up tracking, identifying known users, and maximizing your data collection.

Before you begin, ensure you have:

  • Administrative access to your website's codebase (not required for the basic Google Tag Manager setup)
  • An understanding of basic JavaScript and web analytics (not required but recommended)

Step 1: Installing the Tracking Snippet

  1. Log in to your Common Room account and navigate to Settings.
  2. Click on the "Signals and integrations" tab.
  3. Select "Website visits" to find your unique tracking snippet.

Once you have your tracking snippet, choose one of the following methods to add the tracking snippet:

Option A: Direct Installation

  1. Copy the provided snippet from your Common Room settings.
  2. Paste it within the <body> tag of your website's HTML.

Example:

<script>(function() {
  // Paste your unique tracking snippet here
})();
</script>
</body>

Option B: Using Google Tag Manager

  1. In Google Tag Manager, create a new tag of type "Custom HTML".
  2. Paste the tracking snippet into the tag.
  3. Set the trigger to "All Pages".
  4. Save and publish your changes.

Option C: For React/Next.js/Gatsby Applications

Add the script to a high-level component:

import React from 'react';

const Layout = ({ children }) => (
  <div>
    {children}
    <script dangerouslySetInnerHTML={{
      __html: `Tracking snippet here (avoid duplicate <script> tags)`,
    }} />
  </div>
);

export default Layout;

Step 2: Identifying Known Users

In order to de-anonymize users who might have visited your website, it's important to be able to associate their anonymous visit information (ex: IP address) with identify information (ex: an email or name). Instrumenting places on your website where this information is available helps create this connection.

Tip: Implementing identity calls has been shown to increase deanonymization rates by over 50%

If your website accepts form submissions from users (ex: entering emails in order to get access to a case study, a demo-request form, etc), that presents an opportunity to instrument your code to identify users. Or, when your users log into your product is another opportunity to instrument identification code.

For forms that use standard email or name fields, the Common Room SDK will automatically attempt to de-anonymize users. While Common Room will detect this data most of the time there may be times when you need to do this by adding the following line of code when you have an email available:

window.signals.identify({ email: userEmail })


Below are a few examples of how this call would manifest itself in your website’s code.

Example: Identifying a User After Form Submission

function onUserLogin(user) {
  // Your login logic here

  // Identify the user with Common Room
  window.signals.identify({
    email: user.email,
    name: user.fullName
  });
}

Example: Identifying a User After Login

function onUserLogin(user) {
  // Your login logic here

  // Identify the user with Common Room
  window.signals.identify({
    email: user.email,
    name: user.fullName
  });
}


From your marketing website or your app website, you can issue an API call to identify a user by their email. The same script will work on both your marketing and app website.

It's important to note that this setup only works when both sites share the same root domain (eg. commonroom.io and app.commonroom.io). When the domains are different, visitors sessions cannot be shared.When instrumented correctly with the same root domain, a person who visits your marketing site anonymously and then submits a form or logs into the app will be de-anonymized. However, if the root domains are different, we won't be able to link marketing site page's visits to that identity, and they will remain anonymous.

Step 3: Link Tracking

You can achieve even higher visibility for individual visitors to your website by tracking clicks on links in marketing and sales messages sent to your customers and prospects. You will need to add a parameter to links within message templates in your marketing and sales tools.

Tip: Implementing UTM tracking has been shown to increase deanonymization rates by over 50%

Add the URL Parameter

At the end of each link add the URL parameter cr_email={{email}} using whatever email token is correct for your system.

Email Token/Variable

Email address variables from tools you might be using:

1. HubSpot uses {{contact.email}}

2. Apollo.io uses {{email}}

3. Outreach uses {{email}}

4. Salesloft uses {{email_address}}

Encoded Email Address (optional)

You may prefer to encode the email address. For example, HubSpot uses the following variable for base64 encoded emails: {{contact.base64_email}}

You will need to use an alternate URL param: cr_e={{email}}

TIP: How to Add Parameters Correctly

If this parameter is the first, you will need to add a ? at the beginning.

https://example.com/pricing/?cr_email={{email}}

If the parameter follows others (like UTMs) you will need to add a & like so:

https://example.com/pricing/?utm_source=cr&cr_email={{email}}

FAQs

What info would Common Room tracking provide for existing customers or prospects once we capture them via a form?

When we get the conversion event, we can correlate it with any historical website visits where the user was anonymous, and then blend this with any other signal being captured in Common Room.
For example, if a person visits the integrations and pricing page on your website and then fills out a form 3 days later, Common Room can connect all those dots and show the person's profile post-facto such that you're able to see the historical activity versus just the conversion event, which is what you'd typically see in Salesforce, Hubspot etc.

More importantly though, this is all pulled into the Person360 profile for the contact across all your signals, so website activity is just one of dozens of signals that are captured in the platform at the individual and organizational level, and this is where customers find the most unique and differentiated value.

Does the tracking snippet need to be embedded in the forms of our site?

If you only want to track forms on the website where you're already running our script then no additional actions needed. Our script automatically tracks form submissions that contain an email field. That email field is used to de-anonymize the contact.

If you want to use your product logins to de-anonymize visitors as well, then you'll need to install the script on your app's site as well (which is different from your marketing site) and add an "identify" call to your app code as described in step 2 of this guide. The email passed to that "identify" call is what will be used to de-anonymize the visitor.

Didn't find your answer?Get in touch· Visit ourhelp center