The process of uploading or downloading data to Amazon Simple Storage Service (S3) can be automated. The Amazon Automated Web Services (AWS) command-line interface (CLI) makes API calls to services over HTTPS. Outbound connections on TCP port 443 must be enabled in order to perform calls. SAS Note 57091 provides detailed information about automating the process using the AWS CLI client, which can be downloaded free of charge. To obtain the credentials required to access your S3 account, contact SAS Technical Support.   ... View more

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.   Some Uses of SETTAG As an alternative to user reg. A publisher can call SETTAG after a visitor logs on and provide whatever tags/values are associated with that visitor. The tags and values thus set persist with the visitor's browser and are sent on every subsequent request. There is no need to store visitor data on the back end (a la user reg). To achieve cookie targeting. A publisher could set tags via SETTAG when a visitor hits certain spots on their site, and then target ads against those values. To set a visitor's latitude and longitude, eliminating need to supply them in every call. To test a live page engaging with certain tags that cannot otherwise be provided. For example, calling SETTAG with GEO_COUNTRY=AUS causes subsequent ad calls to override the GEO_COUNTRY tag that was looked up from the visitor's IP address. (Note that setting GEO_IP using SETTAG does not cause a geo lookup to be done mid-session.) To prevent counting impressions, clicks, and actions resulting from testing by SAS or a publisher. This is done by providing the NOLOG tag in the SETTAG call.   Syntax for SETTAG http://whatever.aimatch.com/customer/SETTAG/NAME=cookieName/TTL=secondsToLive/TAGS=urlEncodedTags Where: cookieName is the name to give this set of tags. A cookie with this name, prefixed by "VT_" is set on the visitor. If absent, this directive is ignored. secondsToLive is the time-to-live for this cookie, in seconds. For example, TTL=86400 sets the cookie to expire in one day. If absent, the cookie is set to expire at the same time as the visitor's guid/mid (one year by default). urlEncodedTags is the set of tags and values to persist in this cookie. These must be URL-encoded and in pathinfo format; that is, using encoded forward slashes to separate tags. If absent, this cookie is deleted. Use %3D for "=" and %2F for "/".   Examples 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%3D-43.21 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%2Fnettag3%3D2935 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.   Multiple Values for a Single SETTAG SETTAG supports multiple tag values for a single tag in the SETTAG. For example: http://whatever.aimatch.com/customer/settag/name=multi/TAGS=sports%3Dhockey,football creates a cookie 'VT_MULTI=hockey,football'.The visitor would be assigned the tag/values of 'sports=hockey,football'.   SETTAG Append Values for a tag can be appended in a single cookie using the following sequence: /settag/tags=geo_country=usa /settag/append=1/tags=geo_country=gbr 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.   SETTAG persist 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. ... View more

With each ad request, the Engine synthesizes additional targeting tags providing basic information about characteristics of the device making the ad request. Currently, the lookup is only effective for mobile devices. Traditional computing devices, such as desktops and laptops, are only minimally supported. The lookup of the device tag values is done once at the start of a visitor session. The looked up values are applied to all ad requests received for the balance of that session. The lookup of device tags is based on an inspection of the user agent string. Therefore, this lookup is best suited to mobile web browsing, where the user agent is set appropriately by the browser. Apps that make direct ad calls (i.e. that do not go through browser-based widgets) can either provide a suitable user agent in the request header, or can simply supply the tag values directly in the ad call. Not all tags are necessarily populated by each lookup. For some devices, some tag values may be unknown. In those cases, the Engine treats the tag as having no value (= ""). Like geo tags, these device tags and their values are predefined and are present for all customers. In the UI, device tags appear alongside custom tags and geo tags wherever those tags are selectable. On the Flights screen, the "Tags" section has a separate subsection for "Device tags", just as it does for "Geo tags".   The supported tags and their values are detailed in Usage Note 53895: Device Detection.   To enable this feature please contact SAS Technical Support.       ... View more

The flight contains the detailed instructions, such as targeting options, and creative that a campaign should deliver. A campaign must contain at least one flight but it may contain many depending on the Advertiser's instructions. Flights can only serve within the date ranges applied at the Campaign. (As with the campaign screens only some of the sections are required). The easiest way to add a flight is to navigate to the campaign details page. On the top navigation bar select Traffic and then from the All Campaigns screen click on the Campaign Name you wish to add this flight to. At the bottom of the campaign details page you will see the Flights section. Click on Add New Flight. You are taken to the flight entry page with the Campaign Name and Advertiser clearly shown at the top of the screen.   For a complete description of how to add a flight to a campain, refer to Usage Note 53894: Creating Flights in a Campaign or the User's Guide.   ... View more

  Standard Action Tracking   Standard action tracking enables you to associate actions with a creative for the advertiser who owns the creative. The creative can be recently seen or clicked by a web site visitor. This feature is useful for monetizing behaviors such as leading a web site visitor from an advertisement to a landing page where a transaction (such as a product purchase) subsequently occurs. Note: The action-tracking URL needs to be placed on the action success page (the landing or results page) so that when the page is reached by the visitor, the URL can notify SAS Intelligent Advertising for Publishers to count it.   FCID Tracking   The syntax for an action-tracking URL associated with a viewed or clicked creative is as follows: http://{adserver domain}/{custid}/count/act=3/fcid={FCID} where {FCID} is replaced with the creative's FCID value. The code /act=3 tells SAS Intelligent Advertising for Publishers that this is a standard action-tracking, counting URL. The FCID value can be found in the user interface next to the name of the creative at the bottom of the Edit Flight page.   ADVID Tracking   The syntax for an action-tracking URL associated with an advertiser whose creative has been seen or clicked is: http://{adserver domain}/{custid}/count/act=3/advid={ADVID} where {ADVID} is replaced with the advertiser's ADVID value. The ADVID value can be found in the URL of the Edit Advertiser page. Site and area values are not needed in the action-tracking URL because they are captured at the time of the impression or click that preceded the action. For the default action (act=3), the ad server automatically tracks impressions and clicks for any flight that has a CPA set to a value > 0.00. Flights without a CPA or with CPA=0.0 are not tracked. With the action-tracking URLvisitor's history of tracked flights for advertiser 50 is examined. The flight creative with the most recent click or impression is credited with the action. If a flight has multiple creatives with recent clicks or impressions, the one with the most recent click is credited. Clicks that are older than 15 days are ignored. Impressions older than one day are ignored. If there are no flights with a qualifying click or impression, then the action is ignored. The 15-day window for clicks and one-day window for impressions are configurable per customer and extend to all flights. Standard action counts are available in BI reports and operational reports. The Custom Action report shows custom action activity. It does not show standard action-tracking counts. Example: http://crtl.aimatch.com/customer/count/act=3/advid=12 This URL searches the visitor's history for a flight associated with advertiser 12 that has the most recent click or impression. The value act=3 is assumed if any of the other action-related tags are present (advid, actid, or actname). The value act=1 continues to be for impression beacon counts and the value act=2 is for click counts.   Custom Action Tracking   Custom action tracking enables you to create and track custom actions (for example, tracking whether a web site visitor has viewed 50% of a video). Note that custom action tracking requires completion of the Action Policies section of the Edit Flight page (shown below), whereas standard action tracking does not. Standard action tracking simply requires a value entered in the Cost Per Action field in the Goals and Revenue section of the Edit Flight page. Impressions are tracked for each flight with an action policy that covers impressions or clicks. Flights without an action policy are not tracked unless the action-tracking URL contains a valid FCID value, in which case the custom action is logged even without a Custom Action Policy enabled for the flight. The active period for impressions or clicks are controlled by the action policy that is set for each action on the flight.  Each action has its own policy that governs impressions and clicks per flight. An action is triggered by a COUNT directive that references an advertiser and a custom action. The custom action is referenced by ID or name. The flight creative that has the most recent active tracked impression or click is credited. If the flight has both a click and an impression, the more recent of the two determines which is credited unless the policy has the Click trumps impressions option set, in which case the click is credited regardless of which is more recent. Counts for custom actions are logged by date, FCID, action ID, attribution type, site, and area. Attribution type is either 0 (for impression) or 1 (for click). Site and area are logged as the original site and area that were associated with the credited impression or click when it occurred. Counts for custom actions are currently not displayed in the Conversions columns when you are viewing flights. The revenue associated with custom actions (set in each policy) is not considered by the engine in daily revenue cap decisions. Changes to Custom Action policies are not displayed when you click the View History button for a flight. Custom action counts are available only in the Custom Action report. They are not available in BI reports. Custom Actions must be associated with the advertiser in order for the Custom Action to appear in the Action Policies dropdown menu in the Edit Flight screen. Custom Actions can be assigned to an advertiser at Customers -> Advertisers -> {advertiser name}. Examples: The custom action URL can use either the custom action's actid value or its name (actname). If both actid and actname are present, then the actname is ignored. To find the actid value for a custom action, edit the custom action and check the URL for the Edit Action page. http://crtl.aimatch.com/customer/count/advid=12/actid=4 This URL searches the visitor's history for a flight associated with advertiser 12 that has the most recent click or impression. Only flights that have policies for the action with the actid=4 tag are considered. The act=3 tag is not required.    http://crtl.aimatch.com/customer/count/advid=13/actname=videostart This URL searches the visitor's history for a flight associated with advertiser 13 that has the most recent click or impression. Only flights that have policies for the action with the name "Videostart" are considered. Note that there are some pre-defined actions available in the user interface. You can create additional custom actions in the Custom Actions tab under the Traffic tab. Actions can  be assigned or removed for each advertiser in the Customers -> Advertisers page.   Read Usage Note 53240: Action Tracking (Standard and Custom) to check for any updates to the info above. ... View more

SAS ® Intelligent Advertising for Publishers compares a visitor's IP address with geographic data that corresponds to the IP address. Geographic data enables targets to be built using the data elements shown in the table below. Targeting Item Targeting Tag Corresponding Ad Call Tag City City geo_city Metro code (US, Great Britain, and France only) Metro code geo_metro_code Country Country geo_country Region (state or province) Region geo_region IP address IP Address geo_ip Postal code (ZIP code) ZIP code text geo_zip_code_text Connection speed Conn speed geo_conn_speed Radial Distance in Miles Geo Distance Miles latitude, longitude Radial Distance in Kilometers Geo Distance Kilometers latitude, longitude   Geographic data is provided by Digital Element, a third-party data provider. The geographic data lookup is performed at the initiation of a visitor's ad-serving session. SAS Intelligent Advertising for Publishers updates the geotargeting data that it receives from Digital Element on a weekly basis. See the Digital Element website for information about Digital Element's technology and accuracy.   Build the Geotarget To build a geotarget, follow these steps: Click the Targeting tab on the main page and then click the Targets tab. Update an existing target or add a new one.   3.  Find cities, countries, regions, metro codes, and ZIP codes by using the search in the Targets tab. Tip: Enter a percent sign (%) to see a list of all possible entries. 4.  To specify coordinates for longitude and latitude, select the Geo Distance target. Enter the coordinates directly, or click the icon beside the right value and use the selector to outline the desired area. The numeric codes for country, metro, and region codes are not translated into text values. To access the codes and their corresponding values, see the following topics: SAS Note 53309 provides a link to a downloadable CSV file that maps country code values to the codes used in the Target tab. SAS Note 53339 provides a link to a downloadable CSV file that maps metro code values to the codes used in the Target tab. UK metro codes are based on ITV regions. (ITV is a commercial public service television network in Great Britain.) SAS Note 53305 provides a link to a downloadable CSV file that maps region code values to the codes used in the Target tab. Note: ZIP codes can be targeted, but counts are not logged against them by default. Logging can be turned on by request. See SAS Note 53321 for information about geotargeting using data that is not tied to the visitor's IP address (for example, targeting to a visitor's search request to find a hotel in another city).   See SAS Note 53362 for information about targeting by connection speed. ... View more