Skip to content

Commit e37ef7c

Browse files
authored
Merge pull request #302 from patrykgruszka/DPMMA-2688_smart-camapign-schedule
DPMMA-2688 Smart Campaign Event Scheduling Based on Contact Behavior
2 parents 487f19b + 78ba028 commit e37ef7c

File tree

4 files changed

+38
-0
lines changed

4 files changed

+38
-0
lines changed

docs/campaigns/campaign_builder.rst

+22
Original file line numberDiff line numberDiff line change
@@ -237,6 +237,28 @@ This **doesn't work** for the Anniversary option.
237237

238238
If a Contact appears again at a later date in that Segment because the value of the date has changed, then the Contact passes through the Campaign only once, and hence isn't included in the Campaign again.
239239

240+
241+
Smart event schedule
242+
~~~~~~~~~~~~~~~~~~~~~
243+
244+
For the Send Email, Marketing Message, Push Contact to Integration and Send a Webhook actions, Mautic provides a smart event schedule option. This feature dynamically optimizes the timing of event execution based on individual Contact behaviors, increasing the likelihood of engagement.
245+
246+
**How it Works**
247+
248+
1. **Interaction data retrieval**: the system retrieves interaction data for the Contact, including Email reads, Landing Page hits and Form submissions, to analyze the Contact's engagement patterns.
249+
250+
2. **Minimum interactions requirement**: a Contact must have a minimum number of interactions for the system to calculate optimal timing. Each interaction type - Email open, website visit, Form submit - counts only once per hour. When a Contact doesn't have enough interaction data, default hour ranges and days adjust to the Contact's preferred timezone.
251+
252+
3. **Optimal time calculation - execute event within 24 hours**: based on the Contact's interaction data, the system calculates the optimal time for executing a Campaign event, considering the Contact's historical engagement patterns.
253+
- If the Contact is within the optimal window at that moment, the event executes immediately.
254+
- If the current time is before today's optimal window, the event schedules for the first hour of that window.
255+
- If the current time is after today's optimal window, the event schedules for the first hour of the next day's optimal window.
256+
257+
4. **Optimal date calculation - execute event within 7 days**: the system calculates the optimal time as in the previous option and additionally determines the best day of the week. By default, a Contact can have multiple optimal days.
258+
- If the Contact is within the optimal window at that moment, the event executes immediately.
259+
- If the current time and day are before the optimal window, it schedules for the first optimal hour of the next optimal day.
260+
261+
240262
.. vale off
241263
242264
Triggering Campaign events
Loading
Loading

docs/configuration/settings.rst

+16
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,22 @@ Campaign settings
158158

159159
* **Use summary statistics** - Improves performance when viewing a Campaign with thousands of events per day by using summarized data. When you first turn on this setting you need to run a :ref:`cron job<campaign cron jobs>` to summarize existing data.
160160

161+
Optimal for Contact event scheduler
162+
===================================
163+
164+
.. image:: images/optimal-event-scheduler-settings.png
165+
:width: 600
166+
:alt: Screenshot showing Optimal for Contact event scheduler settings configuration in Mautic
167+
168+
The optimal for Contact event scheduler settings allow you to configure the default timing and caching options used in the optimized event scheduler for Campaigns.
169+
170+
* **Default Optimal Start Hour** - Set the default start hour for the optimal interaction window when specific Contact data is unavailable.
171+
* **Default Optimal End Hour** - Set the default end hour for the optimal interaction window when specific Contact data is unavailable.
172+
* **Default Optimal Days** - Select the default days of the week considered optimal for interaction when specific Contact data is unavailable.
173+
* **Interaction Data Cache Timeout** - Choose how long to cache the interaction data for.
174+
* **Fetch Interactions From** - Select the time frame for fetching interaction data. This determines how far back to look for interactions.
175+
* **Interaction Fetch Limit** - Set the maximum number of interactions of each type - for example: Page hits, Email reads, Form submits - to retrieve for timing optimization.
176+
161177
Email settings
162178
**************
163179

0 commit comments

Comments
 (0)