Edit in GitHubLog an issue

Audience targeting

Overview#

Audiences can be used to target your experimentation and personalization activities. Adobe Target supports myriad powerful audience targeting capabilities out of the box. The following attributes are available for audience targeting:

Target Library#

For more information, see Target Library. ​

  • Referred from Bing
  • Chrome Browser
  • Firefox Browser
  • Referred from Google
  • Internet Explorer
  • Linux Operating System
  • Mac OS Operating System
  • New Visitors
  • Returning Visitors
  • Safari Browser
  • Tablet Device
  • Windows Operating System
  • Referred from Yahoo

Geo#

For more information, see Geo. ​​

  • Country/Region
  • State
  • City
  • Zip Code
  • Latitude
  • Longitude
  • DMA
  • Mobile Carrier

Network#

For more information, see Network.

  • ISP
  • Domain Name
  • Connection Speed

Mobile#

For more information, see Mobile.

  • Device Marketing Name
  • Device Model
  • Device Vendor
  • Is Mobile Device
  • Is Mobile Phone
  • Is Tablet
  • OS
  • Screen Height (px)
  • Screen Width (px)

Custom#

For more information, see Custom parameters.

  • any key / value pair

Operating system#

For more information, see Operating System.

  • Linux
  • Macintosh
  • Windows

Site pages#

For more information, see Site pages.

  • Current Page
  • Previous Page
  • Landing Page
  • HTTP Header

Browser#

For more information, see Browser.

  • Type
  • Language
  • Version

Visitor Profile#

For more information, see Visitor Profile.

  • any key / value pair, which is persisted

Traffic Sources#

For more information, see Traffic Sources.

  • From Baidu
  • From Bing
  • From Google
  • From Yahoo
  • Referring Landing Page: URL
  • Referring Landing Page: Domain
  • Referring Landing Page: Query

Time Frame#

For more information, see Time Frame.

  • Start Date / End Date

Client Hints#

Adobe Target requires Client Hints for correct segmentation of Browser, Operating System, and Mobile audience attributes, as well as certain instances of Profile Scripts. For more background information, see User Agent and Client Hints.

How to Pass Client Hints to Adobe Target#

Starting with Node.js SDK v2.4.0 and Java SDK v2.3.0, Client Hints can be sent to Target via getOffers() calls. Client Hints should be included on the request.context object, along with User Agent.

Copied to your clipboard
1targetClient.getOffers({
2 request: {
3 context: {
4 channel: "mobile"
5 userAgent: "Mozilla/5.0 (Linux; Android 12; Pixel 4a) AppleWebKit/537.36 (KHTML, like Gecko) Mobile Safari/537.36",
6 clientHints: {
7 mobile: "true",
8 platform: "Linux",
9 platformVersion: "12.1",
10 model: "Pixel 4a",
11 browserUAWithMajorVersion: "\"Not A;Brand\";v=\"98\", \"Chromium\";v=\"98\", \"Google Chrome\";v=\"98\"",
12 browserUAWithFullVersion: "\" Not A;Brand\";v=\"98.0.0.0\", \"Chromium\";v=\"98.0.4844.83\", \"Google Chrome\";v=\"98.0.4758.101\"",
13 bitness: "64",
14 architecture: "x86"
15 }
16 },
17 execute: {
18 mboxes: [{
19 name: "home",
20 index: 1
21 }]
22 }
23 }
24});

On-device decisioning#

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.

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})

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.

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})

Server-side decisioning#

The following table indicates which audience rules are supported or not supported for server-side decisioning.

Audience RuleServer-side Decisioning
GeoYes
NetworkYes
MobileYes
Custom ParametersYes
Operating SystemYes
Site PagesYes
BrowserYes
Visitor ProfileYes
Traffic SourcesYes
Time FrameYes
Experience Cloud Audiences (Audiences from Adobe Audience Manager, Adobe Analytics, and Adobe Experience ManagerYes
Was this helpful?
  • Privacy
  • Terms of Use
  • Do not sell my personal information
  • AdChoices
Copyright © 2022 Adobe. All rights reserved.