Online/Offline Web/Mobile Personalization Blueprint

Synchronize web personalization with email and other known and anonymous channel personalization.

Use Cases

  • Landing page optimization
  • Behavioral and offline profile targeting
  • Personalization based on prior product/content views, product/content affinity, environmental attributes, third-party audience data, and demographics in addition to offline insights such as transactions, loyalty and CRM data, and modeled insights

Applications

  • Real-time Customer Data Platform
  • Adobe Target
  • Adobe Audience Manager (optional): Adds third-party audience data, co-op based device graph, the ability to surface Platform segments in Adobe Analytics, and the ability to surface Adobe Analytics segments in Platform
  • Adobe Analytics (optional): Adds the ability to build segments based on historical behavioral data and fine grained segmentation from Adobe Analytics data

Architecture

Reference architecture for the Online/Offline Web Personalization Blueprint

Guardrails

  • Segments shared from Experience Platform to Audience Manager are shared within minutes of segment realization - whether via the streaming or batch evaluation method. There is an initial segment configuration sync between Experience Platform and Audience Manager of approximately 4 hours for the Experience Platform segment memberships to begin to be realized in Audience Manager profiles. Once in the Audience Manager profiles, the Experience Platform segment memberships are available for same page personalization through Adobe Target.
  • Note that for segment realizations that occur within the 4 hour segment configuration sync between Experience Platform and Audience Manager, these segment realizations will be realized into Audience Manager on the subsequent batch segment job as “existing” segments.
  • Batch segment sharing from Experience Platform – once per day or manually initiated via API. Once these segment memberships are realized they are shared to Audience Manager within minutes and available for same/next page personalization in Target.
  • Streaming segmentation is realized within approximately 5 minutes. Once these segment realizations occur they are shared to Audience Manager within minutes and available for same/next page personalization in Target.
  • By default the segment sharing service allows a maximum of 75 audiences to be shared for each Adobe Analytics report suite. If the customer has an Audience Manager license, there is no limit on the number of audiences that can be shared between Adobe Analytics and Adobe Target or Audience Manager and Adobe Target.

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

Reference architecture for the Platform Web SDK or Platform Mobile SDK and Edge Network Approach

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+ Adobe Analytics tracking must use Regional Data Collection (RDC).
Experience Cloud ID service Platform Web SDK* or VisitorAPI.js 2.0+ (Recommended) Use Experience Platform Launch to deploy the ID service to ensure that the ID is set before any application calls
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

  2. Implement Adobe Audience Manager (optional)

  3. Implement Adobe Analytics (optional)

  4. Implement Experience Platform and Real-time Customer Profile

  5. Implement Experience Cloud Identity Service or Experience Platform Web SDK

    NOTE

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

  6. Request provisioning for Audience Sharing between Experience Platform and Adobe Target (Shared Audiences)

On this page

Adobe Summit Banner

A virtual event April 27-28.

Expand your skills and get inspired.

Register for free
Adobe Summit Banner

A virtual event April 27-28.

Expand your skills and get inspired.

Register for free
Adobe Maker Awards Banner

Time to shine!

Apply now for the 2021 Adobe Experience Maker Awards.

Apply now
Adobe Maker Awards Banner

Time to shine!

Apply now for the 2021 Adobe Experience Maker Awards.

Apply now