Edit in GitHubLog an issue

Supported features overview

Adobe Target's server-side SDKs give developers the flexibility to choose between performance and freshness of data for decisions. In other words, if delivering the most relevant and engaging personalized content via machine learning is most important to you, a live server call should be made. But when performance is more critical, an on-device decision should be made. For on-device decisioning to work, please refer to the following list of supported features:

  • Activity Types
  • Audience Targeting
  • Allocation Method

Activity types#

The following table indicates which activity types created using the Form-based Experience Composer are supported or not supported for on-device decisioning.

Activity TypeSupported
A/B TestYes
Auto-AllocateNo
Auto-TargetNo
Analytics for Target (A4T)Yes
Multivariate Test (MVT)No
Experience Targeting (XT)Yes
Automated Personalization (AP)No
RecommendationsNo

Audience targeting#

The following table indicates which audience rules are supported or not supported for on-device decisioning.

Audience RuleOn-device Decisioning
GeoYes
NetworkNo
MobileNo
Custom ParametersYes
Operating SystemYes
Site PagesYes
BrowserYes
Visitor ProfileNo
Traffic SourcesNo
Time FrameYes
Experience Cloud Audiences (Audiences from Adobe Audience Manager, Adobe Analytics, and Adobe Experience ManagerNo

Geo targeting for on-device decisioning#

In order to maintain near-zero latency for on-device decisioning activities with geo-based audiences, Adobe recommends you provide the geo values yourself in the call to getOffers. Do this by setting the Geo object in the Context of the request. This means your server will need a way to determine the location of each end user. For example, your server may perform an IP-to-Geo lookup, using a service you configure. Some hosting providers, such as Google Cloud, provide this functionality via custom headers in each HttpServletRequest.

Node.js

Copied to your clipboard
1const CONFIG = {
2 client: "acmeclient",
3 organizationId: "1234567890@AdobeOrg",
4 decisioningMethod: "on-device"
5};
6
7const targetClient = TargetClient.create(CONFIG);
8
9targetClient.getOffers({
10 request: {
11 context: {
12 geo: {
13 city: "SAN FRANCISCO",
14 countryCode: "US",
15 stateCode: "CA",
16 latitude: 37.75,
17 longitude: -122.4
18 }
19 },
20 execute: {
21 pageLoad: {}
22 }
23 }
24})

Java

Copied to your clipboard
1public class TargetRequestUtils {
2
3 public static Context getContext(HttpServletRequest request) {
4 Context context = new Context()
5 .geo(ipToGeoLookup(request.getRemoteAddr()))
6 .channel(ChannelType.WEB)
7 .timeOffsetInMinutes(330.0)
8 .address(getAddress(request));
9 return context;
10 }
11
12 public static Geo ipToGeoLookup(String ip) {
13 GeoResult geoResult = geoLookupService.lookup(ip);
14 return new Geo()
15 .city(geoResult.getCity())
16 .stateCode(geoResult.getStateCode())
17 .countryCode(geoResult.getCountryCode());
18 }
19
20}

However, if you do not have the ability to perform IP-to-Geo lookups on your server, but you still want to perform on-device decisioning for getOffers requests that contain geo-based audiences, this is also supported. The downside of this approach is that it will use a remote IP-to-Geo lookup, which will add latency to each getOffers call. This latency should be lower than a remote getOffers call, since it hits a CDN that is located close to your server. You must only provide the ipAddress field in the Geo object in the Context of your request, in order for the SDK to retrieve the geo-location of your user's IP address. If any other field in addition to the ipAddress is provided, the Target SDK will not fetch the geo-location metadata for resolution.

Node.js

Copied to your clipboard
1const CONFIG = {
2 client: "acmeclient",
3 organizationId: "1234567890@AdobeOrg",
4 decisioningMethod: "on-device"
5};
6
7const targetClient = TargetClient.create(CONFIG);
8
9targetClient.getOffers({
10 request: {
11 context: {
12 geo: {
13 ipAddress: "127.0.0.1"
14 }
15 },
16 execute: {
17 pageLoad: {}
18 }
19 }
20})

Java

Copied to your clipboard
1public class TargetRequestUtils {
2
3 public static Context getContext(HttpServletRequest request) {
4 Context context = new Context()
5 .geo(new Geo().ipAddress(request.getRemoteAddr()))
6 .channel(ChannelType.WEB)
7 .timeOffsetInMinutes(330.0)
8 .address(getAddress(request));
9 return context;
10 }
11
12}

Allocation method#

The following table indicates which allocation methods are supported or not supported for on-device decisioning.

Allocation MethodSupported
ManualYes
Auto-allocate to best experienceNo
Auto-target for personalized experiencesNo
Was this helpful?
  • Privacy
  • Terms of Use
  • Do not sell my personal information
  • AdChoices
Copyright © 2022 Adobe. All rights reserved.