The SETTAG directive is used to set one or more cookies holding supplemental targeting tags. Once set, these cookies provide additional key/value pairs with every subsequent ad request, click, or action. Each cookie can be set to expire after an arbitrary time.
Where:
http://whatever.aimatch.com/customer/SETTAG/NAME=blythe/TTL=3600/TAGS=geo_country%3Dfra
sets a cookie named VT_BLYTHE that expresses GEO_COUNTRY=FRA. All ad requests, and so on, for the next hour override the visitor's natural GEO_COUNTRY lookup and instead provide FRA as that tag's value.
http://whatever.aimatch.com/customer/settag/name=location/ttl=900/tags=latitude%3D89.9%2Flongitude%3...
sets a cookie named VT_LOCATION that supplies the visitor's latitude or longitude in all requests for the next 15 minutes.
http://whatever.aimatch.com/customer/SETTAG/NAME=nolog/TAGS=nolog
sets a cookie named VT_NOLOG that blocks counting all ad requests, and so on, for the next year.
http://whatever.aimatch.com/customer/settag/name=somenetwork/TAGS=nettag1%3D342%2Fnettag3%3D2321%2Fn...
sets a cookie named VT_SOMENETWORK that expresses three tags, NETTAG1, NETTAG2, and NETTAG3. In this example, these might be tags that are not needed by the Engine for targeting, but could be used as generic tokens (for example, %%NETTAG1%%) in a template making an ad call to a network.
http://whatever.aimatch.com/customer/SETTAG/NAME=blythe
clears the VT_BLYTHE cookie.
Multiple cookies can be set for a visitor by calling SETTAG multiple times, each time with a different cookie name. The combined contents of all such cookies are sent to the Engine as supplemental tags in the request. These tags override any tags held with the visitor within the Engine--that is, those produced from geo lookups, device lookups, and user reg. But tags that are explicitly sent in with an ad request override tags provided in these cookies.
If more than one cookie expresses the same tag, it is undefined which one takes precedence.
A tag=value pair included in an ad request URL's pathinfo string which matches the SETTAG name but has a different value will override the SETTAG value.
SETTAG supports multiple tag values for a single tag in the SETTAG. For example:
creates a cookie 'VT_MULTI=hockey,football'.The visitor would be assigned the tag/values of 'sports=hockey,football'.
Values for a tag can be appended in a single cookie using the following sequence:
The visitor would first be assigned the tag/value of geo_country=usa, and then the following request with APPEND=1 specified would assign the visitor the tag/values of geo_country=usa,gbr. The APPEND option can be used in conjunction with the TTL option detailed above.
If the SETTAG request uses the "/name={cookieName}" directive, the visitor's values are stored with the cookie. Otherwise, the values are stored in the visitor's session and discarded after the session.
If not using "/name={cookieName}", adding "/persist=1" to the SETTAG request saves the values beyond the visitor's session. The values' lifespan is determined by the "/ttl={X seconds}" directive in the SETTAG request.
Read Usage Note 53759: The SETTAG Directive to check for any updates to the info above.
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!
Data Literacy is for all, even absolute beginners. Jump on board with this free e-learning and boost your career prospects.