Day & Hour Parting v1
NOTE: This documentation applies to legacy day parting features. In July 2020, Kevel released a new set of features that allows up to 10 day parts per flight. To learn about these new features, please see: Day & Hour Parting v2 and New in Kevel: Add up to 10 Day Parts on a Flight.
Day & Hour parting is set at the Flights level.
Overview
Day Parting allows you to limit a flight to serve on specific days, times, or both.
For instance, you could target users just in the evening or just on the weekends.
To serve the flight at the same specific time period every day, you must check all days.
Kevel currently Coordinated Universal Time (UTC / GMT), so be sure to account for any time zone difference when setting up day/hour parting. Day-parting is tied to UTC, not the specific user's time zone.
Soon, you'll be able to pick a time zone for a flight. This will allow you to schedule day parts in the local time of the flight, instead of converting day parts to GMT every time. Note that if you set a non-GMT time zone for your flight, you will also need to update the day part on your flight to use the new time zone.
Setting Up via the UI
NOTE: New day parting features allow creating up to 10 day parts per flight. These features need to be enabled on each network. Learn more on the Day & Hour Parting v2 page.
- Click on the 'Day Parting' tab on the left
- Set the times and/or days you'd like it to serve
- Save
Enabling via the API
NOTE: New day parting features that allow for up to 10 day parts per flight use their own API endpoints. These features need to be enabled on each network. Learn more on the Day & Hour Parting v2 page.
Use the below parameters in the Create Flight request.
For day-of-week parting, use boolean logic around the parameters of IsSunday
, IsMonday
, etc, where true
means you want to specifically target this day.
If you want to exclude a day, you can set it to
false
. You do not need to enable the other six days totrue
Property | Descriptions |
---|---|
DatePartingStartTimeISO (string) | Format: HH:MM:SS , or 21:00:00 |
DatePartingEndTimeISO (string) | Format: HH:MM:SS , or 21:00:00 |
IsSunday (boolean) | Whether to show ads on Sunday or not. Default = null |
IsMonday (boolean) | Whether to show ads on Monday or not. Default = null |
IsTuesday (boolean) | Whether to show ads on Tuesday or not. Default = null |
IsWednesday (boolean) | Whether to show ads on Wednesday or not. Default = null |
IsThursday (boolean) | Whether to show ads on Thursday or not. Default = null |
IsFriday (boolean) | Whether to show ads on Friday or not. Default = null |
IsSaturday (boolean) | Whether to show ads on Saturday or not. Default = null |
For time-of-day parting, use Military Time (not AM/PM)
For example, to create a flight that targets:
- Just the weekend (Sat/Sunday)
- Just noon to 8pm (using GMT)
use this Create Flight request:
{
"CampaignId":1234,
"PriorityId":1325,
"Name":"Test",
"StartDateISO":"2017-05-01T00:00:00.00.0000000",
"GoalType": 1,
"DatePartingStartTime": "12:00:00",
"DatePartingEndTime": "20:00:00",
"IsSunday": true,
"IsSaturday": true
}
You can also update the caps with the Update Flights endpoint.
Troubleshooting Non-UTC Times
NOTE: New day parting features now permit day parts to cross midnight GMT. These features need to be enabled on each network. Learn more on the Day & Hour Parting v2 page.
Given that the system uses UTC, it may be the case you have to split apart a flight into two to make time-of-day parting work, if the start/end dates cross the midnight UTC cut-off.
For instance:
Target PST Hours | UTC Time (7 hrs ahead) | Flight 1 (UTC) | Flight 2 (UTC) |
---|---|---|---|
10am - 2pm | 5pm - 9pm | 5pm-9pm | N/A |
4pm - 8pm | 11pm - 3am (crosses midnight) | 11pm-12am | 12am - 3am |
In this case, to target 4pm-8pm PST, you'll have to create two flights, one targeting the time before midnight UTC, and the other targeting the hours after midnight UTC.
Updated about 3 years ago