Autopilot Module • Dayparting by Products

Set hourly schedules at the product level, one rule controls all its campaigns.

Prefer to think in products, not campaigns? With Dayparting by Products, AiHello pauses and resumes every campaign tied to a product (SP/SB/SD) according to a single, product‑centric schedule. It’s the fastest way to align budgets with buyer behavior when a SKU runs across multiple structures. For many goals, product‑level dayparting is recommended over campaign‑level scheduling.

Coverage
All linked campaigns
Time basis
Marketplace TZ
Granularity
Hourly • Weekly
Repricer Overview Screenshot

Why product‑level dayparting?

One rule, many campaigns

Switch OFF/ON all campaigns for a product at once with no more duplicate schedules per campaign.

Goal‑aligned control

Perfect when your objective (profit, inventory, seasonality) is best enforced per SKU rather than per campaign.

Cleaner budgets

Eliminates leakage where one campaign keeps spending in a low‑value window while others are paused.

How it works

1
Select products (SKU / ASIN)

Choose one or more products. Optionally group variants or related items to share a schedule.

2
Pick covered campaigns

Apply to all linked campaigns (SP/SB/SD) or select a subset. The schedule cascades automatically.

3
Review product‑hour performance

Use the product view to compare conversion rate, weighted conversion rate, CTR, sales, and clicks by hour and weekday.

4
Build the schedule

Click‑drag to mark OFF windows (e.g., 01:00–06:00). Add exceptions for specific campaigns if needed.

5
Activate & monitor

AiHello will pause/resume all selected campaigns for the product automatically. Revisit monthly or around seasonality.

UI overview

Everything you need to make smart scheduling calls in one place, centered on the product.

Product selector

Search by SKU/ASIN. Bulk‑select related items to mirror schedules.

Metric heatmap

Hourly/weekday heatmap showing CR, weighted CR, CTR, sales, and clicks for the product.

Campaign coverage

Toggle which campaigns will inherit the schedule. Great for excluding awareness layers.

Conflict rules

Product‑level OFF overrides campaign‑level ON by default. You can create explicit exceptions.

Repricer Overview Screenshot
Screenshot: Coverage toggles

Example product heatmap (placeholder)

Product / Weekday
00–04
04–08
08–12
12–16
16–20
20–24
SKU‑123 Mon
Low
Low
Med
High
High
Med
SKU‑123 Tue
Low
Med
Med
High
High
Med
SKU‑123 Wed
Low
Low
Med
High
High
Med
SKU‑123 Thu
Low
Low
Med
High
High
Med
SKU‑123 Fri
Low
Low
Med
High
High
High
SKU‑123 Sat
Low
Low
Med
Med
High
High
SKU‑123 Sun
Low
Low
Med
Med
High
Med

Replace with your actual product‑level chart screenshot. Recommended 16:9 aspect.

Best practices

Use when a SKU spans layers

If a product runs across SP/SB/SD, product‑level scheduling keeps every layer in sync.

Start broad, then refine

Begin with clear ON blocks and a single OFF window (e.g., 01:00–06:00). Tighten once data confirms.

Mind inventory & price

Big price or stock changes can shift peak hours. Re‑evaluate schedules after changes.

See it in action

Repricer Overview Screenshot

Add captions under screenshots to call out decisions (e.g., OFF 01:00–06:00 Mon–Sun).