Control Tag Implementation Guide

The Salesforce Audience Studio is activated by adding the Audience Studio Control Tag to your website pages. The Control Tag is asynchronous, meaning that it is non-blocking and is optimized for faster page load times. The JavaScript code should be placed in the <head> section of your pages to take advantage of all platform features. Data will start to log in the platform approximately 24 hours after you have implemented the tag.

To implement and test the Audience Studio Control Tag:

  1. Determine Site and Group Structure
  2. Generate Control Tag(s) and copy code snippet in the <head> section of your pages. If you wish, you may first place the code in your development environment before copying to production.
  3. Verify the Control Tag by checking that Audience Studio’s pixel.gif fired on your Site.

For each business need, you will need one Control Tag per configuration (config). For many Audience Studio clients, this will only require one Control Tag for one Site. However, if you wish to manage the configuration for different business units separately, namely in managing and publishing tags across your Sites, then you may wish to implement one Control Tag per Site.

Note: Audience Studio strongly recommends that the Control Tag be used as is: any edit or modification of the Audience Studio Control Tag is at your own risk and will not be supported by Salesforce Audience Studio.

Step 1: Determine Site and Group Structure

Following are some recommendations on setup based on the number of Sites and the complexity of your business. Please discuss your individual needs with your Salesforce Audience Studio Solutions team to determine the most appropriate setup.

  1. One Site = One tag (no Site filter required for reporting)
  2. 2-10 Sites = 2-10 tags (filtering available at the Site level)
  3. More than 10 Sites: You may want to consider grouping Sites based on business unit for managing user permissions and report filtering (at the group and Site level)

You may also associate a group name to each Site. A group is simply another level in the Site hierarchy to simplify the navigation and management of a large number of Sites. If groups exist, an additional filter will be included anywhere a Site filter currently exists for reporting to allow a user to filter results by a group of Sites, and then further to specific Sites within a group. In addition, the administrator can offer users access to specific groups or Sites. For example, all Sites in GroupA (which includes Site1 and Site2) plus individual access to Site4. If group access is provided, then that user will have access to any Site associated to that group in the future.

Step 2: Generate Control Tag(s)

To create the Control Tag use the Audience Studio Console to create a new control tag for each site. Visit Manage >>Sites in the top navigation of Salesforce Audience Studio Konsole.

At the top of the site list click the + Create Site button and provide a name. Each one you create will get a Salesforce Audience Studio Conf ID (configuration ID).

Implementing the Control Tag

Retrieve your Control Tag(s) for the websites and landing pages by visiting Manage>> Sites in the top navigation of Audience Studio and clicking the </> (Actions) button on the right.

Choose JavaScript then click the Copy to Clipboard button. 

For best results, we recommend placing the Control Tag directly on the page in the <head>. This proper deployment ensures that you benefit fully from all Audience Studio data collection and personalization capabilities. Audience Studio platform clients can use the SuperTag application as your Tag Management System. SuperTag enables you to easily manage all tags (including 3rd party) through a single interface in the Audience Studio platform, and use your best-in-class Audience Studio audience segments to inform tag delivery.

Note: The Control Tag should never be deployed within an <iframe>.


Sample Control Tag

! IMPORTANT: Do NOT attempt to copy and paste the example below. The text in RED indicates configuration IDs that are generated in the Salesforce Audience Studio Konsole.

<!-- BEGIN Salesforce Audience Studio ControlTag for " YourSampleSite " -->

<script class="kxct" data-id="<YourSampleSiteID>" data-timing="async" data-version="3.0" type="text/javascript">



   var k=document.createElement('script');k.type='text/javascript';k.async=true;


   var s=document.getElementsByTagName('script')[0];s.parentNode.insertBefore(k,s);



<!-- END Salesforce Audience Studio ControlTag -->

Implementing the Control Tag on AJAX Pages

AJAX pages allow content to be asynchronously loaded without a browser refresh as visitors view a page. When AJAX does change the page, you want the Control Tag to fire when those changes occur for the information Audience Studio should track.


  • The Audience Studio AJAX API requires the Javascript ControlTag to be deployed on the page.
  • Be aware that the Audience Studio AJAX API will fire ALL of your tags again to ensure the necessary information is scraped and captured.

The Control Tag AJAX API can to be called after the AJAX page is loaded. The AJAX API snippet can be retrieved by navigating to Manage>> Sites in the Salesforce Audience Studio Konsole and clicking the </> (Actions) button on the right.

Sample AJAX Control Tag

Below is an example of an AJAX Audience Studio Control Tag within an AJAX page’s source code.

Krux('ns:acme', 'page:load', function(G) {if(G){console.log('Krux error='+G)}},{pageView:false})

Step 3: Verify the Control Tag

You may use Chrome’s Developer Tools, the Firebug browser extension, or other tools to verify the Audience Studio Control Tag fires.  For AJAX Control Tags, you may see multiple ‘pixel.gif’ listed. The first is for the initial page load. Additional ‘pixel.gif’ files will appear for each additional AJAX load. The number of ‘pixel.gif’ files you see depends on the number of additional AJAX loads.

Note that the beacon will return a 204 No Content. Information about our pixel fire can be found here:

How to use the Chrome Browser to Verify the Control Tag

1.     Navigate to a page on your site where the Control Tag is deployed.

2.     Click the Chrome Menu at the top right of your Chrome browser window.

3.     Select  More Tools > Developer Tools. The Developer Tools pane will open at the bottom of your browser.

4.     At the top of Developer Tools pane are several tabs. Click the Network tab.

5.     The resulting Network tab displays several icons, one of which is for Filter. Click the Filter icon and ensure the form input for Filter appears.

6.     Type “pixel” inside the Filter form input.

7.     Verify that you see a “pixel.gif” from the domain “” in the item list. (You might need to refresh the page if you don't see it)

How to use the Firebug Browser Extension to Verify the Control Tag

The Firebug Browser Extension, which you can install in most browsers, is very similar to Chrome’s Developer Tools. Below is how to use it to verify the Event Pixel.

1.     Ensure that you’ve installed the Firebug Browser Extension in your browser.

2.     Navigate to a page on your site where the Control Tag is deployed.

3.     Click the Firebug icon button at the top of the browser.

4.     The Firebug pane should open at the bottom of the browser.

5.     Click the Net tab.

6.     Once the Net tab opens, type “pixel” in the form input at the top right of the Firebug pane.

7.     Verify that the you see a “pixel.gif” from the domain “” in the item list.

Control Tag Helper

If you have access to the Audience Studio UI, you may also use the Control Tag Helper to validate the Control Tag on the page, as well as see other information captured via the Control Tag.

To bookmark the Control Tag Helper, log into Audience Studio and navigate to Manage > Control Tag Helper. From here, either drag the hyperlink into your browser toolbar or create a new one in your toolbar and manually enter the code provided.

Note that the bookmarklet will only work on pages that have your account’s Control Tags implemented. If you have access to multiple accounts you will need multiple bookmarklets in your browser toolbar. Lastly, go to your web site and open the bookmarklet by clicking on it in your browser toolbar.

If the Control Tag is loaded properly you will see information in the Control Tag tab.


If the Control Tag did not load, or if it does not exist on the page you are viewing, you will likely see "No Control Tag Detected".

Understanding Duplicate Calls

The Control Tag is designed to fire multiple calls and avoid any performance delays. These calls ensure that they are hitting the cache consistently without impacting performance. The second set of calls is made from an iframe, so that it will not impact page load time. This setup allows Audience Studio to read and write cookies in the background. The below image illustrates calls being fired as expected. Although it looks like the calls are duplicated, they are not superfluous requests. Additional verification to ensure the Control Tag is firing correctly may be performed by verifying pixel.gif from fires once.



Additional tags may fire with extension usermatch.gif from The number of usermatch calls would depend on integration partners. These match pixels are used to create usermatch tables with partners to ensure that Audience Studio only sends updated segment populations to the partner for their known users. Audience Studio does not send users that the partner has never seen before. Please contact your Client Partner with any additional questions regarding usermatch pixels.


Have more questions? Submit a request


Article is closed for comments.