Every marketer aims to achieve better click rates, easy conversions, reduce the churn rate, and create a memorable experience for their customers. To accomplish it, the decisions they take while sending out emails, designing CTAs, landing pages, and even sending out offers should be inline with the customer they are targeting. To avoid the assumptions of what shall work and what won't, A/B testing, also known as split testing, is the marketing technique that utilizes two versions of the webpage, application, offers, email, or any other marketing asset to analyze and understand which one performs better. A/B testing is essential as different customers may react differently to varied situations. For example, some might want the 'Buy Now' button in the center of the page, and others might like on the bottom right corner. But which one of them leads to the most conversions? Is the answer that A/B testing can provide. How A/B Testing works in Interact? In Interact, an A/B Testing is a test done for a treatment rule with all its properties fixed, but only one parameter varies. In 12.1, this parameter is a combination of offer and its offer attributes. In an A/B testing of a rule, each varying-parameter represents one branch with audience distribution percentage. Depending on the response of the Audience for an Offer in a set Test Period, you can choose the best suitable offer for that treatment rule. Set up A/B Testing for Treatment Rule A new option A/B, is added to the Rule menu; you can directly land to A/B Testing pane by using it. On A/B Testing tab, you can enable A/B Test for a Rule by selecting Enabled Check Box. After enabling the A/B Test for a Rule, a Default branch will be added by copying details from the base...

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/oraload.sh <CONTROLFILE> <TABLE> <USER> <PASSWORD> <DATABASE>oraload.sh 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...