Fatigue rules allow marketers to set global cross-channel business rules that will automatically exclude over-solicited profiles from campaigns.
To implement fatigue rules, you define a maximum number of messages per profile and select a period on which the rule will apply. During delivery preparation, profiles are excluded from the delivery if applicable, depending on the number of messages already sent to them.
For fatigue rules to apply, you need to define a contact date for your delivery. If you choose to send messages immediately, the fatigue rule will not be applied.
In the Channel field, select which channel your rule will apply to. You can either select a single channel (email, SMS, direct mail, mobile application) or select All channels. See Choosing the channel.
In the General tab, define the method for calculating the maximum number of messages per profile. You can choose either a constant threshold or a variable. You can also refine the threshold on profiles and deliveries. For more on this, refer to Defining the threshold.
Choose a Sliding period on which the typology rule will apply. For more on this, refer to Setting the sliding period.
In the Application criteria tab, you can choose to apply this rule to all deliveries or restrict the applicability of the rule according to the message to send. The rule will only execute if the application condition is met. For example, you can apply the rule only on messages with a label starting with a given word or with an ID containing certain letters. See Restricting the applicability of a filtering rule.
During delivery preparation, profiles are excluded from the delivery if applicable, depending on the number of deliveries already sent to them. You can view the fatigue rule execution results in the delivery logs. See Viewing the fatigue results.
For fatigue rules to work, you need to define a contact date for your delivery. If you choose to send messages immediately, the fatigue rule will not be applied.
Fatigue rules are available for various channels. The channel is defined in the Channel field of the typology rule settings. You can either select a single channel or select All channels.
Mobile application: this channel allows you to send push notifications to profiles or to app subscribers. If you choose to send notifications to profiles, they will be compatible with multi-channel fatigue rules.
Fatigue rules are not compatible with push notifications sent to app subscribers. If you're sending messages to app subscribers, fatigue rules will not apply.
Fatigue rules are compatible with all delivery types: one-shot deliveries, recurring deliveries, workflow deliveries and transactional messages.
Transactional messaging can be used to send service messages targeting an event (rtEvent) as well as marketing messages (targeting profiles), for example a remarketing message. Fatigue rules are compatible with marketing messages only (targeting profiles). Event transactional messages do not contain profile information, therefore they are not compatible with fatigue rules (even in the case of an enrichment with profiles). With the support of marketing messages in transactional messaging, you can apply a fatigue rule to all channels including marketing transactional messages.
Each fatigue rule defines a threshold, that is to say the maximum number of messages that can be sent to one profile over a given period. Once this threshold has been reached, no more deliveries can take place until the end of the period considered. This process lets you automatically exclude a profile from a delivery if a message exceeds the set threshold, thus avoiding over-solicitation.
Threshold values can be either constant or variable. This means that for a given period, thresholds can vary from one profile to another, or even for the same profile.
The threshold represents the highest number of messages that can be sent to a profile during the concerned period.
By default, the threshold is constant and you need to indicate a maximum number of messages authorized by the rule.
To define a variable threshold, select the Depends on the recipient value in the Threshold type field.
select a profile field: the threshold will vary for each profile according to the selected field. For example, if you have extended the profiles resource with a 'Communication frequency' field, click the button on the right of the Threshold computation formula field and select your field. For each profile, the threshold will take the value of the 'Communication frequency' field.
define a formula: click the second button on the right of the Threshold computation formula field to define an advanced threshold calculation formula. For example, you can index the number of authorized messages according to the segment to which the profile belongs. This means that a profile belonging to the 'Web' segment may receive more messages than other profiles. An Iif (@origin='Web', 5, 3) type formula authorizes the delivery of 5 messages to profiles of the Web segment and 3 for other segments.
By default, all messages are taken into account for threshold calculation. Check the Refine Threshold on profiles and deliveries box to filter the profiles and deliveries to count when preparing the delivery.
In the following example, only male profiles are counted and only deliveries with a label starting with Newsletters are counted.
Refining the threshold on deliveries is different than restricting the applicability of the entire rule (Application criteria tab):
Application criteria: you choose to execute the rule or not according to specific criteria. For example, if your application condition is 'Label starts with Newsletter', the rule will only apply to deliveries which respect this condition. If the delivery's label starts with 'Promotion', the rule will not execute at all.
Refine threshold on profiles and deliveries > Deliveries to count: all deliveries using this typology rule will execute the rule, but you decide, among the past and scheduled deliveries, which ones you want to count. For example, if your restriction is 'Label starts with Newsletter', the rule will be executed even if the delivery label starts with 'Promo'. It will count, over the selected sliding period, the number of deliveries whose label starts with 'Newsletter'.
Fatigue rules are defined in n-day rolling periods. The period is configured in the Sliding period section, for example 2 weeks, 7 days or 5 hours.
When the rule executes, both past deliveries and scheduled deliveries are taken into account. This guarantees that, on a given sliding period, the threshold is never exceeded.
For example, if you define a 48-hour period, the system will be looking 48 hours before the contact date and 48 hours after the contact date. So, the selected period is doubled to enable the integration of future deliveries as well as previous ones.
To restrict the deliveries taken into account to a 2-week period, enter Day and 7 or 1 week in the Sliding period section. Deliveries sent up to 7 days before the delivery date and scheduled up to 7 days after the delivery date on which the rule is applied will be taken into account in the calculation.
During delivery preparation, profiles are excluded from the delivery if applicable, depending on the number of deliveries already sent to them. To view fatigue rule execution results, click the button in the bottom right corner of the Deployment block.
Three tabs are available, showing you the details of the fatigue execution results including the name of the rule that applied:
Adobe Campaign features a dedicated report on fatigue rules to help you understand how they are applied to your campaigns. This allows you to learn how your campaigns impact one another and make the right adjustments.
The Fatigue rules summary report can be accessed from the Reports button, in the top right corner of each program, campaign, and message.
In the left part of the screen, you can filter the report data on the deliveries' contact date. By default, the selected period starts 15 days before the current date and ends 15 days after. You can also filter on a specific fatigue rule.
The bottom table displays all deliveries within the selected period. For each delivery, you can see the fatigue rules that applied and the corresponding exclusions. Deliveries which do not have a contact date are also displayed in the table.
The displayed data is not contextual to the program, message or campaign you access the report from. This report displays all fatigue rules and deliveries for all organizational and geographical units. This allows you to get a global view of all deliveries in order to understand how your campaigns are influenced by others.
There are many possibilities in terms of fatigue management implementation. Here are some examples of what you can do:
Let's say you create a multi-channel rule, with a constant threshold of 3 over a sliding period of 7 days.
Last week, your premium profiles received a promotion email and a transactional remarketing email. You also scheduled an SMS that will be sent next week. Today, you decide to send a push notification targeting all your profiles. The premium profiles will be excluded from today's push because their maximum number of messages over a 2-week period has already been reached.
You have extended the profiles resource with a 'Communication limit' field, to define a different threshold for each profile. In your fatigue rule, define a variable threshold based on this field and select a sliding period of 2 days. Let's take two examples of profiles: John has a communication limit of 1 and David has a threshold of 2. Both have already received a newsletter email yesterday. You decide to send them another email today. Only David will receive it, because John has been excluded from the target.
You want to change the threshold according to the age of your profiles. If a profile is under 40, you want to define a limit of 4 and for older profiles, a limit of 2. Instead of defining this threshold for each profile with an extended field, you can create a formula directly in your fatigue rule to calculate the threshold according to the profiles' age. In our example, the formula would be Iif (@age<40, 4, 2).
This section also includes a step-by-step example of a fatigue rule using a threshold computation formula.
You have extended the profiles resource with a 'Score' field and you also have extended the deliveries resource with a 'Type' field. You want to define a constant threshold of 3 but you want to exclude from the count all the deliveries of the type 'Alert' or 'Black Friday' and all the profiles with a score greater than 10. When the rule will execute, it will count, among the past and scheduled deliveries, all the deliveries that are not of the type 'Alert' or 'Black Friday' sent to profiles whose score is smaller than 10.
In this use case, we want to create a typology rule to prevent the delivery of more than 2 messages per week to premium profiles and 2 messages per week to standard profiles.
To identify customers and prospects, we extended the profiles resource with the Status field, which contains 0 for premium profiles and 1 for standard profiles.