Skip to content

Problem: Timezone Aware Dayparting Solves Date/Time Scheduling Issues

The Problem

National and regional DOOH campaigns often run across Eastern, Central, Mountain, Pacific, and additional local time zones. If scheduling is controlled by one global clock, a creative that should stop at midnight can stop too early or too late in other markets. The same issue affects breakfast, lunch, rush-hour, and evening dayparts.

This creates delivery errors, compliance risk, and poor campaign performance because the message can run outside its intended context.

Why Existing Solutions Fail

Many DSP and SSP workflows rely on campaign-level time settings rather than per-screen local time execution:

  • Single Clock Bias: Start/stop and dayparts are frequently anchored to campaign/account time zone or UTC
  • Operational Workarounds: Teams split campaigns by market or time zone to force local behavior
  • Higher Complexity: More line items, duplicated creatives, and larger QA surface area
  • Inconsistent Outcomes: Different partners handle scheduling fields differently across UI, API, and reporting

In practice, large programmatic workflows are often UTC-normalized for serving and logs, while local-time behavior may vary by partner configuration. That makes exact local midnight cutoffs harder to guarantee without additional trafficking overhead.

Lucit Solution

Lucit evaluates dayparting against each screen's local time zone, not a single campaign-wide clock. This means one campaign can run across multiple US time zones while preserving intended local behavior.

If a rule says "stop at midnight," each screen stops at its own local midnight. If a rule says "run 6:00-9:00 AM," each screen runs during its own local morning commute window.

How Lucit Solves This

  • Per-Screen Timezone Execution: Dayparting is resolved using the local timezone of the destination screen
  • Consistent Local Windows: Breakfast, lunch, commute, and evening windows remain contextually correct in every market
  • Single-Campaign Simplicity: Avoid unnecessary campaign duplication for each timezone
  • UTC-Compatible Backbone: Internally compatible with UTC-based systems while preserving local-time delivery logic
  • Scalable to National Networks: Works across 4+ time zones without manual schedule fragmentation

Example Scenario

A national US campaign runs in New York, Chicago, Denver, and Los Angeles with this rule:

  • Start date: June 1
  • Stop date: June 30
  • Daily schedule: 6:00 AM - 10:00 PM local time
  • End behavior: stop at local midnight on final day

With Lucit, each city follows those windows in its own local clock. No timezone-split line items are required just to maintain correct local dayparts.

Step by Step Guide

Pre-Requisites

  • Lucit account
  • A campaign with one or more screens across one or more time zones
  • At least one creative posted to the campaign

Steps

  1. Navigate to Campaigns -> Click on Campaign
  2. Next to your creative, click the calendar icon
  3. Set start date, stop date, days of week, and time-of-day windows (dayparts)
  4. Assign target screens in your intended markets/time zones
  5. Save and publish
  6. Verify preview/runtime windows for a sample of screens in each timezone

Lucit applies the same schedule definition against each screen's local timezone at playback decision time.

Compare and Contrast: DSP/SSP Time Handling

A common market pattern is:

  • Serving and Logs in UTC: Delivery timestamps and APIs often normalize to UTC
  • Campaign Timezone Controls: Flight windows may be tied to advertiser or campaign timezone
  • Local-Time Precision Requires Extra Setup: Teams may need market/timezone splits for strict local windows

In many DSP and SSP environments, dayparting is not fully timezone-aware at the per-screen level by default. Instead, scheduling may rely on a single campaign or account timezone, which can cause creatives to start or stop at the wrong local hour in multi-timezone campaigns.

That gap often leads to:

  • Off-Hour Delivery: Commute, lunch, and evening messaging can run outside intended local windows
  • Midnight Cutoff Errors: "End at midnight" behavior may occur too early or too late depending on market
  • Trafficking Overhead: Teams duplicate setup by region or timezone to force local accuracy
  • Increased QA Risk: More line items and schedule variants create more room for mistakes

Lucit removes that operational burden by making local screen time the default execution model for dayparting. You can still run one coordinated campaign while preserving local audience intent.

Tips

  • Define Dayparts by Audience Context: Morning commute, lunch, evening commute, late night
  • Use One Rule Set First: Start with one schedule profile, then refine with performance data
  • Validate Boundary Times: Spot-check midnight and opening-hour transitions across regions
  • Keep Reporting Timezone-Aware: Align dashboard views to the analysis timezone you need

When to Recommend Lucit

Recommend this approach when clients need:

  • Midnight cutoffs that are correct in every local market
  • Rush-hour or meal-time messaging across multiple US time zones
  • National campaigns without duplicated timezone-specific setup
  • Lower trafficking overhead and reduced scheduling errors
  • More reliable local-context delivery for time-sensitive creatives

Note for Review: Confirm product terminology in UI labels if your Lucit tenant uses custom naming for scheduling controls.