"Match Any" in the UX target builder is the equivalent of the Boolean "OR" operator, meaning "if any of the statements are true the target matches". So, if a target is constructed as follows:
Match Any:
Site = ThisSite
Area = sports
- these ad call targets will match:
/site=SomeOtherSite/area=sports
/site=ThisSite/area=chess
/site=ThisSite/area=sports
- while this ad call target will not match:
/site=SomeOtherSite/area=chess
"Match All" in the UX target builder is the equivalent of the Boolean "AND" operator, meaning "all statements must be true for the target to match". So, if a target is constructed as follows:
Match All:
Site = ThisSite
Area = sports
- this ad call targeting will match:
/site=ThisSite/area=sports
- while these ad call targets will not match:
/site=SomeOtherSite/area=sports
/site=ThisSite/area=chess
/site=SomeOtherSite/area=chess
One other item of interest is the usage of the "Not Equal To" and "Not Like" operators in target statements. It's very important that statements using these operators be bound to other statements using "Match All". This is because of the evaluation logic being used. For example, this target:
Match Any:
Site Not Equal To ThisSite
Area = sports
- will match this ad call target:
/site=OtherSite/area=sports
- but surprisingly, this will also match:
/site=ThisSite/area=sports
This is clearly not the behavior intended by the target's creator. This is due to the "Match Any" criteria --- as long as one statement is true ["/area=sports"], the target matches. Setting the target to this:
Match All:
Site Not Equal To ThisSite
Area = sports
assures that the ad call targeting "/site=ThisSite/area=sports" will not match as both target statements must be true and "Site Not Equal To ThisSite" is not a true statement.
Operating System and Release Information
| SAS System | SAS Intelligent Advertising for Publishers | N/A | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.