List of frequently asked questions (FAQs) about experience targeting and audiences.
Target evaluates URLs differently depending on whether you use audience URL targeting while creating an activity or whether you use URL targeting while creating an audience.
Consider the following URL:
To apply audience URL targeting, while creating an activity, on the Experiences page (step one of the three-step guided workflow), click the gear icon, click Page Delivery, then specify the desired URL.
Audience URL targeting looks for an exact URL match. If the URL matches, Target does not consider further logic. In the above URL, if the activity is set to fire on
www.example.com, the URL matches for the following URLs because audience URL targeting is query agnostic:
Beyond audience targeting on the URL, you can also specify specific values that can be in the query.
Audience URL targeting and URL targeting added via Template Rules evaluate as URL targeting (see URL targeting below).
To apply URL targeting, while creating an audience, click Add Rule, click Site Pages, select an option from the first drop-down list (Current Page, Previous Page, or Landing Page), select URL from the second drop-down list, specify an evaluator, then specify the desired URL.
URL targeting transforms the URL into a set of rules to evaluate:
If you use the same parameter name more than once in a URL string, HTTP considers the first parameter name and ignores subsequent parameters with the same name.
For example, in the following URL string:
the first instance of the
Category parameter is evaluated and the second
Category parameter is ignored.
Best practice is to have multiple values associated with a single category, as shown below:
The pre-built audiences in the Target Library category are legacy audiences and exist in other categories. As an example, the legacy Target Library > New Visitors audience has an updated counterpart: Visitor Profile > New Visitor.
Best practice is to use the newer audiences because they have improved performance. Some customers might be using legacy, pre-built audiences, so they have not been removed from the Target interface.
By default, traffic is split evenly between experiences. However, you can specify percentage targets for each experience. In this case, a random number is generated and that number is used to choose the experience to display. The resulting percentages might not exactly match the specified targets, but more traffic means that the experiences should be split closer to the target goals.
The user qualifies for the first experience/audience that displays on the activity’s Target page.
For example, in the following illustration, a user from California using a Windows device qualifies for both Experience A (Windows audience) and Experience C (California audience). This user would be shown Experience A because it displays in the list above Experience C on the Targets page.
Audience names in Target are unique; however, in AAM and the Audience Library, you can have the same name for multiple audiences (if they are in different folders).When Target encounters an audience name that corresponds to an AAM or Audience Library audience, Target appends “#<number>” to the name.
For example, you might see the following audiences: “PC Users” (in AAM) and “PC Users #1” (in Target).
Some Target audiences are predefined, such as “New Visitors” and “Returning Visitors.” These predefined audiences cannot be renamed by users.
Target has a limit of 50 unique profile attributes per mbox call. If you need to pass more than 50 profile attributes to Target, you can pass them using the Profile Update API method. For more information, see Profile Update in the Adobe Target API documentation.
Automated Personalization activities are evaluated once per session. If there were active sessions that have qualified for a particular experience and now new offers have been added to it, users will see the new content along with the previously shown offers. Because they have previously qualified for those experiences, they would still see them for the duration of the session. If there’s a desire to evaluate this at every single page visit, you should change to the Experience Targeting (XT) activity type.
Unlike offers and profile scripts, changes made by API to audiences created via Target Standard are not currently synced back to the Target UI.
If the left and the right part of the equals expressions can be parsed to a number, the two parts are compared as numbers, not as strings.
|1.200||is less than 2||true|
|2||is greater than 3.0||false|
Numbers written in scientific notation will always be compared as strings.
“4e-2” will only equal “4e-2”. It will not equal “0.04”.