Skip to content

Commit 18cdbc6

Browse files
Apply suggestions from code review
fix: use parentheses judiciously Co-authored-by: Ruth Cheesley <[email protected]>
1 parent 064ad6a commit 18cdbc6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/campaigns/campaign_builder.rst

+3-3
Original file line numberDiff line numberDiff line change
@@ -247,14 +247,14 @@ For the Send Email, Marketing Message, Push Contact to Integration and Send a We
247247

248248
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.
249249

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

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.
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.
253253
- If the Contact is within the optimal window at that moment, the event executes immediately.
254254
- If the current time is before today's optimal window, the event schedules for the first hour of that window.
255255
- If the current time is after today's optimal window, the event schedules for the first hour of the next day's optimal window.
256256

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.
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.
258258
- If the Contact is within the optimal window at that moment, the event executes immediately.
259259
- If the current time and day are before the optimal window, it schedules for the first optimal hour of the next optimal day.
260260

0 commit comments

Comments
 (0)