SAP Hybris Marketing - Target group based email campaigns - chapter 3

[joerg_steinmann]

Chapters

1. Segmentation and Target Group


2. Email content and usage of personalization attributes


3. Campaign definition


4. Campaign execution

 

3. Campaign definition

The following campaign automation model will be defined and used for explanation in subsequent chapters.



Following combinations of target group and email content are supported:

a)

Target group TG1 is created by a segmentation model SM1 which uses segmentation profile SP1. Segmentation profile SP1 uses segmentation object SO1.

Target group TG1 is a dynamic target group.

Emails EM1 – EM2_1 can have no personalization attributes or personalization attributes of interaction contact or personalization attributes coming from segmentation object SO1 (or a combination of attributes from interaction contact and segmentation object SO1).

 

b)

Target group TG1 is created by a segmentation model SM1 which uses segmentation profile SP1. Segmentation profile SP1 uses segmentation object SO1.

Target group TG1 is a static target group.

Emails EM1 – EM2_1 can have no personalization attributes or personalization attributes of interaction contact or personalization attributes coming from segmentation object SO1 (or a combination of attributes from interaction contact and segmentation object SO1).

 

c)

Target group TG1 is a static target group without any relation to a segmentation model.

Emails EM1 – EM2_1 can have no personalization attributes or personalization attributes of interaction contact.

 

 

Campaign is executed only once

The campaign is defined as “One-Time” campaign. It can be started immediately or scheduled for future execution at a given date and time.

 

 

Campaign is executed periodically

The campaign is defined as “Recurring” campaign. You have to define the recurrence, when the campaign shall end and which weekday it shall be executed if recurrence uses hours or days. Its first execution can be started immediately or scheduled for future execution at a given date and time.

 

 

Follow-up actions

For follow-up actions you can define when the action shall be executed:

Any Day (default setting)

This is the default setting. The action will be executed on any week day immediately after the trigger has occurred.

Optionally you can define a delay of days.

• If the action is assigned to the “Yes” branch of the trigger you can define the number of days the action shall wait until it is executed. One day means exactly 24 hours. In addition you can set a time when the action shall be executed. Both options are independent, this means you can define a time but set days of delay to zero.


• If the action is assigned to the “No” branch of the trigger you can set a time when the action shall be executed. The delay of days is not available because in the “No” branch you have defined already a waiting period in days. Also here 1 day means exactly 24 hours.

Specific Days

You can select one or more weekdays. In addition you can define a particular time.

The action will be executed on the selected weekday only.

Example:

Action “Send Email” for trigger “Click Through” shall be executed only on Saturday and Sunday at 09:00. If an email recipient has clicked on Monday and another recipient on Thursday, both will get the next email on Saturday. If a third email recipient has clicked on Saturday at 15:45, this recipient will get the next email on Sunday 09:00.

Specific Date and Time

You define a particular day and time.

 

Detailed examples are described in chapter Campaign execution.

 

Previous chapter Email content and usage of personalization attributes

Next chapter Campaign execution