Set Up the Demandbase Adobe Analytics Launch Extension

Step 1: Prerequisites

1. Obtain your Demandbase Adobe API Key from your Demandbase CSM.
2. Install these extensions in Adobe Launch.
   • Core
   • Adobe Analytics
   • Demandbase
3. Add the Adobe Analytics dev and production report suite IDs.
4. Create up to five eVars in Adobe Analytics.
5. Confirm:
   • Launch is deployed on your website
   • You have Launch administrator access
6. Inform your Demandbase CSM so the implementation can be reviewed.
   Tip: Run Adobe Analytics prior to installing Demandbase to simplify troubleshooting.

Step 2: Create and Map Data Elements

1. Create one Data Element per eVar.
   Tip: Name the Data Elements the same as your eVars for easy mapping.
2. Map the Data Elements as follows:
   • Extension: Demandbase
   • Data Element Type: Select the corresponding element
   • Storage Duration: Session
     

Step 3: Configure the Demandbase Extension

1. In the API Configuration section, enter your API Key.
   
2. Set the IP-API Call Timeout value,  which determines how long the extension waits for the Demandbase API to identify the visitor. 
   Tip: Longer timeout values allow for more data to be collected.
3. In the Default Values Configuration section, enter the default values to send to Adobe. Default values reduce report noise by grouping undefined or irrelevant data.
   • Non-Company Visitor: Traffic from residential or unidentified IPs
   • Non-Target Account: Companies not in a defined target account list
   • Target Account but Attribute Unavailable: Target accounts missing a specific attribute value
   • Unavailable Attribute: Attributes returned as NULL or empty
4. In the Data Elements Configuration section, enter the values for each eVar in its data element tab.
   Tip: Two Data Elements are preconfigured by default and can be modified if needed.
   • Each Data Element contains up to eight Demandbase attributes.
     • Attributes are stored in order: Attribute 1 → Attribute 8
     • Each attribute uses the Demandbase API variable name (for example, Attribute1: company_name).
   • To include watch list attributes, prefix them with watch_list_<attribute_name> (for example, watch_list_campaign_id).

Step 4: Configure the Demandbase Firing Rule

You must have two sets of firing rules. The following steps use the Adobe Analytics Action from Launch but you can also use the Adobe Analytics Launch Extension.

1. Create a new rule with the name Page Load: Fire Demandbase.
2. Add an event as follows:
   • Select Core Library Loaded (Page Top).
   • Event order: 1
3. Add an action as follows:
   • Extension: Demandbase
   • Action Type: callDemandbaseIpApi
   • Name: Demandbase - callDemandbaseIpApi
     
     

Step 5: Set eVars and Fire the Beacon

1. Create a second rule with the name Demandbase Complete: Fire Pageview.
2. Add an event as follows:
   • Extension: Demandbase
   • Event Type: API Call Finished (Success, Fail, or Timeout)
   • Name: Demandbase - API Call Finished (Success, Fail, or Timeout)
   • Order: 50
     Tip: Since you’re firing this rule consecutively to the Demandbase API rule, it should have a higher order number.
     
3. Add an action to set eVars as follows:
   • Extension: Adobe Analytics
   • Action Type: Set Variables
   • Name: Adobe Analytics - Set Variables
   • In the Variables section, map the eVars to the data elements.
     
     
4. Add an action to send the beacon as follows:
   • Extension: Adobe Analytics
   • Action Type: Send Beacon
   • Name: Adobe Analytics - Send Beacon
     
     

Step 6: Combine Events and Send a Single Beacon *s.t() call*

Because multiple Adobe s.t() beacon calls are costly, you can combine events so the beacon fires only after all required events complete.

This requires custom JavaScript because Adobe Launch uses OR logic and does not support combining events using AND rules. 

Tips:

• To control the amount of time to wait for the Demandbase event, use the Extension timeout setting.
• All events must be combined before you can use them under a single Send Beacon Action.

1. Modify the API call rule from Step 4: Configure the Demandbase Firing Rule. 
   1. Complete Step 4.
   2. Add a new action as follows:
      • Extension: Core
      • Action Type: Custom Code
      • Language: Javascript

   3. Open the Editor and paste the following code snippet to keep track of the API event.

      window.demandbaseHasCompleted = false;

   4. Select Keep Changes.
      
2. Modify the set eVars rule from Step 5: Set eVars and Fire the Beacon.
   1. Complete Step 5.
   2. For clarity, rename the rule to Demandbase Complete: Set Evars.
   3. Remove the Adobe Analytics - Send Beacon action. A new rule with the action is created in another step to combine events.
   4. Set event order for Demandbase - API Call Finished (Success, Fail, or Timeout) to 2. 
   5. In the Conditions row, add a new Condition as follows:
      • Logic Type: Regular
      • Extension: Core
      • Select Custom Core

   6. Open the Editor and paste following code snippets to indicate the complete state of the API.

      window.demandbaseHasCompleted=true;
      return window.demandbaseHasCompleted;

3. Add a rule for an event.
   The following steps show a Page Bottom event as an example. Page Bottom is typically the best place to fire the beacon.
   1. Create a new rule as follows:
      • Name: For example, Demandbase - page bottom completed
      • Event: Core - Page Bottom
      • Order: 3
      • Action: Custom Code
      • Select Javascript.

   2. Open the Editor and paste the following code snippet:

      window.pageBottomFired = true;

   3. Select Keep Changes.
      

   4. Repeat this step for every event you want to include in the combined rule. For custom events or additional Core events, create a rule following the same pattern and use custom code to set a completion flag in the DOM.

      For example, if you create a rule named MyCustomEvent, add this in the Action custom code:

      window.myCustomEventIsComplete = true;

4. Create a final rule combining the events.
   Important: If your rule has more than one event, each must have a corresponding Complete event (from step 3). If not done, some events can cause the rule to trigger before all events are completed.
   
   For example, combine the Demandbase API event with a Page Bottom core event.

   1. Add Page Bottom event.
   2. Order: 100
   3. Add Demandbase - API Call Finished (Success, Fail, or Timeout) event
   4. Order: 5
   5. Conditions: Custom Code

   6. Open the Editor and paste the following code snippet to combine the AND events.

      return !!window.pageBottomFired && !!window.demandbaseHasCompleted;

   7. Select Keep Changes.
   8. Action: Adobe Analytics - Send Beacon
      
      
      The following screenshot shows the ending screen.
      

Step 7: Set up Classification Reports

1. For each eVar, create classification reports in Adobe Analytics. See Adobe's article Conversion Classifications.
   

2. Create one classification rule per eVar to split the eight attributes. 
   Use the following Regex for all rows:

   ^([^:]*):([^:]*):([^:]*):([^:]*):([^:]*):([^:]*):([^:]*):([^:]*)$