Implementation Guide (Adobe Analytics Connector)

Updated:

Overview

The Demandbase Connector for Adobe Analytics assigns Company Profile Attributes to conversion variables and traffic variables in Adobe Analytics. The Data Connector works with Context Variables in Platform 15 and thus requires s_code H23 and above. There are options for how conversion variables can be assigned depending on your business needs and how your Adobe Analytics instance is configured. 

Implementation Steps Summary

  1. Ensure Adobe Analytics is actively used and confirm which version is being utilized
  2. Select Demandbase attributes to capture in Demandbase Setup (guide HERE)
  3. Select which eVars to map to and enable them in Staging and Production (at least one eVar required)
  4. (Recommended) Configure Adobe Data Connector in Staging
  5. (Recommended) Deploy scripts in Staging
  6. Configure Adobe Data Connector in Production
  7. Deploy scripts in Production
    • Option 1: Inline (Recommended)
    • Option 2: Through a Tag Manager
  8. Set up basic reports (guide HERE)

Walkthrough

Step 1: Ensure Adobe Analytics is actively used and confirm which version is being utilized

Step 2: Select Demandbase attributes to capture in Demandbase Setup (guide HERE)

Standard Attributes

For identified companies, the Data Connector automatically sends the following Demandbase attributes to one conversion variable:

  • demandbase_sid
  • company_name
  • industry
  • sub_industry
  • employee_range
  • revenue_range
  • audience
  • audience_segment

Using a second conversion variable, another 8 Demandbase attributes can be integrated. This includes any custom Account Watch attributes. For instructions on how to chose attributes to go Attribute Selection Guide.

Step 3: Select which Conversion Variables (eVars) to map to and enable them for both Staging and Production

To add or edit conversion variables (eVars) follow the steps below:

  1. Click Analytics > Admin > Report Suites.
  2. Select a report suite.
  3. Click Edit Settings > Conversion > Conversion Variables.
  4. On the Conversion Variables page, click the Expand icon [+] next to the conversion variable you want to modify.

    Or

    Click Add New to add an unused eVar to the report suite.

  5. Select the conversion variable fields you want to modify.
  6. Click Save.

Recommended Settings

The appropriate settings for an eVar (conversion variable) are driven by business requirements and definitions as well as the type of reports an analyst wishes to run. The following settings recommendations are based on current best approaches used by marketers. Verify the appropriate settings with business users as well as analysts before deploying your solution.

To enable eVars in the Admin Console, first check the 'Status' box, then select 'Enable'.

Any eVars receiving Demandbase attributes should have the following settings:

Setting Recommended Value Description
Status Enabled

Turns the eVar on for receiving data.

Type Text String

Data type to be stored.

Allocation Most Recent (Last)

Determine which value persists for a visitor -either the first one set or the most recent value.

Expire After Visit

Indicates when value can be re-written for a particular visitor.

Reset Do Not Reset

Unless overwriting/replacing a previously-used eVar

Enable Merchandising Disabled

Enables eVar for Merchandising reports for eCommerce sites.

 

Example Conversion Variable Setup:

 

Steps 4 and 6: Configure Adobe Data Connector in Staging / Production

The fastest and easiest way to add Demandbase to Adobe Analytics is through the Adobe Data Connector (formerly known as the Genesis platform). The Data Connector provides an easy-to-follow wizard interface for capturing attributes into eVars as well as creating dashboards and starter reports.

Leveraging the newest features of the Adobe Analytics platform, the latest Adobe Data Connector enables the integration of up-to 40 Demandbase attributes using up to 5 conversion variables. This is achieved using contextData and a combination of Processing Rules and Auto Classification rules. The Data Connector wizard handles the setup of the Processing Rules and Auto Classification rules. Administrators only need to provision new conversion variables (eVars), as described earlier in this article.

(For instruction videos, follow the links for version 2 and version 3)

1. Go to Admin > Data Connectors

2. Locate the Demandbase Connector in the Other category, then drag and drop it to begin configuration. Make sure you see the orange v3 next to the Demandbase logo.

3. Enter all the basic information and Click Save.

Note: Your Tag UID and API Key will be provided to you by Demandbase team during the implementation.

Screen_Shot_2017-03-15_at_3.56.01_PM.png 

4. Select the eVars you provisioned to capture the concatenated attributes. Important: If you're switching from the Legacy version of the connector, it's best to reset your eVars, or provision new ones.

Screen_Shot_2017-03-15_at_3.53.54_PM.png

5. Set the names of the attributes you want to use in the Auto Classifications. The first 8 are filled automatically, and the second 8 should be filled in as needed.

6. Under Classification Rule Sets, always check the first box. Check the other boxes only if using more than the 8 standard attributes.

Screen_Shot_2017-03-15_at_3.56.36_PM.png

7. Check the box next to Demandbase Integration to create a default report.

Screen_Shot_2017-03-15_at_3.58.07_PM.png

8. Review your setup.

 

Steps 5 and 7: Deploy Scripts in Staging / Production

At the end of running Demandbase Data Connector V3, under the Support tab you'll find 2 links for downloading 3 scripts. The first set of scripts is for deploying the API call and the callback script. The second is the snippet for your AppMeasurement library. 

 

Script Deployment Guide:

Option 1: Deploy Scripts Inline (Recommended deployment)

1. Deploy 2 tags to the head in the global template to optimize against racing condition with Adobe's image request.

2. Deploy another snippet for s_code.js to read the cache.

Example HTML Setup: Changes to your global template.

Example S-Code Changes: You only need to add a small snippet in the s_code to read the cached data.

Screen_Shot_2017-03-15_at_3.30.17_PM.png

Option 2: Deploy Scripts through a Tag Manager

Deploying using a tag manager means you will introduce another layer of asynchronicity (the tag manager code is async as well) and other variables of the TMS such as firing order and priority. This means Demandbase cannot guarantee you're optimized, and you may need your own technical resources to improve the identification rate.

1. Deploy 2 tags to the head in your tag manager. 

2. Deploy another snippet for s_code.js to read the cache.

For more instructions to how to deploy via different tag managers follow the links below:

Note: After the code deployment additional configuration tweaks might be required before implementation can be considered complete. A Demandbase Engineer will identify those during the Technical Implementation Call.

Step 8: Set up basic reports (guide HERE)

 

Additional Information

Auto Classification Rules

The Adobe Data Connector will automatically create Auto Classifications as seen here. Auto Classifications are an innovation and relatively new feature of Adobe Analytics. Unlike a traditional (SAINT) Classification, which requires an offline process and uploading of data, Auto Classifications are run automatically. Further, Demandbase attributes are captured in real-time.

Using Classification Rules, several Demandbase attributes (generally up-to 7) can be sent to a single eVar then broken-out into a Classification.

Important Note: There is a 255-character limit on eVars. If this limit is exceeded the image request will fail. When combining attributes into a single eVar, be sure to cap the maximum length of each eVar.

For further details on Classification Rules talk to your Adobe Customer Care Representative, and see: https://microsite.omniture.com/t2/help/en_US/reference/index.html#Classification_Rules.

  

Data Flow Summary

Was this article helpful?
1 out of 1 found this helpful