Set Up 6sense WebTag 2.0

  • Updated on Aug 26, 2026
  • Published on Jul 23, 2025
  • 13 minute(s) read
Prev Next

6sense WebTag 2.0 overview

The 6sense WebTag 2.0 is a small block of JavaScript that’s placed on your website. WebTag 2.0 collects website visitor activity and interaction data on your website. You can deploy the WebTag through a content management system (CMS), tag management system (TMS), or directly in your website code.

WebTag 2.0 is the latest version of the 6sense WebTag.  

This page helps you to create, configure, install, and verify WebTag 2.0.

WebTag 2.0 configuration

You configure WebTag 2.0 in Settings > Integrations. You can generate multiple WebTags, each with its own configuration for domains and landing pages.

When new features become available for WebTag 2.0, you can update the integration settings to “push” the update to the tag that is already in place on the website or tag manager. The code present on the website or tag manager remains the same.

Pre-existing 6sense WebTags continue to function normally when you enable the WebTag 2.0 interface.

WebTag 2.0 recommendations

We recommend that the WebTag appears on all pages, including any ad landing pages, micro-sites, or marketing automation platform-hosted pages. The JavaScript code is lightweight and loads asynchronously.

For additional WebTag information, refer to:

Prerequisites for WebTag 2.0

  • Before you begin, make sure your 6sense instance has been created.

  • 6sense does not support http/2; only http/1.1 is supported.

Set up WebTag 2.0

Create a WebTag

  1. In the 6sense platform, go to Settings > Integrations.

  2. In the All Integrations tab, select WebTag & APIs > WebTag.

    • If you are using WebTag 1.0, you can view your WebTag 1.0 [Legacy] Code by selecting View Code.

  3. Select Add domains.

  4. Select +Add Domains.

    • At least one domain is required to enable your WebTag. Add all of your domains to make sure all meaningful web activities are accepted and used in 6sense analytics and predictive models.

      Example: Company XYZ owns 4 web domains to help sell their products. They want to track 3 of their 4 domains within 6sense. They would add 3 domains in this section, for example: dundermifflin.com, dundermifflinsaber.com, thedundies.com. The last domain, MichaelScott.com, would not be added to 6sense.

    • Note: Subdomains are automatically covered when you tag the domain. You don't need to add subdomains manually.

  5. Select Create WebTag.

    • A Setup page opens, where you enter basic details, including the WebTag Instance name and WebTag Host Platform.

      Note: If you are using Adobe as your tag manager solution, select HTML Website.

  6. Select Save & Next.

Configure the WebTag

After you create the WebTag, set up your configurations based on your requirements. The configuration options are grouped into Basic Configuration Options and Advanced Configuration Options.

Basic WebTag configuration options

  • Company Details API: The Company Identification API (also known as 6signal API or Company Details API) helps you identify your anonymous website visitors or leads by taking an IP as input and returning company firmographic attributes, segments, and scores associated with the visitor.
    The default is OFF. When you toggle this to ON, then the Company Identification API will help you identify your anonymous website visitor using their IP Address. Refer to the Company Identification API FAQ. To integrate with Google Analytics/Google Tag Manager, refer to Install the Company Identification API on Google Tag Manager [6sense WebTag 2.0].

  • Limit Company Details API Calls: This option works only when the “Company Identification API” in ON. When you toggle this to ON, then Company Identification API calls are limited to one call per user session. 6sense WebTag makes API calls only when data needs to be refreshed. If this option is disabled, then the WebTag makes the API call on every page load.

  • Cookie Tracking: The default is ON. When you toggle this to OFF, Cookie Tracking is disabled in this WebTag. Cookie Tracking is very important for identifying a user across your website pages. You can also integrate cookies on your website cookies. See 6sense Cookies & Browser Storage for a list of cookies and more information on disabling and re-enabling the cookies.

Advanced WebTag configuration options

  • Event Tracking: The default is ON. When you toggle this setting OFF, 6sense cannot track user interactions across your website pages.

    Events include user interactions such as:

    • HTML meta-tag “description” value

    • HTML meta-tag “keywords” value

    • Page Title

    • Page Loads

    • Form Interactions and Submits

    • Link, Button, and Object Clicks

    • Video Events

  • Set Custom Meta Tags: Your website might have additional metadata tags that contain useful information and need to be captured. Use these fields to tell the 6sense WebTag to capture additional metadata tags.

    Your 6sense Onboarding Consultant may instruct you to configure this setting.
    Tip: If you need additional guidance, work with your 6sense CSM to choose the appropriate properties based on your business needs and compliance requirements.

  • After selecting the required configurations, select Save & Next.

Install the WebTag

After you configure the WebTag, follow the installation instructions based on the WebTag Host Platform you selected.

Get the WebTag code

  1. Select Download in a TXT file to download the WebTag code.

  2. Select Copy to clipboard to copy the WebTag code.

  3. Select Email this Code to send the WebTag code to your development team.

You can also select View Code to download, copy, or send the WebTag code from the Manage page. To send the WebTag code by email, see Send WebTag 2.0 Code to Your Development Team.


Install the WebTag using HTML

If you selected HTML Website as the hosting platform, follow the installation instructions provided in the 6sense WebTag UI or follow the steps below:

  1. Copy the 6sense WebTag code.

  2. Open the HTML codebase of your website.

  3. Paste the WebTag code just above the closing </head> tag of your codebase.

    If an existing 6sense WebTag is present, replace it with the new WebTag 2.0 code.

  4. Publish the changes.

  5. In the 6sense WebTag UI, select the checkbox to confirm that you have installed the WebTag, and then select Finish.

In-line deployment is preferred. The tag must be placed on every page of your website, including microsites, landing pages, and conversion pages.

Install the WebTag using Adobe Launch (Data Collection)

If you selected HTML Website as the hosting platform for Adobe Launch, see WebTag 2.0 Guide: Adobe Launch (Data Collection) Installation.

If an existing 6sense WebTag is present, replace it with the new WebTag 2.0 code.

The 6sense WebTag 2.0 is not compatible with the existing 6sense Adobe Launch Extension App. Follow the above guide to achieve the same functionality.

Install the WebTag using Google Tag Manager (GTM)

If you selected Google Tag Manager as the hosting platform, follow the installation instructions provided in the 6sense WebTag UI or see Install WebTag 2.0 using Google Tag Manager (GTM).

If an existing 6sense WebTag is present, replace it with the new WebTag 2.0 code.

If you are updating WebTag 1.0 to 2.0 and have the 6sense Company Identification API installed with Google Tag Manager, see WebTag 2.0 Guide: Install the Company Identification API on Google Tag Manager & GA4.

Verify the WebTag

After you install the WebTag, verify that it is behaving correctly on your website. For instructions, see How to Check if the 6sense WebTag is Firing.

Traffic from the WebTag can take up to 24 hours to begin flowing into your 6sense Sales Intelligence(SI) App.

Salesforce Marketing Cloud Account Engagement (Pardot) iFrames and Smart Form Fill

For a Salesforce Marketing Cloud Account Engagement form with Smart Form Fill, place the WebTag 2.0 code inside the Salesforce Marketing Cloud Account Engagement iframe, as shown below.

<iframe src="https://pardot.6sense.com/l/123456/123examplesource456">
#document
<!DOCTYPE html>
<html>
<head></head>
<body>
<form accept-charset="UTF-8">
<script type="text/javascript">
</script>
<script id="6senseWebTag">

FAQs

Why should I implement the WebTag?

70% of the buyer’s journey consists of anonymous research, website visits, and other interactions that most sellers and marketers don’t know about. Traditional sales and marketing solutions are designed for known contacts and accounts that show up in your known funnel. 6sense lights your Dark Funnel with our patented Company Graph, which identifies anonymous accounts more accurately than any other vendor, giving you visibility into your full funnel so you can select and work the best accounts for your business based on the intent they’re exhibiting.

Do I need to remove my old/existing 6sense WebTag if I upgrade to WebTag 2.0?

Yes. Please replace the existing 6sense WebTag with the new WebTag 2.0 code. Only one 6sense WebTag should be present on a page.

What data does the WebTag collect?

The WebTag collects a combination of IP address, cookie ID, and advertising ID (from mobile devices where available) from website visitors. The data stored in the cookie is the unique identifier of the user that gets deleted if the user clears their cookie. 6sense looks to match these data points against its Company Graph to identify the account (company) to which that visitor belongs. 6sense does not de-anonymize at the person level, but only matches the account to which that site visitor belongs.

By default, the tag sends back the following event data to 6sense:

  • HTML page “title” value

  • HTML metatag “description” value

  • HTML metatag “keywords” value

  • Page load

  • Forms

  • Anchor

  • Video

  • Button

  • Object

Can I configure what data the WebTag sends back to 6sense?

By default, the tag sends all data back to 6sense. You can only enable or disable the event tracking configuration.

Yes, customers can configure this setting manually in the Manage WebTag section of your Revenue Marketing platform. This stores temporary values in memory that will not persist across page loads.

That means that all events that happen (clicks, form submits, etc.) on a page view will be linked to the same visitor. However, once that visitor navigates to a new page, the linkage is broken, and there is no way of knowing if this is a different person using the same IP address.

What are the privacy implications?

Like any area that impacts our business, and especially our customers, we devote significant resources through our privacy team and executive leadership to ensure we have robust and up-to-date privacy processes in place in compliance with applicable laws. Our in-house privacy team is supported by best-in-class external privacy counsel that helps us monitor regulatory changes that impact the GDPR and other privacy laws, including the CCPA.

As you implement your account-based strategy, in addition to ensuring that you are getting a high-quality product that will provide real value, you may need to work with your legal and/or privacy teams to confirm you have privacy policies and/or cookie policies in place as necessary to comply with applicable privacy laws.

Specifically with respect to the tag, our customers are responsible for ensuring they have the right to provide the data to 6sense via the JavaScript tag. Although we don’t provide legal advice to our customers on privacy compliance, our customers are generally required to maintain a privacy policy compliant with applicable privacy laws that informs visitors about the use of cookies, the data collected, and how the data is used, for example to deliver content or ads of interest or for other marketing purposes, and that the cookie data may be disclosed to third party vendors (like 6sense) for these purposes. Customers can implement cookie consent programs to obtain necessary opt-out/opt-in under applicable laws prior to the collection of data through the 6sense JavaScript tag.

As noted above, features of our JavaScript tag provide our customers’ webmasters the ability to stop the JavaScript from sending data to 6sense for a visitor if the visitor has either not opted in or has opted out (depending upon how the customer has enabled the features) from the capture of data on the customer’s website.

See the latest version of the 6sense privacy policy.

How effective is the WebTag if cookies are blocked?

IP addresses are our main lookup and we dynamically update our ID graph (not static). Even when cookies are blocked (cookies are already blocked on Safari/Firefox), we have seen minimal impact to our match rates based on the dynamic nature of our company ID graph. In the EU, where GDPR and cookie consent restrictions are more widespread, we have implemented a number of alternate solutions and continue to have strong match rates. Additional updates are available in IP Targeting in the EU.

What domains should I add to my Content Security Policy (CSP)?

Add the following domains to your CSP:

  • *.6sc.co

  • *.6sense.com

Does the 6sense WebTag script load asynchronously?

The script placed on the website is not set to load asynchronously, but it is very lightweight and does not impact page load times. If setting this script to load asynchronously is a requirement, this can be added with no change to functionality. The contents of this script will load the full 6sense WebTag, which is set to load asynchronously.

Why am I not able to delete a WebTag instance?

If the WebTag is currently being used in an active smart form fill, it cannot be deleted. Please unlink it from that smart form fill before you proceed to delete it.

Why am I not able to disable or deactivate a WebTag instance?

If the WebTag is currently being used in an active smart form fill, it cannot be deleted. Please unlink it from that smart form fill before you proceed to delete it.

Why am I not able to disable the Company Identification API setting?

The Company Identification API is required for Smart Form Fill to work. If you are using Smart Form Fill, you cannot disable this setting.

While we do not provide legal advice to our customers, our customers typically provide notice in a privacy policy or use cookie banners, in accordance with the Customer’s privacy policies and cookie consent settings. Where legally required, our customers implement cookie consent programs to obtain necessary opt-out or opt-in depending on applicable privacy laws prior to collection of data through the 6sense JavaScript. Features of our JavaScript provide our customers’ web admins the ability to stop the JavaScript from sending data to 6sense for a visitor if the visitor has either not opted in or has opted out (depending on how the customer has enabled the features pursuant to its privacy and cookie consent policies).

In regard to the GDPR, and without offering legal advice, the EU has the ePrivacy Directive, which is implemented through individual country privacy laws. In general, the EU ePrivacy Directive requires informed consent for the placement of a cookie or use of another technology that stores or accesses information on a user’s device. There are exceptions to the consent requirements, for example, for technical storage and access purposes and where strictly necessary to provide a service requested by a subscriber. The scope of these exceptions (for example, whether it includes analytics cookies) differs among some member countries. Many of our customers follow the most restrictive approach, while others adopt different approaches based on the countries in which they do business and the types of services they provide to their subscribers. Some customers consider the collection of cookie data analytics as essential for running their business. This varies based on the customer and their use case.

Regardless of the above, there are two components to the 6sense webtag: (1) the JavaScript, and (2) the cookie. Features of the 6sense webtag provide our customers’ web admins the ability to either: (1) place both the JavaScript and cookie behind a cookie banner, or (2) place just the cookie behind the cookie banner while allowing the JavaScript to fire.

The 6sense JavaScript allows for account identification without dropping a cookie. In this case, while our customer will not collect cookie information to track a specific visitor’s journey, the JavaScript will be able to identify a specific account that has visited the customer’s website, and information such as date/time of access, browser used, etc., to provide value to the customer. Many customers consider this an important use-case because it allows for website personalization based on the account that is visiting the website.

Note that all data displayed as a result of collection by the 6sense JavaScript is at the “company level,” and 6sense does not identify a person from the JavaScript data that we collect. 6sense cannot and does not identify individuals through this process.

Related articles