Behavioral Web and mobile personalization blueprint

Last update: March 20, 2024

CREATED FOR:

  • Developer
  • User

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

Applications

  • Adobe Target
  • Adobe Analytics (optional)
  • Adobe Audience Manager (optional)
  • Adobe Real-time Customer Data Platform (optional)

Architecture

Reference architecture for the Behavioral Web Personalization Blueprint

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. Refer to the Experience Platform Web and Mobile SDK Blueprint
  2. Using traditional application-specific SDKs (for example, AppMeasurement.js). Refer to the application specific SDK Blueprint

Implementation steps

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

Implementation steps - Audience Manager or Adobe Analytics

  1. Implement Adobe Audience Manager

  2. Implement Adobe Analytics

  3. Implement Experience Cloud Identity Service

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

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

  5. 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)

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

Implementation steps - Real-time Customer Data Platform

  1. Create schemas for data to be ingested.
  2. Create datasets for data to be ingested.
  3. Configure the correct identities and identity namespaces on the schema to be sure that ingested data can stitch into a unified profile.
  4. Enable the schemas and datasets for profile.
  5. Ingest data into Experience Platform.
  6. Provision Real-time Customer Data Platform segment sharing between Experience Platform and Audience Manager for audiences defined in Experience Platform to be shared to Audience Manager.
  7. Create segments in Experience Platform. The system automatically determines whether the segment is evaluated as batch or streaming.
  8. Configure destinations for sharing of profile attributes and audience memberships to desired destinations.
Previous pageOverview
Next pageKnown customer personalization - Target & RTCDP

Target