Skip to content

Date Range

Date Range is the parameter that defines the time period for which the report pulls data. Fixed presets, relative periods, and a custom range are all supported.

Available presets

today

Data for the current day. If run at 14:00, you get data from 00:00 to 14:00 of the current day (or up to the latest available data point).

yesterday

Data for the previous full day. A stable option for daily reporting — data doesn't change during the day.

last_7d

Data for the last 7 days, including today. If run on July 15, you get data from July 9 to July 15.

last_30d

Data for the last 30 days, including today. The standard option for monthly reporting.

this_month

Data from the first day of the current month through today. Useful for progress reports throughout the month.

last_month

Data for the full previous month. If run in July, you get data for June. A stable option for closed periods.

custom

A fixed range with specified start and end dates. Suits one-off analytical tasks.

Step-by-step instructions

1. Choose a preset

In the builder, open the Data > Date Range section. Choose the appropriate preset from the dropdown list.

2. Configure custom (if needed)

When choosing custom, specify:

  • Start date — inclusive
  • End date — inclusive

Dates are set in YYYY-MM-DD format.

3. Account for timezone

The system uses the data source's timezone, not the workspace's. For example:

  • Google Ads uses the ad account's timezone
  • Facebook Ads — UTC-8 (Pacific Time)

This matters: yesterday in a source with a UTC+3 timezone arrives 3 hours earlier than in UTC+0.

4. Account for data delay

Most advertising platforms update data with a delay:

  • Google Ads — 3 hours
  • Facebook Ads — from a few hours up to 48 hours

Using today in the morning hours may return incomplete data.

Start-date behavior on repeated runs

For relative presets (today, yesterday, last_7d, last_30d, this_month, last_month), dates are recalculated on every report run.

For custom, the dates are fixed. On repeated runs, data is pulled for the same fixed period.

How to verify

  • Run the report and check the dates in the output data
  • Compare the row count against expectations (1 row per day for daily reports)
  • Check that data exists for every day in the range (empty days should be reflected)

Recommendations

  • For daily reports — yesterday
  • For weekly reports — last_7d
  • For monthly reports — last_month
  • For real-time monitoring — today (accounting for data delay)
  • For one-off exports — custom
  • Filters — additional filtering by date
  • Schedule — automatic runs tied to the date range
  • Timezone — how timezone affects scheduling

Maintained by the LightLead Documentation Team · Last verified: 2026-07-25