Hypothesis templates hypothesis-templates

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.

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.

For more on defining and configuring a control group, refer to this section.

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. Learn more

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.

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:

1. Click the Frequency of execution… link, then the Change… button.

   

2. Configure the frequency, the related events and the validity period.

   

3. 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.

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. Learn more).

Transaction/Margin amount: these fields are optional and enable you to calculate turnover indicators automatically. Learn more

Unit amount: lets you set an amount for calculating revenue. Learn more

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.

Filter on transactions: in the Scope tab, you can configure a filter on the hypothesis. To do this:

1. Click the Edit query link.

   

2. Specify your filtering conditions.

   

3. 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.):

1. Click the Add a filter link, then Edit query.

   

2. Specify your filtering conditions.

   

3. Click Finish to save your query.

   

Script: you can use a JavaScript script to dynamically overload the hypothesis settings during its execution.

To do this, click the Advanced settings link then enter the desired script.