The Campaign Execution page lets Admins configure how and when campaigns are executed on your site — how long the batch data is considered fresh, how long Optimove will wait for a late batch data update, and the site-wide defaults for conditional execution.
| Tab | Who sees it |
|---|---|
| Data Freshness | Campaign Execution 2.0 sites only |
| Scheduled Conditional Execution | Sites with scheduled conditional execution enabled |
| Triggered Conditional Execution | Sites with triggered conditional execution enabled |
Prerequisites
- You must have an Admin role to access this page.
Navigating to Campaign Execution
- Click the Settings icon in the main navigation menu.
- Under the General Settings category, select Campaign Execution.
Data Freshness
The batch data update is the main process that refreshes data. Regular campaigns (not marked as "run anyway") only run while this data is considered fresh. Once it expires, regular campaigns will not run. Relevant for scheduled campaigns only.
Choosing a freshness method
- Open the Data Freshness tab.
- Select one of the two methods:
- Specific hour — Data is considered fresh until a fixed time on the next day after the batch data update completes. Enter a value in "Data will be considered fresh until this hour in the next day (24-hour format):" This is applied in your site's time zone.
- Duration in hours — Data is considered fresh for a set number of hours after the batch data update completes. Enter a value in "Data will be considered fresh for the following duration (in hours):" The default is 24.
- Click Save.
Which method should I use?
- Specific hour: Use this if you want early-morning campaigns to wait for the new batch data before sending. Setting this to 00:01 in your site's time zone matches the behaviour from before the CE 2.0 migration — campaigns scheduled before the batch data update completes will hold until it finishes.
-
Duration in hours (default: 24): Use this if your batch data update always completes before your first campaign of the day, or if campaigns can run on the previous day's data without issue.
Note: this is the default applied when a site is first migrated to CE 2.0.
If your site was recently migrated to CE 2.0 and campaigns ran on stale data or returned no customers, check that this has been updated from the 24-hour default to a specific hour. See Batch Data Freshness in the Campaign Execution 2.0 guide for a full explanation.
Allowed delay time
When a regular campaign reaches its scheduled time but cannot run (for example, due to a delay in the batch data update), Optimove will keep trying to execute it during this time window.
- In the Data Freshness tab, set Allowed delay time.
- Click Save.
For the full behavior, including a worked example, see Batch Data Freshness in the Campaign Execution 2.0 article.
Scheduled Conditional Execution
What is Conditional Execution?
Conditional Execution performs a final check on a customer's eligibility at the exact moment a campaign is sent. If the customer no longer meets the Target Group's criteria, they are excluded from the campaign, even if they were eligible when it was originally scheduled.
Require conditional execution for scheduled campaigns by default
- OFF (Default): When a user creates a new scheduled campaign, the "Conditional Execution" flag will be turned off. They can choose to turn it on manually.
- ON: When a user creates a new scheduled campaign, the "Conditional Execution" flag will be turned on automatically. They can still manually disable it if needed for a specific campaign.
Heads up time
The time your system has to approve or reject customers after the "Event type 5" notification is sent.
- Default: 60 minutes
- Minimum: 1 minute
- Maximum: 12 hours
Deadline
All customers must be approved or rejected before the deadline, which is 5-15 minutes before the scheduled campaign time.
For more on conditional execution, see Conditional Execution V2 and Scheduled Conditional Execution.
Triggered Conditional Execution
Require conditional execution for triggered campaigns by default
- OFF (Default): When a user creates a new triggered campaign, the "Conditional Execution" flag will be turned off.
- ON: When a user creates a new triggered campaign, the "Conditional Execution" flag will be turned on automatically. They can still manually disable it if needed.
After making your changes, be sure to click the Save button in the bottom-right corner to apply the new settings.