Deploying the Integration
Deploying this integration is a simple process that requires the following actions.
Completing the Adobe Integration Wizard
To activate the integration, you must complete the configuration wizard within the Data Connectors interface.
- Navigate to the Data Connectors (formerly Genesis) area within the Adobe Experience Cloud.
- Launch the Demandbase 2.0 integration wizard.
- Choose the desired Report Suite and provide a name for the integration.
- Configure the following items:
|Email address||The primary contact's email address.|
|Description||(Optional) Description for this integration setup.|
|Demandbase API key||You can obtain this from your Demandbase representative.|
|Custom Demandbase Dimension #N||These are the IDs for the 8 optional dimensions. For more information, see Demandbase Custom Dimensions.|
|Send to Adobe Target||If “true”, the Demandbase dimensions will also be sent to Adobe Target using a hidden mbox.
Note: A configured mbox.js file must be implemented on the webpage for dimensions to be collected.
- Configure the following Variable Mappings items:ItemDescriptionDemandbase DimensionsChoose an available eVar variable from your report suite.Demandbase Custom Dimensions (optional)Choose an available eVar variable from your report suite.
- Configure the names for the Custom Dimension (if applicable).
- If you chose to include Custom Dimensions in step 4 and mapped the optional eVar in step 5, then you have to provide friendly names for those dimensions. For example, if you chose to enter “stock_ticker” as Custom Dimension 1, then you should change the box containing “Dimension 1” to “Stock Ticker”.
- Do NOT modify the names of the standard 8 dimensions (i.e. Demandbase SID, Company Name, Industry, etc.).
- Check the box to have the Demandbase Integration dashboard automatically created for you (recommended).
- Review all configuration items and click Activate Now .
Deploying the Integration Code
After completing the integration wizard, you must deploy the integration code to your Adobe Analytics deployment code (s_code).
If you used Adobe TagManager or Dynamic Tag Management to deploy Adobe Analytics, you can easily add the integration code using one of those tools.
- Go to the Support tab and download and save the integration code v2_0_1 resource from the Resources area of the integration.
- If applicable, make any necessary modifications to the code. For more information, see Modifying the Integration Code (on this page).
- Include the Integrate Module if it is not already present in your Adobe Analytics deployment code.
- Deploy the code using one of the following methods:
- Use Adobe TagManager or Dynamic Tag Management to add the code.
- Or, deliver the code to the organizational resource that is responsible for updating your Adobe Analytics deployment code.
Make sure you test deployment for this integration in a development/staging environment before deploying it to a production environment.
Modifying the Integration Code
In most cases, you will not need to make any modifications to the integration code that is produced by the Data Connector wizard.
However, if you do need to make adjustments, some of the code settings are described below.
|s.maxDelay||The maximum number of milliseconds that the Adobe Analytics image request will wait for the Demandbase data before firing off to the Analytics collection server.
Note: This setting applies across all integrations that might be running through the Integrate Module.
|_db._key||Your Demandbase API key.|
|_db._apiURL||The URL template for the Demandbase API.|
|_db._delim||The delimiter used to separate the Demandbase dimension values when they are sent to Adobe Analytics. Changing this setting may cause the default Classification Rules to not function correctly.|
|_db._setTnt||If true, then the integration code will attempt to use a hidden mbox to send the Demandbase dimensions to Adobe Target as Profile Parameters.
Note: This requires that the mbox.js code exists on the page.
|_db._tntVarPrefix||This string is prepended to each Demandbase dimension name before sending to Adobe Target. Example, if this setting has the value “db_” then the dimension “industry” will be sent to Adobe Target as “db_industry”.|
|_db._dimensionsArray||The standard Demandbase dimensions that are sent to Adobe Analytics. It is recommended that you do not modify this setting. The “max_size” property is the number of allowed characters for the dimension before truncation occurs.|
|_db._dimensionsArrayCustom||The custom Demandbase dimensions that are sent to Adobe Analytics. The “max_size” property is the number of allowed characters for the dimension before truncation occurs.|
|_db._cName||The name of the session cookie used to keep the state for the Demandbase API communication.|
|_db._contextName||The name of the contextData variable that is used to sent the standard dimensions to Adobe Analytics. It is recommended that you do not modify this setting.|
|_db._contextNameCustom||The name of the contextData variable that is used to sent the custom dimensions to Adobe Analytics. It is recommended that you do not modify this setting.|
Including the Integrate Module
The integration code requires that the Integrate Module exists within your Adobe Analytics deployment.
If you do not already have the Integrate Module as part of your deployment, please complete the following steps depending on the type of implementation you have.
For AppMeasurement v1.0+
- Unzip the AppMeasurement zip file that you downloaded from Analytics > Admin > CodeManager .
- Open the file named AppMeasurement_Module_Integrate.js.
- Copy and paste the contents of this file into your primary AppMeasurement.js file.Paste it just before the DO NOT ALTER ANYTHING BELOW THIS LINE comment within the file.
For Legacy Code (H-code)
- Download the Integrate Module from the “Resources” area within the Data Connectors UI (under the Support tab).
- Copy and paste the contents of that file into your s_code file.Paste it just before the DO NOT ALTER ANYTHING BELOW THIS LINE comment within the file.
Verifying the Integration
Validate that the integration is successfully capturing data by checking live tracking and reporting.
Use the DigitalPulse debugger tool to verify that Demandbase dimension data is being sent through to Adobe Analytics. After deleting your cookies, reload a page on your website where the integration code has been deployed. Assuming that your current IP maps to an organization recognized by Demandbase, you should see results similar to the following.
Reports & Analytics (formerly SiteCatalyst) includes the two Demandbase context data variables:
Target Mbox includes the Demandbase Profile parameters: You will see this only if you have Target implemented on the page AND you have this integration configured for Adobe Target - see Step 4 in the Adobe integration wizard.
Review your Demandbase reports within Adobe Analytics using the Dashboard that was automatically created for you using the Adobe Integration wizard (Step 7).
Alternatively, you can navigate to the Demandbase reporting within the Adobe Analytics menu structure - see screenshots below.
This data should appear within 24-48 hours of successful deployment.
Frequently Asked Question
What does " #" mean?
The Demandbase Data Connector indicates when an attribute is “Not Available” by setting this default value. There are two common scenarios where the default is set:
- Demandbase detects that the visitor is coming from an IP address that does not belong to a company.
- An Account Watch attribute (beginning with “watch_list”) is used, but the company is not in your Account Watch list.
Why does “ [n/a] ” appear more often for certain attributes?
Demandbase classifies all IP addresses and provides the audience and audience_segment attributes even when the visitor is not coming from a company IP. When audience returns values such as “Residential”, “Wireless”, and “Hospitality”, the rest of the attributes are likely not available.
At times, a visitor’s audience will be “SMB”, but other attributes will show “ [n/a] ”. This means Demandbase is able to classify the visitor as a small business, but the full company profile is not available. This typically happens for the smallest companies, when more than one small business is using the same service provider or block of IP addresses.
If you need to adjust the default value in your implementation, update the line:
_db._nonOrgMatchLabel = "[n/a]";