If you have landed here you have pasted an error string into a search box, probably with the code #1487675 next to it, which means you want the cause and the fix rather than an essay. Both are below, then the context for why Meta refuses this combination at all.
Direct answer: Dayparting needs an ad set that paces a fixed budget across a fixed period, which means standard pacing on a lifetime budget. Accelerated or no-pacing delivery spends as fast as the auction allows and has no period to pace across, so a schedule cannot mean anything and Meta rejects it. Set lifetime budget, set standard pacing, then apply the schedule, in that order. If the ad set has to stay on a daily budget, no pacing change will help and you need the throttle approach instead.
Questions that bring people here
Why the two settings genuinely cannot coexist
A schedule is an instruction about when a budget may be spent. That instruction only makes sense if there is a defined pot and a defined window to spread it over, which is exactly what a lifetime budget is.
Accelerated delivery is the opposite instruction: spend this as fast as possible. Asking for both is asking the system to hold budget back and not hold budget back, so rather than silently discarding one, Meta rejects the pair. That is better behaviour than the alternative, even though it does not feel like it at the time.
Why the API is stricter than the interface
Ads Manager mostly stops you reaching this state by not showing the scheduling control on ad sets that cannot support it. The API has no such courtesy: it accepts the field and validates afterwards.
So this error is usually a sign you are working at scale, through a partner tool, a bulk sheet or your own integration. If that is where you are, the practical lesson is to validate budget type and pacing before writing schedules across a batch, rather than discovering it one rejection at a time. The batching discipline is in bulk Meta ads edits.
Before you switch to lifetime, ask whether you should
The fix is easy enough that it is worth pausing on whether the schedule is the right idea at all. Moving to a lifetime budget to gain a schedule means accepting a budget type that is harder to adjust mid-flight, and a learning reset on the way in.
If the hours you want to switch off carry almost no spend, you have bought that disruption for very little. Prove there is a real dead zone in your own hourly data first. The test is in what is dayparting, and the reasons Meta makes this awkward in the first place are in why Meta dayparting does not work.
The error is easy to clear. Whether you wanted the schedule is the harder question, and the one worth answering first.
If the stockout is the real problem
A recurring reason people reach for dayparting is that evening performance looks poor. Sometimes that is genuinely an hour-of-day effect. Often it is that the sizes which convert have gone by the evening, and no clock fixes an empty shelf. Worth ruling out before you rebuild budgets around a schedule: ads when stock is thin.
Clear the pacing and dayparting conflict on a Meta ad set
- Read which two settings are in conflict. The error names pacing and dayparting. So inspect exactly three fields on the ad set: the budget type, the pacing or delivery type, and whether a schedule is set. One of those three is not what you assumed, and guessing which wastes more time than checking.
- Confirm the budget is lifetime, not daily. A native schedule requires a lifetime budget, because the schedule describes how to distribute a fixed pot across a fixed period. If the ad set is on a daily budget, no pacing change will make the schedule valid and you should skip to the throttle option below.
- Set pacing to standard. Accelerated or no-pacing delivery is designed to spend as fast as the auction allows, which is fundamentally incompatible with holding budget back for particular hours. Standard pacing is what the schedule needs, and it is what almost every ad set should be on anyway.
- Apply the schedule after the other two are correct. Order matters through the API. Set the budget type and pacing first, let those persist, then write the schedule. Sending all three at once is a common way to get the same error back even though the end state would have been valid.
- Check the timezone the schedule is interpreted in. Schedules run in the ad account's timezone, which is not necessarily your store's or your own. A schedule that is silently an hour out is worse than no schedule, because it looks like it is working.
- If it must stay on a daily budget, throttle instead. Rather than a native schedule, raise and lower the daily budget on a timetable from outside the platform. Keep a floor so the ad set never drops so low that delivery collapses, and change it in steps rather than swings.
- Confirm the ad set is actually delivering to the schedule. Wait a full cycle, then check hourly delivery in the breakdown. An accepted schedule and an obeyed schedule are not the same claim, particularly on ad sets that were mid-learning when you made the change.
Questions people actually ask
What does 'pacing type incompatible with day parting' mean?
Meta is telling you that the ad set's delivery pacing and its schedule cannot both be what you have asked for. Dayparting requires the ad set to pace its budget across a defined period, which in practice means standard pacing on a lifetime budget. Accelerated or no-pacing delivery spends as fast as it can and therefore has no period to pace across, so a schedule is meaningless and Meta rejects the combination rather than silently ignoring one half.
Why do I only see this through the API or a partner tool?
Ads Manager mostly prevents the combination by hiding the scheduling control when the ad set cannot support it. The API will accept the instruction and then reject it with this error. Bulk tools and partner integrations sit on the API, which is why the error tends to appear when you are editing at scale rather than clicking through the interface.
Does switching to lifetime budget restart learning?
Changing the budget type is a significant edit and should be expected to re-enter learning. Do it deliberately, at the start of a period rather than mid-flight, and do not stack it with creative changes on the same day or you will not be able to read what caused what.
Is there any way to daypart a daily budget natively?
No, and this is the underlying constraint rather than a bug. Daily budget ad sets have no native hour-of-week schedule on Meta. The alternative is throttling: raising and lowering the daily budget on a schedule from outside, which is a different mechanism with different trade-offs.
What is Meta error #1487675?
It is the code Meta's API attaches to the message 'pacing type incompatible with day parting: this pacing requires a campaign with not day parting'. Same cause, same fix: the ad set is on accelerated or no pacing, or on a daily budget, so a schedule cannot be applied. Set a lifetime budget and standard pacing first, then add the schedule.
pacing type incompatible with day parting: this pacing requires a campaign with not day parting (#1487675)
Meta rejects a schedule on an ad set whose pacing cannot spread a budget across a period: accelerated or no pacing, or a daily budget. Set a lifetime budget and standard pacing first, then apply the schedule. If the ad set must stay on a daily budget, use a stepped budget throttle instead of a schedule.
If the hours are the problem: Ralph reads sixty days of your hourly results, proposes the switch-off with floors, and applies it on Meta after you approve. On Google he recommends the schedule. See Ralph · How Ralph dayparts · Docs