If you've never used Exchange Capture before, a setup wizard will walk you through so that you are able to start connecting to all of our available partners and exchanging data. 

When you go through the setup wizard for the first time, the wizard:

• Collects your credentials to be added to the embed code. This information is needed to authenticate you when Exchange Capture accesses partner applications on your behalf.
• Allows you to set up global settings for partner applications.
• Generates embed code that you add to the head section of your web pages.

To set up the Exchange Capture in the wizard:

1. Go to Tools > Exchange Capture.
2. Provide a client ID or generate a new one:
   • If you have a client ID, select your client ID in the drop-down:
     1. If you are an existing user, click Connect existing user?
     2. Enter your user name and password. If you don't remember your username and password, click Contact support so that the information can be recovered for you.
     3. Click Next. If your client ID, username, and password are valid, you get the following message: Success! Your client ID has been validated. You can go to the next step.
   • If you don't have a client ID, click Generate your ID. The wizard will automatically generate an ID for you and then you can click Next. 
3. Define global settings for partner applications. Global settings define how pages are identified and how tag processing for deployment groups is performed.
   
   1. Set up a unique page identifier for your partner applications by configuring a method. For information about unique page identifiers, check out Unique page identifiers. For information about methods, check out Methods and their associated parameters.
   2. Select a deployment group tagging process for deployed tag groups. This setting is important when an individual page belongs to more than one deployment group.
      • Execute tags in all tag deployment groups - If you have multiple deployment groups deployed, execute all tags in the deployment groups.
      • Execute tags in only the first tag deployment group - Execute all tags in the first deployment group which satisfies the deployment group rules criteria. Tags in any other deployment group are not executed.
        

        If you deployed the same tag across multiple deployment groups that each include the same page and you select Execute tags in all deployment groups, the tag is syndicated multiple times. In this scenario, selecting Execute tags in only the first deployment group prevents the same tag that has been deployed in multiple deployment groups from being syndicated more than once.

   3. Choose tracking options to stop tracking tags from executing in specific browsers when the Do Not Track setting is enabled on the browser. By default, the Exchange Capture always executes tracking tags. Available options include:
      • Honor DNT settings in Internet Explorer 10 or later
      • Honor DNT settings in browsers other than Internet Explorer
   4. Click Next.
4. Copy the embed code by clicking the Copy icon and paste the code into the head section of your web pages.

   Note: Only do this if you did not have an account with Digital Analytics DDX. If you already have eluminate.js script embedded on your site from your DDX account, skip this step.

5. Click Done.

You can change your global settings or access the embed code at any time by going to the main navigation and selecting Global settings or Copy embed code.

Unique page identifiers

Exchange Capture relies on page rules logic that is based on unique page identifiers found on your site pages. The unique page identifier is some value (for example, a JavaScript or HTML object that contains a string) that uniquely identifies every site page for which you want Exchange Capture to manage tags.

A unique page identifier needs to be on every page that you want to evaluate for deployment  rules. If Exchange Capture cannot find the unique page identifier on a page, no tag data is syndicated for that page, because no deployment group rules can be evaluated.

Optionally, if you require a certain level of granularity in your development, and have pages with different sets of tags and have rules that are applied to them at different stages of testing or production, you can use the unique page identifier to uniquely identify a page in a particular environment. A page that goes through various stages of development to production might have the same page ID, but the version of the page in production is not the same as the version of the page in development. If each of the page versions needs a unique set of tags and applied rules, you can distinguish them by using a different unique page identifier for each version.

By default, unique page identifiers in Exchange Capture  are JavaScript objects. They can also be values based on a number of other methods, including cookie, HTML object, URL, local or session storage, or HTML meta tag. The values for the unique page identifiers can be the same as your page ID parameter values, but you must still explicitly specify what data object Exchange Capture uses for the unique page identifiers. If you already have an HTML object that is defined for Page IDs, you can use that same object as your unique page identifier method.

Examples

Here are examples you can use to define the unique page identifier for a deployment group with one deployment group rule that states Page Identifier equals product.

• JavaScript Object - Using this method, deployment group rules look for the JavaScript Object that was provided in the Global Settings>. For example, if you enter digitalData.pageInstanceID, you need to ensure that every page on the website has a JavaScript object similar to this, where dd-standardpagesis the value of the unique page identifier:

  var digitalData = {pageInstanceID:"dd-standardpages"};

• URL - Using this method, deployment group rules evaluate against the entire URL (not just URL parameters) to find a matching value for each rule condition. For example, if your product page URL is http://www.mysite.com/shop/product/dinnerware-4-piece-setting?ID=1234&CategoryID=5678, the deployment group rule finds a match (the URL contains the word "product") based on the deployment group rule Page Identifier equals product. Using "ends with" in your deployment group rule for a URL, might not always work, because your site might append parameters to the end of the URL.
• HTML - Using this method allows you to specify either an HTML object or an attribute of an HTML object for the deployment group rule to evaluate against.
  • HTML object only - Deployment group rules find the HTML object with the specified ID and look at the inner HTML to retrieve the unique page identifier. For example:

    <p><div id="uniqueIdentifier">product<div></p>

  • HTML object & attribute - Deployment group rules find the HTML object with the specified ID and look for the specified attribute name to retrieve the unique page identifier. For example:

    <p><div id="uniqueId" uniquepageidentifier="product"></div></p>

Methods and parameters

The following table describes supported methods and associated parameters:

What's next?

Next, deploy tag groups by performing these major tasks:

1. Enable partners
2. Configure tags from partner tag templates
3. Create deployment groups
   1. Add tags to deployment groups
   2. Add tag rules to deployment groups
4. Deploy tag deployment groups