Pre-built Audience: Use the pre-built audience if you want to target only visitors who use a specific browser to visit your site. For example, if you are offering a Chrome extension, you would target only Chrome users.
When setting up your activity, select the browser from the drop-down list.
This option targets the activity only to visitors who use the specified browser.
Customized Browser Audience Rule: A customized audience lets you target multiple browsers, or to set up rules or exclusions for specific browsers, browser versions, or browser languages. This functionality provides significant flexibility when targeting an activity based on browser attributes.
In the Target interface, click Audiences > Create Audience.
Name the audience and add an optional description.
Drag and drop Browser into the Audience Builder.
Click Select, then select one of the following options:
Type: Target or exclude a certain browser. See Type.
Language: Target or exclude certain browsers that are set to use specific languages. See Language.
Version: Target or exclude certain browser versions. See Version.
(Optional) Set up additional rules for the audience.
Click Done.
The following example shows an audience that includes Microsoft Edge users on versions 91 or 92:
Target or exclude activity entrants based on their browser type, language, or version.
Type section_6ADC758F23F145B3A310151546D83D56
Target or exclude a certain browser.
Select Type, then choose either equals or does not equal.
Equals: Target the selected browsers.
Does not equal: Exclude the selected browsers.
Select one or more browsers. Multiple options are connected with an OR.
Language section_7520D1AA464A45A6843EABE2D2B431A1
Target or exclude certain browsers that are set to use specific languages.
For example, if an offer is available only in English, you might target browsers with their language set to English. Or, if your page is not double-byte enabled, you might exclude browsers set to East Asian languages.
Including or excluding browser language can provide more accurate visitor targeting than targeting based on geography in cases where language is more important than location. For example, if you are offering an article written in English, you could either target English-speaking countries, or you could target browsers that are set to English. Targeting to the browser makes the article available to English speakers in countries where English is not the primary language.
Select Language, then choose either equals or does not equal.
Equals: Target the selected browser languages.
Does not equal: Exclude the selected browser languages.
Select one or more languages. Multiple options are connected with an OR.
The following browser languages can be targeted or excluded:
English
French
German
Japanese
Korean
Portuguese
Russian
Spanish
Traditional Chinese
Version section_37CC8CE45DA04E8682AE6388321BA6EF
Target or exclude certain browser versions.
For example, if your page does not appear correctly in Internet Explorer version 11 or earlier, you can create an audience that excludes those versions. In that case, you would set up a rule where the browser type equals Internet Explorer and add a second rule where the version is less than or equal to 11.
Select Version, then choose an operator:
Equals
Does not equal
Is greater than
Is greater than or equal to
Is less than
Is less than or equal to
Type the version number. Only major versions can be entered in the text field. The specified version includes any minor version of that release. For example, if you specify version 10, visitors on version 10.1 are also included.
Multiple options are connected with an OR.
Training video: Creating Audiences
This video includes information about using audience categories.
Starting April 30, 2024, iPad and iPhone will be removed from the available Browser type drop-down list in the Target UI when creating categories for audiences.
Built-in audiences created using the Target UI, such as “Browser: iPad” and “Browser: iPhone”, will be automatically moved over to the new Audience definition. However, going forward, you should use the settings described below.
If you use user.browserType in any profile scripts to check if it is an iPhone or iPad (for example, user.browserType == 'iphone' or user.browserType != 'ipad'), those profile scripts should be changed as instructed below before April 30, 2024 to ensure that these audiences continue to function as expected.
JavaScript audiences are legacy audiences using Target expressions that were deprecated with the Target Classic UI. These audiences can be modified via API only. Customers must update these audiences only if continuing to use legacy audiences in activities.
Audiences created using the Target UI ui
The following settings could be used going forward:
For browser matches Apple: Mobile > Device Vendor matches Apple
For browser matches tablet: Mobile > is Tablet > true
For browser matches iPad: Mobile > Device Marketing Name matches iPad with an And container with Mobile > Is Tablet is true
For browser matches iPhone: Mobile > Device Marketing Name matches iPhone with an And container with Mobile > Is Mobile Phone is true
There are many other possible settings that could be used, for example when conditions are negated. Examples of negated conditions could look like the following:
For browser does not match iPhone: Mobile > Device Vendor does not match Apple with an Or container with Mobile > Is Mobile Phone is false
For browser does not match iPad: Mobile > Device Vendor does not match Apple with an Or container with Mobile > Is Tablet is false.
Audiences created using profile scripts profile-scripts
If you use user.browserType in legacy Target Classic audiences or in profile scripts, changes should include the following:
NOTE
The following profiles are scheduled to be released in the next few weeks, as of January 24, 2024. The current release notes will be updated when these profiles are available.
These profiles make the following changes possible:
