Mix of at.js and Platform Web SDK implementation
| Solutions | Use Case Enabled |
|---|---|
|
|
|
|
Segment evaluation time
The following table shows the segment evaluation time for events coming from different implementation scenarios:
| Scenario | Edge segment (millisecond evaluation) | Streaming segment (minute evaluation) | Batch segment evaluation |
|---|---|---|---|
| Events/data from Adobe Experience Platform SDKs | Yes | Yes | N/A |
| Events from at.js | No | Yes | N/A |
| Events from Target Mobile SDKs | No | Yes | N/A |
| Events from batch upload | No | No | Yes |
| Events from offline data (stream) | No | Yes | Yes |
Use audiences from Adobe Experience Platform
Using audiences created in Adobe Experience Platform provide richer customer data that leads to more impactful personalization. The Real-Time Customer Data Platform (RTCDP), built on Adobe Experience Platform, helps companies bring together known and anonymous data from multiple enterprise sources. This process lets you create customer profiles that can be used to provide personalized customer experiences across all channels and devices in real time.
By connecting Target to the Real-Time Customer Data Platform, customers can enrich their web personalization. This integration lets you unlock new segments that might have been previously inaccessible to Target to enable real-time millisecond personalization on the first page of a customer’s web visit. Using audiences and profile attributes created in Adobe Experience Platform lets you expand the available data points for richer personalization.
This integration unlocks key use cases with Real-Time CDP:
- Same-page / Next Hit personalization
- First-time / Unknown users personalization
Share Real-Time CDP Profile Attributes with Target
Real-Time CDP Profile Attributes can be shared with Target for use in HTML offers and JSON offers.
Real-Time CDP Profile Attributes feature limitations and considerations
Consider the following:
- Attributes within a given offer must be from the same Experience Platform sandbox. (In other words, an offer cannot contain attributes from different Experience Platform sandboxes.)
- Attributes within a given offer can come from different sources; namely, the Target profile and the Experience Platform profile. (In other words, you can combine attributes whether they come from Target or from the Experience Platform profile.)
- When defining an offer, you can assign default values for Real-Time CDP Profile Attributes, in case the attribute does not have an explicit value. For example, if a consent or governance policy blocks the attribute being used in the personalization service, the default value can be used instead.
- Target supports only the “string” data type for Adobe Experience Platform profile attributes to be used in offers. “Map” and “Array” type attributes are not yet supported.
JSON sample use case
As an online marketer, you want the AEP/Unified Profile to share attribute values with Target to provide real-time personalization. By using Real-Time CDP Profile Attributes, you can display the value of the Experience Platform attribute in a Target offer using token replace. For example, you can personalize according to a customer’s favorite color using ${aep.profile.favoriteColor}, or their loyalty tier and loyalty point value using the tokens ${aep.loyalty.tier} and ${aep.loyalty.points}.
To create a JSON offer to share AEP/Unified Profile attributes with Target:
- While creating a JSON offer, from the Select a source list, select Adobe Experience Platform.
- From the Select a profile sandbox name list, select the desired sandbox.
- From the Select a profile attribute list, select the desired attributes.
- (Optional) From the Insert a default value list, select the desired values.
- Click Add.
The following illustration shows that two profile attributes: loyalty.tier and loyalty.points have been added to the JSON offer.
