Latest Articles

Marketing & Commerce | October 23, 2018
Campaign Sort Orders
  This is Swati Rajput. I am getting started with my first blog today in which I am writing about various sort orders that a database has and what sort orders are specifically needed by Campaign. ​ If sort order of database is different than what Campaign needs, what parameters, configuration or commands need to be run on database to match those so that data sorting can be avoided on Campaign Server. Instead if appropriate sort orders are set , sorting of data would be carried on database which would be much faster. By default, Campaign Use Binary Sort order. In order to do proper sorting at campaign, set default character set as UTF-8, default character type as Unicode and sort order as Binary. Oracle Sort Orders: Default sorting order in oracle is binary. Execute this command to check various sorting techniques in Oracle: select * from v$nls_valid_values where parameter='SORT'; ​Sort order Sql Server​ More description: DB2 sort order collate_info - Collating Information This parameter determines the database's collating sequence. For a language-aware collation, the first 256 bytes contain the string representation of the collation name (for example, SYSTEM_819_US). This parameter can only be displayed using the db2CfgGet API. It cannot be displayed through the command line processor or the Control Center. You can specify the collating sequence at database creation time. More description: Teradata sort order: The Teradata Database offers five standard collation sequences in which data can be defined as CASESPECIFIC or NOT CASESPECIFIC. This affects how the five collation sequences collate and compare data. The five collations, determined either by default or explicit use of the SET SESSION COLLATION statement, are: •  ASCII •  EBCDIC •  CHARSET_COLL •  JIS_COLL •  MULTINATIONAL CASESPECIFIC or NOT CASESPECIFIC can be chosen at table definition time, or specified...
Marketing & Commerce | October 3, 2018
Interact Coverage Analysis
  Database marketers often want to test their Interactive channel(s) whether they have enough offer coverage for each group of their customer base or for certain groups of segments. ​ NEW FEATURE IN INTERACT  In addition to the Simple and Advanced Scenario simulator features which had already been introduced, a new and very useful simulation capability has been made available in Interact version 11.0.   FUNCTIONALITY  The ‘Simulator Coverage Analysis scenario’ functionality allows marketeers to create reusable scenarios in order to test whether their offers, events, segmentation, strategy and suppression rules will work as expected.   LOCATION  The simulator functionality is accessible in the Design Time environment (this is the same environment marketers use for Campaign) and can be found in the Interactive Channel’s Simulator tab.   DETAILS  ​A set of commonly used API methods (startSession(), getOffers() and endSession() is used to build your reusable simulation scenario. Users can define against which Audience ids the coverage analysis scenario will run (All or a custom defined selection of audience ids using filter criteria in the profile data)​The scenario can be run against All of a selection of Zones. The user can choose whether to take Event pattern existing states and Offer suppression rules into account when running the scenario.   In order to create a new coverage scenario open the Scenario tab in the Marketing Suite Interactive channel definition screen. ​ You can select All or a selection of Zones: ​ You can use all Audience ids or apply a filter condition: ​ The scenario editor also allows you to add additional columns from the profile data to capture during the scenario run: ​ Indicate whether to apply existing event pattern state and offer suppression rules: ​ ​Note that depending on the size of the profile data table (and the complexity of...
Marketing & Commerce | September 27, 2018
Planning for Marketing Effectiveness
Planning for a campaign is much easier with Marketing Suite products which are designed to cater to every marketing objective or activity. Marketing Effectiveness helps in reducing the time and budget for any Campaign. The below article will help to understand the steps
Marketing & Commerce | September 6, 2018
Using Campaign Outbound Triggers
An outbound trigger is the execution of a command, batch file, or script (that is stored on the Campaign Application Server) that takes place after a flowchart or process is run. You can define triggers to perform virtually any action, such as opening an application, sending an email, or running a program.
Automation | August 27, 2018
Using Campaign Inbound Triggers
  This blog will take you through the Inbound Triggers – triggers sent from other applications to Campaign. Inbound Triggers Inbound triggers are triggers sent from other applications to Campaign.  The other applications send information to the unica_actrg executable that resides in the bin directory (<CAMPAIGN_HOME>/bin).  The application calls unica_actrg and passes parameters: ​ Usage of unica_actrg ​Possible parameters can be seen by typing ‘unica_actrg’ from the command line: Unica_actrg [-p <port.] [-s ] [-v] [ | | -n ] , , … Where items enclosed in [] brackets are optional.   The | sign indicates an ‘OR’ – campaign code can be used, or campaign name or flowchart name.   -v is used to indicate the version of the Campaign Trigger Utility.   Examples: 1)     All flowcharts waiting for ‘Go’ This would send a message to continue execution of all flowcharts (the * is a wildcard) waiting for the command ‘go’.   Tip:  In Unix, if there are spaces in the campaign name or flowchart name this will cause an error.  To avoid this put quotes around the asterisk. <CAMPAIGN_HOME>/bin/unica_actrg ‘*’ Go   2)     All flowcharts waiting for ‘Go’ specifying the port.   <CAMPAIGN_HOME>/bin/unica_actrg –p 5664 ‘*’ Go   This would call the Campaign on port 5664 (if multiple versions of Campaign are installed on the same server you may need to specify the port) and send a message to continue execution of all flowcharts (the * is a wildcard) waiting for the command ‘Go’.   3)     A specific flowchart waiting for the command ‘Go’ <CAMPAIGN_HOME>/bin/unica_actrg TestFlowchart Go   This would send a message to continue execution of the flowchart ‘TestFlowchart’ waiting for the command ‘Go’. Campaign A Triggers Execution of Campaign BIn this example Campaign A will send an outbound trigger that will then be the inbound trigger that Campaign...
Marketing & Commerce | August 15, 2018
Configuring Db Loader with Interact Runtime
About As we all know Interact is used for delivering optimal, personalized messages in real-time across marketing channels. Interact communicates with the customer-facing touch point using the runtime servers.​You can learn more about Interact architecture here. ​By default, the runtime environment writes contact and response history data from session data into staging tables. On a very active production system, however, the amount of memory required to cache all the data before runtime can write it to the staging tables may be prohibitive. You can configure runtime to use a database load utility to improve performance.When you enable a database load utility, instead of holding all contact and response history in memory before writing to the staging tables, runtime writes the data to a staging file.You define the location of the directory containing the staging files with the  externalLoaderStagingDirectory property.This directory contains several subdirectories. The first subdirectory is the runtime instance directory, which contains the contactHist and respHist directories.The contactHist and respHist directories contain uniquely named sub directories in the format of audienceLevelName.uniqueID.currentState, which contain the staging files.Here are the detailed steps for configuring Db loader with Oracle, Db2 and Sql Server. Db Loader configuration for Oracle: 1.  Create a Data Source under asm_admin as "systemTablesDataSource". Specify the login details of the Interact Runtime specified in the "InteractRTDS" JNDI2. Need to update below configuration Update the parameters under - "Affinium|Interact|general|systemTablesDataSource|loaderProperties" as follows:databaseName: ujanidatabaseName must be correctly specified as SID.loaderCommandForAppend: /data/unica/qa/interact/RG_ACI753_RT_8100/Affinium/Interact/loaderService/ <CONTROLFILE> <TABLE> <USER> <PASSWORD> <DATABASE> is located under <Interact_Home>/ loaderService directory update above configuration with path to it along with the mentioned arguments.loaderControlFileTemplateForAppend: /data/unica/qa/interact/RG_ACI753_RT_8100/Affinium/Interact/loaderService/oraload_control_template.txtFor above configuration update path till Oracle Control template file located under  <Interact_Home>/ loaderService directory at your installation directory.loaderDelimiterForAppend: |loaderDelimiterAtEndForAppend: FalseloaderUserLocaleDP: False   3.   Update the parameters under "Affinium|Interact|services" as follows: externalLoaderStagingDirectory: /data/unica/qa/interact/RG_ACI753_RT_8100/Affinium/Interact/loaderService/staging Mention path till <Interact_Home>/loaderService/staging...

Upcoming Event

HCL Volt MX – How Low Code Visual Assembly Can Drive Your Business
April 29, 2021, Webinar