Configuring the hypothesis template lets you define the context for measuring reactions, whether for a delivery or for an offer. This is where the various measuring tables are referenced, including those for defining relations between individuals, hypotheses and the transaction table.
To create a hypothesis template, apply the following steps:
In the Adobe Campaign explorer, click Resources>Templates>Hypothesis templates.
Click New or right-click in the list of templates and choose New in the drop-down list.
Enter the hypothesis label.
Specify whether the template is destined for hypotheses on offers or deliveries via the Hypothesis type.
For Delivery type templates, specify whether measurements should be carried out with or without a control group (for more on this, refer to Properties of a hypothesis template).
For Delivery type templates, you can choose a specific channel or decide to apply the template to all available channels in Adobe Campaign using the Channel drop-down list (for more on this, refer to Properties of a hypothesis template).
Select the Execution folder in which you wish to create and automatically execute the hypotheses that will be created from this template.
Choose the execution settings (for more on this, refer to Hypothesis template execution settings).
Specify the hypothesis calculation period (for more on this, refer to Hypothesis template execution settings).
This period is determined from the contact date.
In the Transactions tab, specify the tables and fields required for the hypothesis calculation (for more on this, refer to Transactions).
If your template is configured for Offer type hypotheses, you can enable the Update offer proposition status option: in this case, select the status of the offer proposition you want to change.
Specify the scope of the hypothesis application (for more on this, refer to Hypothesis perimeter).
If necessary, use a script to complete filtering (for more on this, refer to Hypothesis perimeter).
The template’s General tab lets you specify the general template options. The available fields are:
Hypothesis type: lets you determine whether the template should be destined for hypotheses on deliveries or offers.
You can also choose to create a hypothesis that will apply to both deliveries and offers.
If the template applies to offers, the Update offer proposition status option is available in the Transactions tab.
Measurement with control group: lets you state whether a control group has been defined for the delivery or the campaign and include it in measurement indicators. The control group, which doesn’t receive deliveries, lets you measure the impact of the campaign after the delivery, by comparing it with the target population which did receive the delivery.
If the template is configured to take a control group into account, but no group is defined in the delivery which the hypotheses concern, the results will be based on targeted recipients only.
For more on defining and configuring a control group, refer to Defining a control group.
Channel: you can choose a specific channel or make the hypothesis template available to all channels in the Adobe Campaign console by selecting All channels in the drop-down list. If you configure the template for a specific channel, this lets you automatically filter deliveries per channel when creating the hypothesis (refer to Creating hypotheses).
Execution folder: lets you specify the execution folder for the hypothesis.
Taken into account in campaign ROI calculation: takes the hypothesis result into account in the ROI calculation for the related campaign.
The template’s General tab also lets you specify the hypothesis execution parameters. The options available are as follows:
Schedule execution for a time of low activity: lets you schedule the hypothesis launch to optimize Adobe Campaign performances. When this option is checked, the processing workflow on campaigns executes hypothesis calculation during downtime.
Priority: level applied to the hypothesis to space out the hypothesis calculation orders if there are simultaneous executions.
Automatic execution: if necessary, lets you schedule hypothesis recalculation (for example, if you want to update indicators regularly until the end of the delivery).
To specify a schedule, apply the following process:
Click the Frequency of execution… link, then the Change… button.
Configure the frequency, the related events and the validity period.
Click Finish to save the schedule.
Log SQL queries in journal: this function is reserved for expert users. It lets you add a tab to the measuring hypothesis audit to show SQL queries. This enables the detection of possible malfunctions if a simulation finishes with errors.
Keep execution workflow: lets you keep the workflow that was automatically generated at the start of the hypothesis calculation. In the hypotheses created from a template that has this option checked, the generated workflow is available to follow the process.
This option must be activated for debugging purposes only, in case of error while running the hypothesis.
In addition, workflows generated automatically must not be modified. Any eventual modification would not be taken into account elsewhere for later calculations.
If you have checked this option, delete the workflow after it has executed.
This tab contains the various fields and tables which let you save the history of recipient reactions in terms of transactions. Refer to the Configuration guide for more information on the tables dedicated to response management.
Schema (reaction log storage): select the recipient reaction table. The out-of-the-box table in Adobe Campaign is NmsRemaMatchRcp.
Transaction schema: choose the table that the hypotheses will concern, i.e. the transaction or the purchase table.
Querying schema: choose the criteria for filtering the hypothesis.
Link to individuals: choose the link between individuals and the table used as a transaction schema.
Link to the household: select the link to the household in the transactions schema if you wish to include all members of a household in a hypothesis. This field is optional.
Transaction date: this field is optional but recommended since it lets you define a scope for hypothesis calculation.
Measurement period: lets you configure start and end dates during which hypotheses are executed and purchase lines are recovered.
When the hypothesis is linked to a delivery, measurement is automatically triggered a few days after the contact date for direct mail deliveries, or after the delivery date for email or SMS deliveries.
If the hypothesis is launched on the fly, it can be forced if would like to trigger it immediately. Otherwise, it is triggered automatically based on the configured end of calculation date, which is based on the hypothesis creation date (refer to Creating a hypothesis on the fly on a delivery).
Transaction/Margin amount: these fields are optional and enable you to calculate turnover indicators automatically (refer to Indicators).
Unit amount: lets you set an amount for calculating revenue (refer to Indicators).
Additional measures and data: lets you specify additional reporting measures or axes from fields in the different tables.
Update offer proposition status: lets you change the status of the offer proposition if an offer recipient is identified by the hypothesis.
Filtering on transactions: in the Scope tab, you can configure a filter on the hypothesis. To do this:
Click the Edit query link.
Specify your filtering conditions.
Select the transaction which the hypothesis will concern.
Filter on recipients: in the Scope tab, you can limit your hypothesis to any information linked to a message (delivery, recipient, email address, service, etc.):
Click the Add a filter link, then Edit query.
Specify your filtering conditions.
Click Finish to save your query.
To do this, click the Advanced settings link then enter the desired script.
This option is for expert users.
In this example, we are going to create a hypothesis template on a direct mail type delivery. The transaction table (Purchases in our example) which the hypotheses will be based on contains purchase lines linked to articles or products. We want to configure our model to create hypotheses on articles or products in the purchase table.
In the Adobe Campaign explorer, go to the Resources > Templates > Hypothesis templates node.
Click New to create a template.
Change the template label.
Select Deliveries as a hypothesis type.
Specify that the delivery can contain a control group by checking the relevant box.
Choose the Direct mail channel.
Since the template is specific to direct mail deliveries, hypotheses created using this model may not be linked to any other delivery types.
In the Transactions tab, select the recipient reactions table.
In the Transactions schema field, choose your purchase table.
Select purchase lines in the Querying schema field.
Choose the recipients linked to the purchase table.
Select the field linked to the purchase date.
This lets you define a time frame for hypotheses. This stage isn’t mandatory but it is recommended.
Configure the calculation period for 5 to 25 days.
In the Scope tab, click Edit query to create a filter on hypotheses.
The template created thus enables you to run hypotheses on the products or articles in the purchase table.
Click Save to record your template.