Get going with Exchange Capture – Acoustic Help Center

Overview

Exchange Capture now provides a single interface that streamlines configuration and deployment of Acoustic and certified partner enablements and code. This single interface helps reduce the burden of code development and placement on IT or web development teams. To get started with the Exchange Capture, go to Tools Exchange Capture in Exchange. A new browser tab opens. What happens next depends on who you are:

Note: You must have Exchange to access Exchange Capture. If you don't have an Exchange Account, contact Acoustic Support.

If you are not already linked to an Exchange/DDX ID and you are not an existing Capture user, the Set up tag manager wizard automatically starts and guides you through your initial setup. For Instructions, check out Set up the Exchange Capture tag manager.
If you are an existing DDX user with an Exchange / DDX ID and not an existing Capture user, the Partner enablement window opens. You are almost ready to start using Capture! First, review the major concepts. After you review these concepts, you can start using Capture by going to the next steps.
If you an existing Capture user and not an existing DDX user, nothing changes for you.

With Exchange Capture, you can:

Manage tags from Acoustic and certified partners
Optionally configure deployment group rules to trigger third-party JavaScript and code snippets
Group applicable tags into deployment groups and set rules for when these grops and their tags are applied
Set up individual tag rules within deployment groups to determine when and if the tags should be applied
Deploy deployment groups to either test or production environments
Perform test deployments of deployment groups, and optionally send tag data to the test servers for testing purposes
Use test results to troubleshoot or fine-tune the behavior of tags on pages before you deploy them to production
Disable or re-enable all tags from a particular partner in all deployments

Data collection using tags

To capture data from your site, you use tags. Understanding the various methods to make data available for tagging, tag standards, unique page identifiers, and tag placement on pages is key to making sure you get the data that you need. You should have already received information from the partner regarding their enablement and tagging. For information about implementing tagging in Exchange Capture, see theTagging implementation.

Data identification in tagging

Capture gives you various methods to make data on your website available for tag syndication. Methods include JavaScript objects, HTML, URL, constants, cookies, session storage or local storage. For fields that are not required, Unassigned is displayed unless you specify a value.

Not every tag supports all methods. The methods that are supported for a particular tag type are reflected in the available choices when you configure a tag in Capture. See the following examples of some of the methods you can use to identify data for tagging. The examples use a Digital Analytics Page View tag, with the page ID parameter and Category ID, which are required parameters.

JavaScript Object example

The value that is entered for the JavaScript object name needs to exist on the page exactly as it is entered in the Object Name field in the tag configuration. This is the JavaScript variable name that contains the field value.

Tag Field	Method	Object Name
* Page ID	JavaScriptObject	digitalData.page.pageInfo.pageID
* Category ID	JavaScriptObject	digitalData.page.pageInfo.primaryCategory
Search Term	JavaScriptObject	mySearchTerm
No. of Search Results	JavaScriptObject	mySearchTermsReturned
Page Attributes 1-50	unassigned
Page Extra Fields 1-15	unassigned

digitalData = {
    pageInstanceID'Standard Page',
    page {
        pageInfo {
            pageID:'SearchPage'
        },
        category {
            primaryCategory:'Search'
        }
    }
};
mySearchTerm 'books';
mySearchTermsReturned =;

HTML example

HTML supports two different formats for Capture to read in data from your website. In the first method, the HTML object name between the start and end tags is read.

A code example for page ID:

<p><div id ="pageID">phHome</div></p>

The pageID value is the HTML Object Name that is required to be set in the HTML Attribute Name field. This value must be unique for each tag field.

A code example for Category ID with Attribute Name:

<p><div id="categoryID" catValue="HOME PAGE"/></p>

The optional attribute name is catValue. This value is collected from the HTML tag. For example: catValue="HOME PAGE". If you don't specify an attribute name value in the code, no data is sent. For example: catValue="".

Tag Field	Method	Object Name
* Page ID	HTML	pageID
* Category ID	HTML	categoryID [catValue]
Search Term	JavaScriptObject	digitalData.page.pageInfo.onsiteSearchTerm
No. of Search Results	JavaScriptObject	digitalData.page.pageInfo.onsiteSearchResults
Page Attributes 1-50	JavaScriptObject	digitalData.page.attributes.exploreAttributes
Page Extra Fields 1-15	JavaScriptObject	digitalData.page.attributes.extraFields

URL example

With the URL method, the URL is parsed to find the parameters that are specified in the tag configuration. The tag parameters are then retrieved from the parameters found. For example, with the URL parameters pageId and categoryId, the URL would need:

http://www.mysite.com/?pageId=pgHome&categoryId=HOME%20PAGE

Constant example

This method specifies a constant value that is syndicated for every tag. In Digital Analytics, a constant value that is supported only for "Category ID".

Unassigned example

This method sets the tag parameter to JavaScript null, which is passed in as a tag parameter. The unassigned method cannot be used for required fields.

Tag standards

As a best practice, if your website uses JavaScript to collect data, you adopt the Digital Analytics (W3C Customer Experience Digital Data Layer) tag standards. Capture fully supports the W3C Customer Experience Digital Data Layer tag standards. By default, all Digital Analytics and certified partner tags are configured to use these Acoustic standards. If your website uses the Acoustic standards to surface data, all tags work without requiring extra tag configuration. It is recommended that you surface data in this way. When these standards are adhered to by a client website, Capture can automatically and accurately collect the named parameters (data fields) associated with the specific tag. For additional information about Digital Analytics tag standards, refer to the Customer Experience Digital Data Layer v1.0 Final Report (http://www.w3.org/2013/12/ceddl-201312.pdf).

Tag placement on tagged pages

The Capture tag is configured within Capture tool. Depending on the method that is selected for the Digital Analytics tag parameters, you may need to declare an object in the target web pages to process the data correctly.

The Digital Data Layer is included in the head section on the web page.

Capturetags might also be called in response to visitor interaction with in-page/site elements.

For example, using the JavaScriptObject method for Digital Analytics tag parameters, it is necessary to declare the specified JavaScript Object in target web page HTML:

digitalData = {
  pageInstanceID:'Standard Page',
    page: {          
      pageInfo: {
        pageID:'Shopping Cart',
        onsiteSearchTerm:",            
        onsiteSearchResults:"
      },
      category:{
        primaryCategory:'Checkout'          
      },
      attributes: {            
        exploreAttributes:",
          extraFields:"          
      }
   }
};

Capture service domains

For full Capture functionality, you must allow a number of domains to have inbound and outbound access to your corporate network. In addition, browsers that are used by development, QA and other internal network teams allow JavaScript execution and cookies set by the domains on this list.

To ensure that Capture tools, reporting and data collection function correctly within your internal corporate network, allow the following domains inbound and outbound access to your network.

testdata.coremetrics.com
test.coremetrics.com
data.coremetrics.com
welcome.coremetrics.com
itt.coremetrics.com
tmscdn.coremetrics.com
Any Acoustic-managed data collection domains in use.

Europe data center service domains:

data.de.coremetrics.com
testdata.de.coremetrics.com
welcome.de.coremetrics.com
ftp.de.coremetrics.com

Capture might change the IP addresses associated with these domains without notice, so it is not possible to reliably allow access to these domains by IP.

Capture