A paid media dayparting analysis can show whether performance changes by weekday or hour are strong enough to justify higher bids, lower bids, or scheduled pauses. This guide provides a spreadsheet-ready template, comparison points for Google Ads, Microsoft Ads, and Meta Ads, and a repeatable process for making scheduling decisions without mistaking short-term noise for a durable pattern.
Overview
Dayparting, also called ad scheduling, is the practice of comparing campaign performance across time blocks and adjusting delivery accordingly. The goal is not to find a universally “best” hour. It is to determine whether a particular period produces enough incremental value, at an acceptable cost, to deserve a different share of budget.
For search campaigns, the analysis may lead to schedule bid adjustments, separate campaigns, or a decision to let automated bidding operate without manual intervention. For paid social, the available controls and reporting dimensions may differ by campaign type, objective, account setup, and interface version. In some cases, the practical choice is to adjust budgets or use an experiment rather than apply an hour-by-hour rule.
Use dayparting as a budgeting and bid strategy decision, not as a dashboard exercise. A time block should be changed only when its performance is meaningfully different, the data is sufficiently reliable, and the change fits the campaign’s conversion window and business operations.
Platform comparison
| Platform | Scheduling or delivery controls to review | Useful reporting dimensions | Practical caution |
|---|---|---|---|
| Google Ads | Campaign ad schedule, day and time ranges, and any available bid adjustment settings | Day of week, hour of day, date, cost, clicks, conversions, conversion value, and impression share where relevant | Check the campaign’s time zone and whether automated bidding makes a manual adjustment appropriate. |
| Microsoft Ads | Campaign or ad-group scheduling controls and bid adjustment settings available in the account | Day, hour, spend, clicks, conversions, revenue or conversion value, and other selected performance columns | Do not assume an imported Google Ads schedule or column definition behaves identically. |
| Meta Ads | Campaign or ad-set budget and scheduling options available for the selected buying setup | Breakdowns by day and time, delivery, spend, results, cost per result, and value where tracked | Confirm that the selected breakdown is available for the campaign and that the data is comparable across the analysis period. |
Platform controls, column names, attribution settings, and automated delivery behavior can change. Treat this table as a planning guide and verify the current interface before implementation.
How to estimate
Build the analysis in a spreadsheet with one row for each time block. Start with a consistent block structure, such as Monday 00:00–05:59, Monday 06:00–11:59, and so on, or use one-hour rows if volume supports that level of detail. A four-hour or six-hour grouping is often easier to interpret for smaller accounts.
Use these columns:
- Time block: weekday, start time, end time, and account time zone.
- Impressions and clicks: useful for understanding delivery and traffic volume.
- Spend: the amount attributed to the block in the platform report.
- Conversions and conversion value: use one clearly defined conversion action or a consistent conversion set.
- CTR and conversion rate: clicks divided by impressions, and conversions divided by clicks.
- CPC and CPA: spend divided by clicks, and spend divided by conversions.
- ROAS: conversion value divided by spend, when value tracking is appropriate.
- Share of total: block spend divided by total spend, and block conversions divided by total conversions.
- Decision: increase, maintain, decrease, pause for testing, or collect more data.
Core formulas are simple:
- CPA = spend ÷ conversions
- ROAS = conversion value ÷ spend
- Conversion rate = conversions ÷ clicks
- Relative CPA index = time-block CPA ÷ account CPA
- Relative ROAS index = time-block ROAS ÷ account ROAS
For a first pass, compare each block with the campaign or account baseline from the same reporting period. A block with a lower CPA than the baseline may deserve more exposure, but only if it has adequate conversions and is not simply benefiting from a small sample. A high ROAS block can also be misleading when it contains very few purchases or unusually large orders.
To estimate the effect of a schedule change, calculate the block’s average daily spend and expected change in delivery. For example, if a time block receives $40 per day and a proposed adjustment is expected to reduce exposure by 25%, the rough daily spend at risk is $10. This is not a forecast of conversions; it is a way to understand the budget being moved before applying the change.
Inputs and assumptions
Time-zone normalization is the first control. Platform reports normally use the account, campaign, or reporting time zone rather than the analyst’s local time. Record the reporting time zone in the spreadsheet, convert imported data only once, and avoid combining campaigns with different time zones in the same comparison without labeling them.
Next, define the conversion window. A click late in the evening may convert the following day, so same-hour platform reporting can understate the eventual value of later time blocks. If the account has a material conversion lag, wait for the chosen window to mature or compare time blocks using a lag-adjusted reporting period. Keep the attribution model and primary conversion actions consistent throughout the test.
Set a minimum evidence rule before looking at results. The rule can be based on conversions, clicks, spend, or a combination. For example, an internal rule might require at least 20 conversions per time block before considering a strong schedule change, while smaller blocks are labeled “directional.” The number is an assumption, not a universal benchmark; choose a threshold that reflects account volume and the cost of being wrong.
Also record external factors that can distort a time pattern: promotions, holidays, paydays, stock availability, sales-team hours, tracking outages, landing page changes, and major creative or keyword changes. A block should not be paused because of a single unusually weak weekend during a site outage.
For the spreadsheet, create an assumptions area containing:
- Reporting period and platform time zone
- Conversion definition and attribution setting
- Expected conversion lag
- Minimum conversion or spend threshold
- Target CPA or target ROAS, if one is used
- Allowed schedule change, such as a maximum bid or budget movement per test
- Review date and owner for the next decision
Worked examples
Assume a campaign has a target CPA of $50 and an overall period result of $2,000 spend, 40 conversions, and a $50 CPA. The Tuesday 08:00–12:00 block produced $360 spend and 10 conversions, giving it a $36 CPA. Its relative CPA index is 0.72, meaning its CPA is 72% of the campaign baseline. That is a useful signal, but the block represents only 10 conversions and may still require another reporting cycle before a large increase.
Now assume Friday 20:00–24:00 spent $300 and produced four conversions. Its CPA is $75, or 1.5 times the $50 baseline. If the result appears in several mature periods and the block is not strategically important, a modest reduction or controlled pause could be reasonable. If it occurred during a one-off event, check the context before changing the schedule.
For ROAS, suppose a campaign spent $1,200 and recorded $3,600 in conversion value, producing 3.0 ROAS. A Wednesday afternoon block spent $240 and generated $960 in value, producing 4.0 ROAS. The block is efficient relative to the baseline, but increasing bids may not create more eligible demand. Check impression share, reach, frequency, auction pressure, and the platform’s delivery model before assuming that efficiency can be scaled.
Apply changes gradually. A practical test might alter only the clearest high-volume block, preserve a comparison period, and log the change date. Avoid changing schedules, budgets, bidding targets, landing pages, and creative at the same time. Use the PPC Account Change Log Template to record the hypothesis, expected effect, implementation date, and rollback condition.
When several campaigns target the same audience, evaluate the pattern at both campaign and account level. A schedule that looks weak in one campaign may be important for another. For budget decisions across campaigns, pair the findings with the marginal ROAS budget reallocation framework rather than relying only on average ROAS.
When to recalculate
Revisit the analysis monthly for active campaigns and at least quarterly for stable programs. Recalculate sooner after a major budget change, a new bidding strategy, a conversion-tracking update, a different landing page, a significant audience or keyword change, or a shift in business hours. Recheck time zones and reporting-column definitions whenever a platform interface or account structure changes.
At each review, import a fresh period, let recent conversions mature, compare the result with the previous period, and mark each block as stable, improving, declining, or inconclusive. Validate whether earlier schedule changes produced the intended result before making another adjustment. If a pattern disappears after controls are applied, return the block to the default schedule and continue monitoring.
Keep a simple next-test plan: one hypothesis, one change, a minimum observation period, a primary metric, and a rollback rule. For example: “If Wednesday 08:00–12:00 remains below the target CPA after the next mature period, increase exposure modestly; if CPA exceeds the target by the agreed tolerance, restore the prior setting.” This makes dayparting analysis a repeatable part of campaign optimization rather than a reaction to the latest dashboard fluctuation.
Finally, reconcile platform results with analytics and business records before making a large budget move. The Paid Media Attribution Reconciliation workflow can help explain differences between platform-reported conversions and broader reporting. Once the data is aligned, use the PPC Budget Pacing Template to check that any schedule change still supports the month’s delivery plan.