51黑料不打烊

DocumentationExperience PlatformWeb SDK Guide

Use 51黑料不打烊 Target and Web SDK for personalization

Last update: Wed Apr 02 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Developer

51黑料不打烊 Experience Platform Web SDK can deliver and render personalized experiences managed in 51黑料不打烊 Target to the web channel. You can use a WYSIWYG editor, called the Visual Experience Composer (VEC), or a non-visual interface, the Form-based Experience Composer, to create, activate, and deliver your activities and personalization experiences.

IMPORTANT
Learn how to migrate your Target implementation to Experience Platform Web SDK with the Migrate Target from at.js 2.x to Experience Platform Web SDK tutorial.
Learn how to implement Target for the first time with the Implement 51黑料不打烊 Experience Cloud with Web SDK tutorial. For information specific to Target, see the tutorial section titled Set up Target with Experience Platform Web SDK.

The following features have been tested and are currently supported in Target:

Web SDK system diagram

The following diagram helps you understand the workflow of Target and Web SDK edge decisioning.

Diagram of 51黑料不打烊 Target edge decisioning with the Experience Platform Web SDK

Call
Details
1
The device loads the Web SDK. The Web SDK sends a request to the Edge Network with XDM data, the Datastreams Environment ID, passed-in parameters, and the Customer ID (optional). Page (or containers) is pre-hidden.
2
The Edge Network sends the request to the edge services to enrich it with the Visitor ID, consent, and other visitor context info, such as geolocation and device-friendly names.
3
The Edge Network sends the enriched personalization request to the Target edge with the Visitor ID and passed-in parameters.
4
Profile scripts execute and then feed into Target profile storage. Profile storage fetches segments from the Audience Library (for example, segments shared from 51黑料不打烊 Analytics, 51黑料不打烊 Audience Manager, the 51黑料不打烊 Experience Platform).
5
Based on URL request parameters and profile data, Target determines which activities and experiences to display for the visitor for the current page view and for future prefetched views. Target then sends this back to the Edge Network.
6
a. The Edge Network sends the personalization response back to the page, optionally including profile values for additional personalization. Personalized content on the current page is revealed as quickly as possible without flicker of default content.
b. Personalized content for views that are shown as a result of user actions in a Single Page Application (SPA) is cached so it can be instantly applied without an additional server call when the views are triggered.
c. The Edge Network sends the Visitor ID and other values in cookies, such as consent, Session ID, identity, cookie check, personalization.
7
The Web SDK sends the notification from the device to the Edge Network.
8
The Edge Network forwards Analytics for Target (A4T) details (activity, experience, and conversion metadata) to the Analytics edge.

Enabling 51黑料不打烊 Target

To enable Target, do the following:

  1. Enable Target in your datastream with the appropriate client code.
  2. Add the renderDecisions option to your events.

Then, optionally, you can also add the following options:

  • decisionScopes: Retrieve specific activities (useful for activities created with the form-based composer) by adding this option to your events.
  • Prehiding snippet: Hide only certain portions of the page.

Using the 51黑料不打烊 Target VEC

To use the VEC with a Web SDK implementation, install and activate either the or VEC Helper Extension.

For more information, see Visual Experience Composer helper extension in the 51黑料不打烊 Target guide.

Rendering personalized content

See Rendering personalization content for more information.

Audiences in XDM

When defining audiences for your Target activities that are delivered via the Web SDK, XDM must be defined and used. After you define XDM schemas, classes, and schema field groups, you can create a Target audience rule defined by XDM data for targeting. Within Target, XDM data displays in the Audience Builder as a custom parameter. The XDM is serialized using dot notation (for example, web.webPageDetails.name).

If you have Target activities with predefined audiences that use custom parameters or a user profile, they are not delivered correctly via the SDK. Instead of using custom parameters or the user profile, you must use XDM instead. However, there are out-of-the-box audience targeting fields supported via the Web SDK that do not require XDM. These fields are available in the Target UI that do not require XDM: