Behavioral Web/Mobile Personalization Blueprint

Personalize based on online behavior and audience data.

Use Cases

  • Landing page optimization
  • Behavioral targeting
  • Personalization based on prior product/content views, product/content affinity, environmental attributes, third-party audience data, and demographics


  • Adobe Target
  • Adobe Analytics (optional)
  • Adobe Audience Manager (optional)


Reference architecture for the Behavioral Web Personalization Blueprint


By default, the segment sharing service allows a maximum of 75 audiences to be shared for each Adobe Analytics report suite. If Audience Manager is being used for audience sharing, there is no limit on the number of audiences that can be shared.

Implementation Patterns

The Web/Mobile personalization blueprint can be implemented via the following approaches as outlined below.

  1. Using the Platform Web SDK or Platform Mobile SDK and Edge Network.
  2. Using traditional application-specific SDKs (for example, AppMeasurement.js)

1. Platform Web/Mobile SDK and Edge Approach

Refer to the Experience Platform Web and Mobile SDK Blueprint

2. Application-specific SDK Approach

Reference architecture for the Application-specific SDK Approach

Implementation Prerequisites

Application/Service Required Library Notes
Adobe Target Platform Web SDK*, at.js 0.9.1+, or mbox.js 61+ at.js is preferred as mbox.js is no longer being developed.
Adobe Audience Manager (Optional) Platform Web SDK* or dil.js 5.0+
Adobe Analytics (Optional) Platform Web SDK* or AppMeasurement.js 1.6.4+
Experience Cloud Identity Service Platform Web SDK* or VisitorAPI.js 2.0+
Experience Platform Mobile SDK (Optional) 4.11 or higher for iOS and Android™
Experience Platform Web SDK 1.0, current Experience Platform SDK version has various use cases not yet supported for the Experience Cloud applications

Implementation Steps

  1. Implement Adobe Target for your web or mobile applications.

    If using Audience Manager or Adobe Analytics:

  2. Implement Adobe Audience Manager

  3. Implement Adobe Analytics

  4. Implement Experience Cloud Identity Service


    Each application must use the Experience Cloud ID and be part of the same Experience Cloud Org to allow audience sharing between applications.

  5. Request provisioning for the People and Audience Sharing services (Shared Audiences)

  6. Build segments in Adobe Analytics or Adobe Audience Manager and configure those audiences for sharing to the Experience Cloud (if using Audience Manager or Adobe Analytics)

  7. Once the audiences are available in Adobe Target, they can be used for targeting experiences with Adobe Target

On this page