AEM 6.1/6.2 Setup Guide

Updated:

 

About This Document

This not an official implementation document but merely a guide and snapshot as of the date of this document from 2017. Your Adobe Consultant might find it useful but they should be the main point of contact to implement this integration as this integration uses AEM's own mechanisms for ingesting data. A lot can change and this document may become outdated but we will try to keep it up to date as much as possible. Demandbase offers and supports our Company API for the ingestion mechanism to consume our data and that is the scope of Demandbase's role in this integration.

Assets

Assuming you have an Engagement license and are ready to implement, you will need to contact your CSM for acquiring the API key and URL for AEM.

Guide

AEM 6.x third-party data uses a hybrid of AEM 5.x ClientContext + AEM 6.x ContextHub. You will need ClientContext installed to leverage the Segmentation offered in JSONP Store. This is how Adobe designed it. See their docs for more information.

See Adobe Segmentation Docs

First Setup Segments in ClientContext

Switch the URL of your page to go to the old UI

Remove everything starting at "etc/..."

 

Replace it with "miscadmin"

Go to ClientContext and open it up to begin creating segments.

 

Follow our guide from AEM 5 to setup the store and segments

Click for Segments/Store SETUP GUIDE

 

Create a new ContextHub Module

From the AEM Experience Manager home menu select "Tools"

 


Operations

Cloud

 

ContextHub

 

Enter the default or your own configuration

 

Click the Configuration text, NOT the pencil icon


 

Create a new ContextHub

 


 
 

{
"service":
 {
  "jsonp": true,
  "host": "api.demandbase.com",
  "path": "/api/v2/ip.json?key=[YOUR_DB_KEY]"
 }
}

 


 

Create a new ContextHub UI Module

 

This will allow us to use the ContextData in the new UI

 

From the main ContextHub Configuration Menu, now we will do a UI Module

 

 

Supplemental Code:

  • The template {{demandbase.company_name}} is interchangeable - it's mainly for naming convention in the UI
  • The storeMapping is what you named the ContextData store name.
  • template refers to a template used creating the UI component in contexthub

{

  "icon": "coral-Icon--home",

  "title": "Company",

  "storeMapping": { "demandbase": "demandbase" },

  "template": "<p>Company</p><p>{{demandbase.company_name}}</p>"

}

 

Example Connecting Segments to Content

  1. From left navigation select Sites and choose Geometrixx Outdoors package as an example. Open the Geometrixx Site by clicking the whole thing.
  2. Now click pencil icon on a Page within to open it up.

 

Select Targeting from top-right menu

 

Create a new Campaign or use an existing one

 

Name the activity/campaign

 

Create a new Experience by clicking the plus on the top right-hand side.

 

 

Hover over an element and click it to popup the Wrench.

  1. Click the wrench icon if you want to modify the default behavior
  2. Otherwise click the Target/Dart icon to add a new offer to variation 

  1. Click the + to enable modifying the Offer

 

Click an area such as the banner and the edit menu shows up. As an example Click the WRENCH icon to modify the banner URL.

 

 

Upload a new Image 

 

 

Click NEXT to choose an Audience for this Experience - remember we created one already in ContextData for Audience === SMB. So we'll reuse that segment here.

 

Click through and Save with the defaults.

 

Now you can Preview - to see your experience you must have an IP that matches your segment if you used DB data.

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