Read Usage Note 50483: Enabling debug logging in SAS® Customer Intelligence 6.1 General Availability (GA) and 6.1_M1 to find out the five steps to change logging output locations and levels.   Before you begin the steps, note the following:   With SAS Customer Intelligence 6.1 GA, the XML files are incorrect. You should follow the instructions in this SAS note and download the correct XML files that are included in this note. With a new SAS Customer Intelligence 6.1_M1 installation, the XML files are set to DEBUGas a standard and all the missing tags are included. When you upgrade from SAS Customer Intelligence 6.1 GA to 6.1_M1, the correct XML files do not overwrite the incorrect files. You need to use the files that are included in this SAS note. In both SAS Customer Intelligence 6.1 GA and 6.1_M1, changing the logging level in the Environment Variables dialog box as described in "Chapter 16 – Troubleshooting" of the SAS Marketing Automation 6.1 and SAS Real-Time Decision Manager 6.1 Administrator’s Guide does not work correctly. It does not matter which environment variables you choose (for example, Off, Medium, or High), the XML files do not change.   This is described in SAS Note 53444, "Changing the logging options in the Environment Variables dialog box in SAS®Customer Intelligence Studio does not work as expected."   By default in release 6.1_M1, the value for the logging levels in the XML files is set to DEBUG. If you want to modify the logging level, you need to edit the XML files and change value for the logging level to INFO.     ... View more

When you migrate from an earlier release of SAS Customer Intelligence, you must run the SAS Customer Intelligence migration utility with the -useraction ContentCheckcommand – and you get the following error:   SAS Marketing Automation version 5.4: ERROR 2015-04-20 13:27:03: ERROR:Exception: null ERROR 2015-04-20 13:27:03: ERROR:java.lang.IllegalStateException      at com.sas.analytics.crm.util.client.ContentCheck.createSessionForPath(ContentCheck.java:1515)      at com.sas.analytics.crm.util.client.ContentCheck.getBCForPath(ContentCheck.java:1335)      at com.sas.analytics.crm.util.client.ContentCheck.getBCNameForPath(ContentCheck.java:1366)      at com.sas.analytics.crm.util.client.ContentCheck.execute(ContentCheck.java:313)      at com.sas.analytics.crm.util.client.Utilities.(Utilities.java:165)      at com.sas.analytics.crm.util.client.Utilities.main(Utilities.java:84) SAS Marketing Automation version 5.41: ERROR 2014-02-06 14:05:38: ERROR:The requested object no longer exists. ERROR 2014-02-06 14:05:38: ERROR:com.sas.analytics.crm.error.client.UserException at com.sas.analytics.crm.flow.ejb.FlowBean.getFlowStateID(FlowBean.java:3933) at com.sas.analytics.crm.flow.ejb.FlowBean.createAndAddFlowState(FlowBean.java:4074) at com.sas.analytics.crm.flow.ejb.FlowBean.initCampaign(FlowBean.java:425) at com.sas.analytics.crm.flow.ejb.FlowBean.initCampaign(FlowBean.java:353) at sun.reflect.GeneratedMethodAccessor1425.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597)   To resolve this problem:   Add the DEBUG option to the command line, as shown below:   sasciutils_console -userid sasadm@saspw -password [pass] -useraction ContentCheck -metaserver [metaserver] -metaport 8561 –debug This command generates the following output: <Server>    <TransformationActivity Id="A588LTJ7.C50000DN" IsActive="1" IsUserDefined="0" MetadataCreated="19Nov2014:07:44:16" MetadataUpdated="19Nov2014:07:44:16"                            Name="campaign-name" PublicType="CICampaign" TransformRole="CICampaign" UsageVersion="1000000"> </Server>   In this output, campaign-name specifies the name of your campaign.   Verify that your campaign still exists in SAS Customer Intelligence Studio and in the folder structure of SAS Management Console. If you cannot find the campaign, use the METABROWSE procedure to delete the orphaned campaign. Read Usage Note 55668: A failure occurs when you run the SAS Customer Intelligence migration utility with the "-useraction ContentCheck" command to see operating system and release information and to check to updates to this info.   ... View more

SAS Marketing Automation campaigns might fail to execute and return the error below:       Error in the stored process or called macro - Vendor Code: 1012, Message:     There was an error in the stored process or called macro. Check the log for details   This error occurs when a process node follows a communication node and the process node references a pre-defined library. When this situation occurs, the stored process server and macore logs also contain the following error:   ERROR: Libname xxxxxx is not assigned. Post-process nodes are usually included after communications to perform specific updates after the communication completes successfully. In the example below, the process moves data from a database table into a .lst file:   data _null_; set explib.testtable; file "c:\temp\excn122.lst"; put _ALL_; run; The libref EXPLIB is created as a pre-defined library in SAS ®  Management Console. In order to ensure that the library is still in scope for the process node, add the following macros to your process node code: %mausrexp(explib,Execute); - before the library is referenced %mausrexp(explib,Clear); - after the library is referenced %mausrexp(explib,Execute);   data _null_; set explib.excn122; file "c:\testing\w32\excn122.lst"; put _ALL_; run; %mausrexp(explib,Clear); Check back for updates to the above info by reading Usage Note 37561: SAS® Marketing Automation might return "Error in the stored process or called macro.." when a process node follows a communication node.   ... View more

There are the items that are needed when starting this installation:   The application download URL. This can be provided by Support. The Enterprise version of Saleforce and administrator privileges to install this application. Create an account in your SAS Intelligent Advertising for Publishers instance that has Administrator Role permissions. This will be the account used to interface with the SAS Intelligent Advertising for Publishers instance from Salesforce. Retrieve the API key for the account to be used to interact with the SAS Intelligent Advertising for Publishers instance. This can be found in your SAS Intelligent Advertising for Publishers instance by navigating to Admin->Users->The user account. Once on this page you should see the API key. Retrieve the ID of the default Terms and Conditions to be used when creating a Proposal from Salesforce. This ID can be obtained by navigating to Sales->Terms and Conditions and then the Terms and Conditions entry to be used as the default. The ID will the number at the end of the URL. Here is a video tutorial of setting up the application in Salesforce: Part 1 Part 2 SAS Intelligent Advertising for Publishers Salesforce API Connection Installation URL https://login.salesforce.com/packaging/installPackage.apexp?p0=04tU0000000M59g   Password: spear   Read Usage Note 53741: Salesforce API Connection Installation Requirements to check for any updates to the info above. ... View more

When serving third-party creatives, you often need to log clicks for the first-party ad server (in this case SAS Intelligent Advertising for Publishers) as well as the third party. This requires that the first-party ad server provide a URL to the third party that not only logs a click on their end, but also redirect the visitor to the third party click URL, which then takes the visitor to the destination.   This presents a challenge as there is no accepted industry standard as to how to deal with passing the click URLs between each party. The most common approach is that the third party provides a Javascript variable or a key/value pair in the URL where the first party click URL should be placed.   Read Usage Note 53277: Click tracking with 3rd party creatives to see an example of how this works. You’ll also learn how to implement the click tracking token and test to ensure it works. ... View more

In SAS Intelligent Advertising for Publishers, the prioritization method of the tier allows you to select criteria for the engine to calculate the priority of tier flights. The priority orders the flights in a tier so that the engine evaluates them in the desired order. To view the available prioritization methods, click:   The Traffic tab The tiers tab, then the desired tier On the Prioritization Method dropdown menu In Usage Note 53613: Tier Prioritization Methods, you’ll learn about schedule-based tiers (the most common), click rate prioritization, action rate, CPM rate (cost per thousand), eCPM (effective cost per thousand), weighted, cost per second, share of voice, broad share of voice and broad weighted. ... View more

If you use Brightcove and know how to set up creative formats and creatives in SAS Intelligent Advertising for Publishers, read Usage Note 53702: Serving VAST ads to Brightcove players. To get started, you’ll take three steps to set up the video player and three steps to load the advertising module. You’ll also learn how to set up Key=value pairs, how to use a vast wrapper to serve third-party VAST ads from SASIA/aiMatch, and how to enable support for companion flights and categories. ... View more

Read Usage Note 53728: Multivalue Targeting to find out how to express multiple values 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. You’ll learn how to create correct syntax and also about Ad Debug output, logging, simulation forecasting and BT analysis. ... View more

As a special-purpose web server, the SAS Intelligent Advertiser for Publishers ad server responds to HTTP requests from any browser. It uses path information to determine which creative to serve. The method in this path contains the directive that tells the server how to return the creative, as in the following example:   http://crtl.aimatch.com/{custid}/hserver/site=A/size=728x90 In this case, the directive /hserver/ tells the application to select an ad that is appropriate for delivery to site A and is sized 728 by 90, wrap it in an HTML tag, and return it to the browser as a complete HTML page. There are multiple middle-ware server directives that you can use to develop ad calls that are appropriate for your service model.   Read Usage Note 53291: Creating Ad Requests for the SAS Intelligent Advertising for Publishers Ad Server to learn about ad tag parameters, considerations for developing an ad call and ad call methods and to check for updates to the content above. ... View more

Usage Note 56441: Implementing click tracking for HTML5 creatives shows you how to track clicks for an HTML5 creative in the SAS Intelligent Advertising for Publishers system.   First, edit the creative code before you upload the HTML5 ZIP package through the Smart Upload tool. (For details on that, see SAS Note 56432: Trafficking HTML5 creatives using the SAS ®  Intelligent Advertising for Publishers Smart Upload tool. As with traditional third-party click tracking in Flash, HTML5 creatives vary in the way they handle that clicks. Most third parties use a "clickTag" or "clickTAG" (case sensitive) variable. This allows the system actually serving the HTML5 content to pass in a click URL, ensuring that the click is counted on both the serving and third-party systems.   Because HTML5 creatives are served into IFRAMEs with SAS Intelligent Advertising for Publishers, you need to add a small snippet of code to the HTML5 creative source code so that the clickTag variable is usable. This is typically "index.html" in the ZIP file containing the creative contents. Once you add the code snippet, you can repackage and upload the ZIP through the Smart Upload tool.   In Usage Note 56441: Implementing click tracking for HTML5 creatives, you’ll learn 9 steps to prepare HTML5 creatives for the Smart Upload tool. ... View more

Read Usage Note 53242: Building Targets in SAS Intelligent Advertising for Publishers to find out how to target specific demographic composed of sites, areas, custom tags, geotargeting, keywords, and even web visitors. You’ll also learn how targets can be applied to flights, tiers, products, and creatives. ... View more

Yes, SAS Intelligent Advertising for Publishers supports dynamic tokens for string replacement in creative code content. For example, an ad call can pass in a key=value pair such as "/toys=nerfgun": http://crtl.aimatch.com/customername/hserver/site=toycatalog/size=728x90/toys=nerfgun The creative content can then use the token %%TOYS%% to get the associated value "nerfgun": <a href="%%CLICKURL%%?%%TOYS%%"><img src="%%MEDIA%%" width=728 height=90> - where %%TOYS%% is replaced with "nerfgun" in the querystring of the click URL.  Notes: "toys" does not have to be a targeting tag in the SAS Intelligent Advertising for Publishers system for this feature to work. The dynamic token must have %% in front of and after the string. The dynamic token must be uppercased in the creative code ["%%TOYS%%"]. Appending ":URLENCODED" [for example, "%%DATETIME:URLENCODED%%"] will URL-encode the token value. Similarly, appending ":URLDECODED" will decode a URL-encoded string. Read Usage Note 53300: Using dynamic tokens in SAS Intelligent Advertising for Publishers to check for updates to this information.   ... View more

In SAS Intelligent Advertising for Publishers, actions are sent to the system using the 'count' directive. For example:   http://{SASIA adserver URL}/{customer short name}/{content type}/count/fcid=1234/act=3/inc=1   - increments the action count for fcid 1234 [the unique creative identifier] by 1. act=1 This ad call parameter denotes a beacon count URL. act=2 This ad call parameter denotes a click count URL. When using this instead of the 'adclick' directive the click count is incremented but the browser is not relocated to the click URL destination. act=3 This ad call parameter denotes a generic action count URL. inc=X This ad call parameter increments the count by X When act= is missing, 1 is assumed. When inc= is missing, 1 is assumed. Other targeting tags present in the URL [site or area, for example] will be logged against when the URL is executed. Note that the current version of action tracking is not cookie-based, hence the need for the FCID value to be present in the URL for correct counting.   Check Usage Note 53313: Beacon, Click, and Action Count URLs in SAS Intelligent Advertising for Publishers for updates to this information. ... View more

  SAS Intelligent Advertising for Publishers has a number of pre-defined "tokens" which can be placed in both file-based and URL-based creatives. The data sources which are used to replace the tokens are defined here. The standard format for a token is "%%{token name}%%". Tokens must always be presented in UPPERCASE. Refer to SAS Note 53714 for details on creating custom tokens for use in creative formats.  Refer to SAS Note 53300 for details on using the dynamic ["on-the-fly"] token feature in SAS Intelligent Advertising for Publishers.  Appending ":URLENCODED" [for example, "%%DATETIME:URLENCODED%%"] will URL-encode the token value. Similarly, appending ":URLDECODED" will decode a URL-encoded string.  While there is no practical length on a token's value the total length of the ad request URL's pathinfo, querystring, and HTTP headers cannot exceed 32Kb. Visit Usage Note 53297: Using pre-defined tokens in SAS Intelligent Advertising for Publishers to see a list of tokens and their definitions. ... View more