Behavioral Targeting

Home Page: When users visit the home page after browsing either Bali Surf Camp, Riverside Camping, or Tahoe Skiing adventure pages, they are categorized as the Family Travelers audience and see a personalized hero section above the Next Adventures section.

Adventure Page: When users view Bali Surf Camp or Surf Camp In Costa Rica adventure pages, they are categorized as Surfing Interest audience and see a personalized hero section on the adventure page.

Magazine Page: When users read three or more articles, they are categorized as Magazine Readers audience and see a personalized hero section on the magazine page.

In the Adobe Experience Platform home page, click Schemas from the left navigation and click Create schema.

In the Create Schema wizard, for Schema details step, select the Experience Event option and click Next.

For Name and review step, enter the following:

• Schema display name: WKND-RDE-Behavioral-Targeting
• Class selected: XDM ExperienceEvent

Update the schema as follows:

• Add field group: AEP Web SDK ExperienceEvent
• Profile: Enable

Click Save to create the schema.

In Adobe Experience Platform, click Datasets from the left navigation and click Create dataset.

In the Create dataset step, select Create dataset from schema option and click Next.

In the Create dataset from schema wizard, for Select schema step, select the WKND-RDE-Behavioral-Targeting schema and click Next.

For Configure dataset step, enter the following:

• Name: WKND-RDE-Behavioral-Targeting
• Description: Dataset to store page view data

Click Finish to create the dataset.

Update the dataset as follows:

• Profile: Enable

In Adobe Experience Platform, click Datastreams from the left navigation and click Create datastream.

In the New datastream step, enter the following:

• Name: WKND-RDE-Behavioral-Targeting
• Description: Datastream to send page view data to Experience Platform
• Mapping Schema: WKND-RDE-Behavioral-Targeting
  Click Save to create the datastream.

Once the Datastream is created, click Add Service.

In the Add Service step, select Adobe Experience Platform from the dropdown and enter the following:

• Event Dataset: WKND-RDE-Behavioral-Targeting
• Profile Dataset: WKND-RDE-Behavioral-Targeting
• Offer Decisioning: Enable
• Edge Segmentation: Enable
• Personalization Destinations: Enable

Click Save to add the service.

In the Add Service step, select Adobe Target from the dropdown and enter the Target Environment ID. You can find the Target Environment ID in Adobe Target under Administration > Environments. Click Save to add the service.

In Adobe Experience Platform, click Tags from the left navigation and click the New Property button.

In the Create Property dialog, enter the following:

• Property Name: WKND-RDE-Behavioral-Targeting
• Property Type: Select Web
• Domain: The domain where you deploy the property (for example, .adobeaemcloud.com)

Click Save to create the property.

Open the new property, and click Extensions from the left navigation, and click the Catalog tab. Search for Web SDK and click the Install button.

In the Install Extension dialog, select the Datastream you created earlier and click Save.

Click Data Elements from the left navigation and click the Create New Data Element button.

In the Create New Data Element dialog, enter the following:

• Name: Host Name

• Extension: Select Core

• Data Element Type: Select Custom Code

• Open Editor button and enter the following code snippet:

  code language-javascript
  if(window && window.location && window.location.hostname) { return window.location.hostname; }

Likewise, create the following data elements:

• Name: Site Section

• Extension: Select Core

• Data Element Type: Select Custom Code

• Open Editor button and enter the following code snippet:

  code language-javascript

  if(event && event.component && event.component.hasOwnProperty('repo:path')) { let pagePath = event.component['repo:path']; let siteSection = ''; //Check for html String in URL. if (pagePath.indexOf('.html') > -1) { siteSection = pagePath.substring(0, pagePath.lastIndexOf('.html')); //replace slash with colon siteSection = siteSection.replaceAll('/', ':'); //remove `:content` siteSection = siteSection.replaceAll(':content:',''); } return siteSection }

• Name: Page Name

• Extension: Select Core

• Data Element Type: Select Custom Code

• Open Editor button and enter the following code snippet:

  code language-javascript
  if(event && event.component && event.component.hasOwnProperty('dc:title')) { // return value of 'dc:title' from the data layer Page object, which is propagated via 'cmp:show' event return event.component['dc:title']; }

Next, create a data element of Variable type. This data element is populated with the page details before sending it to the Experience Platform.

• Name: XDM-Variable Pageview
• Extension: Select Adobe Experience Platform Web SDK
• Data Element Type: Select Variable

In the right panel,

• Sandbox: Select your sandbox
• Schema: Select the WKND-RDE-Behavioral-Targeting schema

Click Save to create the data element.

In your Data Elements list, you should have four data elements:

Click Rules from the left navigation and click the Create New Rule button.

In the Create New Rule dialog, enter the following:

• Name: all pages - on load

• For the Events section, click Add to open the Event Configuration wizard.

  • Extension: Select Core

  • Event Type: Select Custom Code

  • Open Editor button and enter the following code snippet:

    code language-javascript

    var pageShownEventHandler = function(evt) { // defensive coding to avoid a null pointer exception if(evt.hasOwnProperty("eventInfo") && evt.eventInfo.hasOwnProperty("path")) { //trigger Launch Rule and pass event console.debug("cmp:show event: " + evt.eventInfo.path); var event = { //include the path of the component that triggered the event path: evt.eventInfo.path, //get the state of the component that triggered the event component: window.adobeDataLayer.getState(evt.eventInfo.path) }; //Trigger the Launch Rule, passing in the new 'event' object // the 'event' obj can now be referenced by the reserved name 'event' by other Launch data elements // i.e 'event.component['someKey']' trigger(event); } } //set the namespace to avoid a potential race condition window.adobeDataLayer = window.adobeDataLayer || []; //push the event listener for cmp:show into the data layer window.adobeDataLayer.push(function (dl) { //add event listener for 'cmp:show' and callback to the 'pageShownEventHandler' function dl.addEventListener("cmp:show", pageShownEventHandler); });

• For the Conditions section, click Add to open the Condition Configuration wizard.

  • Logic Type: Select Regular

  • Extension: Select Core

  • Condition Type: Select Custom Code

  • Open Editor button and enter the following code snippet:

    code language-javascript
    if(event && event.component && event.component.hasOwnProperty('@type') && event.component.hasOwnProperty('xdm:template')) { console.log('The cmp:show event is from PAGE HANDLE IT'); return true; }else{ console.log('The cmp:show event is NOT from PAGE IGNORE IT'); return false; }

• For the Actions section, click Add to open the Action Configuration wizard.

  • Extension: Select Adobe Experience Platform Web SDK

  • Action Type: Select Update variable

  • Map the web > webPageDetails > name to the Page Name data element

    

  • Likewise, map the server to the Host Name data element and siteSection to the Site Section data element. For pageView > value enter 1, to indicate a page view event.

  • Click Keep Changes to save the action configuration.

• Again, click Add to add another action and open the Action Configuration wizard.

  • Extension: Select Adobe Experience Platform Web SDK
  • Action Type: Select Send event
  • In the right panel’s Data section, map the XDM-Variable Pageview data element to the Web Webpagedetails Page Views type.

  

  • Also, in the right panel’s Personalization section, check the Render visual personalization decisions option. Then, click Keep Changes to save the action.

  

• Click Keep Changes to save the rule.

Your rule should look like this:

Click Publishing Flow from the left navigation and click the Add Library button.

In the Add Library dialog, enter the following:

• Name: 1.0
• Environment: Select Development
• Click Add All Changed Resources to select all the resources.

Click Save & Build to Development to create the library.

Once the library is built for the Development swim lane, click the ellipses (three dots) and select the Approve & Publish to Production option.

In Adobe Experience Platform, click Profiles from the left navigation and click the Merge Policies tab.

You can use an existing merge policy, but for this tutorial, a new merge policy is created with the following configuration:

Make sure to enable both Default merge policy and Active-On-Edge Merge Policy options. These settings ensure that your behavioral data is properly unified and available for real-time audience evaluation.

In Adobe Experience Platform, click Destinations from the left navigation and click the Catalog tab and filter by Personalization and select (v2) Adobe Target destination.

In the Activate Destinations step, provide a name for the destination and click the Connect to destination button.

In the Destination details section, enter the following:

• Name: WKND-RDE-Behavioral-Targeting-Destination
• Description: Destination for behavioral targeting audiences
• Datastream: Select the Datastream that you created earlier
• Workspace: Select your Adobe Target workspace

Click Next and complete the destination configuration.

In Adobe Experience Platform, click Audiences from the left navigation and click the Create Audience button.

In the Create Audience dialog, select the Build-rule option and click the Create button.

In the Create step, enter the following:

• Name: Family Travelers
• Description: Users who have visited family-friendly adventure pages
• Evaluation method: Select Edge (for real-time audience evaluation)

Then, click the Events tab and navigate to the Web > Web Page Details and drag and drop the URL field to the Event Rules section. Drag the URL field two more times to the Event Rules section. Enter the following values:

• URL: Select contains option and enter riverside-camping-australia
• URL: Select contains option and enter bali-surf-camp
• URL: Select contains option and enter gastronomic-marais-tour

In the Events section, select the Today option. Your audience should look like this:

Review the audience and click the Activate to destination button.

In the Activate to destination dialog, select the Adobe Target destination you created earlier and follow the steps to activate the audience.

There is no data in AEP yet, so the audience count is 0. Once users start visiting the website, data is collected and the audience count increases.

Login to Adobe Experience Cloud and navigate to Experience Manager from the App Switcher or Quick Access section.

Navigate to your AEM Author environment and click the Sites button.

In AEM, click Experience Fragments

Navigate to the WKND Site Fragments folder, then navigate to the Featured subfolder and click the Create button.

In the Create Experience Fragment dialog, select Web Variation Template and click Next.

Author the newly created Experience Fragment by adding a Teaser component and customize it with content relevant to family travelers. Add a compelling headline, description, and call-to-action that appeals to families interested in adventure travel.

Select the authored Experience Fragment and click the Export to Adobe Target button.

Login to Adobe Experience Cloud and navigate to Adobe Target from the App Switcher or Quick Access section.

In Adobe Target, click Audiences and verify that the Family Travelers audience is created.

By clicking on the audience, you can see the audience details and verify it’s properly configured.

Next, click Offers and verify that the AEM exported offer exists. In my case, the offer (or Experience Fragment) is called A Taste of Adventure for the Whole Family.

In Adobe Target, click Activities and click the Create Activity button and select Experience Targeting activity type.

In the Create Experience Targeting Activity dialog, select the Web type and Visual composer option, and enter the WKND site home page URL. Click the Create button to create the activity.

In the editor, select the Family Travelers audience and add the A Taste of Adventure for the Whole Family offer before the Next Adventure section. Please see the below screenshot for reference.

Click Next and configure the Goals and Settings section with appropriate goals and metrics, then activate it to push the changes live.

Visit the published site (for example, the WKND Enablement website) and browse either Bali Surf Camp or Riverside Camping or Tahoe Skiing adventure pages. Make sure to spend at least 30 seconds on the page to trigger the page view event and allow the data to be collected.

Then, revisit the home page, and you should see the personalized experience for the Family Travelers audience before the Next Adventure section.

Open your browser’s developer tools and check the Network tab. Filter by interact to find the Web SDK request. The request should show the Web SDK event details.

The response should include the personalization decisions made by Adobe Target, indicating you are in the Family Travelers audience.

Home Page: For Family Travelers audiences, a personalized hero offer is displayed above the Next Adventures section. When a user visits the home page and has visited either Bali Surf Camp or Riverside Camping or Tahoe Skiing adventure pages, the user is categorized as the Family Travelers audience. The audience type is Edge, so evaluation happens in real-time.

Adventure Page: For Surfing enthusiasts, the adventure page is displayed with a personalized hero section. When a user views Bali Surf Camp or Surf Camp In Costa Rica adventure pages, the user is categorized as the Surfing Interest audience. The audience type is Batch, so evaluation is not in real-time but over a period of time like a day. It’s useful for returning visitors.

Magazine Page: For Magazine readers, the magazine page is displayed with a personalized hero section. When a user reads three or more articles, the user is categorized as the Magazine Readers audience. The audience type is Batch, so evaluation is not in real-time but over a period of time like a day. It’s useful for returning visitors.