Usage Note 53728: Multivalue Targeting
 |  |  |  |
/SITE=ALASKA.COM/AREA=NEWS
But now SASIA accepts and can target multiple values, e.g.
/SITE=ALASKA.COM,YUKON.COM/AREA=NEWS,POLITICS,ELECTION
Multiple values can be expressed for most tags used in targeting, including SITE, AREA, all custom tags, geo tags, and GEO_IP. LATITUDE and LONGITUDE cannot have multiple values. SIZE and KEYWORD already accept multiple values.
Syntax
Multiple values must be separated by commas or the URL-encoding for commas (%2d). They cannot be expressed separately in multiple instances of the "tag=" phrase. E.g./SITE=ALASKA.COM/SITE=YUKON.COM/AREA=NEWS/AREA=POLITICS/AREA=ELECTION
is not a valid way to express multiple values and does not yield the same result as the example above. When a tag appears more than once in an ad call, typically all those before the last are ignored.
Targeting
When the Engine evaluates a target rule or tag restriction for a tier, flight, or creative, it considers all values passed in for the tag. For most operations, if any of the tag's values match the rule or restriction, then the rule is considered to match. For example, if a flight has a target of "AREA = POLITICS", then the above ad call matches. If the target is "AREA = SPORTS", it does not match. Pretty straightforward.However, for negative operations ("Not Equals", "Not In", and "Not Like"), all of the tag's values must "not" match. For example, if a flight has a target of "AREA != POLITICS", then the above ad call does not match, because one of the values passed in was POLITICS. If the target is "AREA != SPORTS", it does match, because none of the values passed in was SPORTS.
If a flight has a target of "SITE Not In ( YUKON.COM,CANADA.COM )", then the above ad call does not match, because one of its values is in the target list.
Ad Debug output
The Ad Debug output alphabetically lists the multiple values supplied for the tag. The corresponding tag value ids are shown in parentheses after. A 0 id is shown for any invalid tag value.
Logging
In the default state only a single tag value id is logged for each tag. The value logged is the one with the lowest non-0 id, or 0 if none of the values were valid.Note: Using the feature with the default settings may result in some flights reporting as having appeared against targets for which they were not eligible. This is a reporting limitation and flights would have delivered correctly. Please be aware of this limitation before implementing the feature.
It is possible for SAS Intelligent Advertising for Publishers to log a value that was matched in targeting of the flight/creative that was served. If multiple values were matched in targeting, then the one with the lowest value id is logged. If no values were matched in targeting, then logging occurs as for the default. This feature must be enabled by SAS Client Services - please contact them to discuss the specific requirements as only a limited number of tags can be supported.
Simulation Forecasting
Sampling does record multiple values, and they are all processed and used in targeting during simulation, just as with live ad serving. Invalid tag values are not sampled, and so are not presented to the simulation. As mentioned, logging can only record one value per tag.Prior to the changes made to support multivalue targeting, only one SIZE value would be recorded in sampling even when multiple sizes were present in the ad call. Now all sizes are included in sampling and processed during simulation.
BT analysis
BT analysis considers a tag's multiple values when looking for matches to qualify a visitor for BT traits.Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS Intelligent Advertising for Publishers | N/A | ||
| Type: | Usage Note |
| Priority: |
| Date Modified: | 2015-09-08 10:25:56 |
| Date Created: | 2014-07-23 15:51:44 |