Schedule Amazon bids by the hour.
Spend rises during peak conversion windows and drops during slow hours, across 168 slots a week for every ASIN.
- Slots per week
- 168
- Bid granularity
- 24h
- Marketplaces
- 8
Slots per week
Bid granularity
Marketplaces
The 24-hour bid curve, shaped around your buyers.
A flat bid pays peak-window prices for 3am traffic. Day-parting spends the same budget where the orders actually happen, and pulls back where the clicks never convert.
- Hourly multipliers derived from your own order data, not category averages
- Budget caps that stop slow hours from draining the day before the evening peak
- A weekly refit, so the curve keeps matching the account as it changes
- 168
- Schedulable slots per week
- -43%
- Typical slow-hour spend
- +19%
- ROAS lift over 30 days
- 8
- Marketplaces supported
Four passes from raw hours to a live schedule.
The profile is rebuilt on a weekly cadence, so the curve tracks the account rather than the week it was created.
Profile your week
Thirty to ninety days of hourly order data per ASIN, per marketplace, in the buyer's local time.
Find the windows
Peaks, shoulder periods, and the hours that reliably produce clicks without orders.
Schedule the spend
Bid multipliers and budget caps applied to each of the 168 weekly slots.
Refit every week
The schedule follows seasonality, lifecycle, and competitive shifts instead of freezing on launch day.
Full week, all 168 slots
Same budget, different hours.
The comparison that matters is not spend against spend. It is what each hour of that spend is worth when the buyer is actually shopping.
| Flat bidding | Day-parted bidding | |
|---|---|---|
| Overnight hours | Full bid, minimal orders | Reduced bid or paused entirely |
| Peak window | Same bid as 3am | Bid raised while intent is high |
| Budget exhaustion | Often spent before evening peak | Reserved for converting hours |
| Weekend behaviour | Identical to weekdays | Separate curve, shifted later |
| Adaptation | Manual, when someone notices | Weekly refit on live data |
Controls
- Hourly granularity
- Buyer-timezone aware
- Per-ASIN profiles
- Weekly auto-refit
- Event boost mode
- Manual overrides
- Budget caps per slot
- Marketplace-specific schedules
Before you schedule a single hour.
Does day-parting just reduce my spend?
No. It moves the same budget to better hours. Slow-hour spend comes down, peak-window spend goes up, and the net effect shows in ROAS rather than in a smaller invoice.
What if my category does not have obvious peaks?
Then the schedule stays close to flat, and the system says so. A profile is only applied where the hourly conversion difference clears a confidence threshold on your own data.
How does this work across marketplaces?
Each marketplace gets its own schedule in the buyer's local time, so a DE and a US campaign for the same ASIN can run opposite curves without fighting each other.
Can I override a slot?
Yes. Any slot can be pinned manually, and a manual override survives the weekly refit until you remove it. Overrides are written to the decision ledger like any other change.