croissant
Home / Blog / Reporting

Agency reports and time zones: when the same date means different hours

Croissant editorial team · · 4 min read

Compare marketing reports across time zones with a clear reporting window, a worked example and a practical review checklist.

Two dashboards can show the same calendar dates while covering different hours. Before comparing or combining figures, record each source's time zone and agree the exact start and end of the reporting window. If the available data cannot be aligned, label the difference and hold calculations that require matching periods.

Define the window before comparing numbers

A client may ask for Monday through Sunday, but that phrase needs a governing time zone. Write the window as a start inclusive and an end exclusive: Monday 00:00 to the following Monday 00:00 in America/New_York, for example. An exclusive end avoids counting the boundary twice when consecutive reports meet. Record the named zone, not only a fixed offset, because local clock changes can alter the offset.

Google Ads says time-segmented reports use the account time zone. Google Analytics asks for a reporting time zone when a property is created, and warns that reports can briefly refer to the old zone after a setting change. These are separate settings; check the actual account and property rather than assuming they match. [1] [2] Changing a setting is a consequential administrative decision, not a routine reporting fix.

Worked example: a Monday starts at two different instants

This example is entirely synthetic. An agency's client wants Monday 2 November 2026 through Sunday 8 November in New York local time. Assume one advertising account reports in Los Angeles time and a second source reports in New York time. On these dates New York is UTC−05:00 and Los Angeles is UTC−08:00. Monday 00:00 New York is 05:00 UTC; Monday 00:00 Los Angeles is 08:00 UTC. The two reports labelled Monday start three hours apart.

Suppose three fictional events occur at 06:00 UTC on Monday. They fall on Monday in New York but on Sunday in Los Angeles. Monday-to-Sunday exports from the two sources therefore cover different boundary hours. The difference does not prove a tracking fault or identify how many records are missing. End boundaries differ too, and offsets should be calculated for the actual dates, including any clock change within the period.

If appropriately granular, authorized source data and its definitions permit, the reporting owner can filter both sources to the agreed instants and recompute the relevant totals. Verify that the source's time fields and filtering behavior support that operation. A daily aggregate alone cannot reveal which events belong in the overlapping hours, so do not shift or prorate a daily total as if the underlying events were evenly distributed.

Build a comparison record

For each figure record the source and account, metric definition, filters, native time zone, native start and end, extraction time, and whether the value is provisional. Beside it record the agreed reporting zone and exact boundary instants. Keep identifiers and evidence in your approved client workspace. A client-facing note can say: 'Ads uses Los Angeles account days; the website report uses New York property days. The date labels match but the hours do not.'

Choose a decision for each pair: aligned and comparable for the stated purpose; shown separately with a limitation; or held pending a more suitable export. Matching time windows is necessary for some comparisons, but it does not make different metrics equivalent. Clicks, sessions and accepted enquiries still count different things. The weekly reporting workflow covers broader metric reconciliation.

Account for freshness and changes separately

A time-zone mismatch and delayed processing are different questions. Google Analytics says processing can take 24–48 hours and figures may change during that period; its typical availability timings are not a guarantee. Record when the data was extracted, apply the team's agreed cutoff and recheck as needed. [3] Do not assume another provider has the same processing schedule.

Before changing any source setting, check the documented effects and get the responsible account owner involved. Google says a standard Google Ads account's time zone is set at creation; manager-account changes have separate restrictions. [1] A new account is a major operational choice, so investigate the reporting need and consequences before proposing one. Preserve notes on known setting changes when comparing historical periods.

Set the review and release boundary

Test the workflow with a record just before and just after each boundary, a period spanning a local clock change, and two consecutive windows. Check inclusion against the agreed instants and confirm each eligible event appears once. Also test a daily-only export: the expected outcome is a visible limitation, not a fabricated aligned total.

Let an automated workflow collect metadata, calculate supported windows and flag conflicts. A reporting owner checks source settings, filters and arithmetic; the account lead decides whether a limited comparison is useful and approves the client-facing explanation. If the report has already been issued, use the report corrections guide to preserve the issued version and review a replacement. Explore the reporting demo if you want to discuss a scoped workflow for your team.

Implementation checklist

  • Agree the client reporting zone and inclusive start and exclusive end.
  • Record each source account, metric, filters, native zone and extraction time.
  • Calculate boundary instants for the actual dates, including clock changes.
  • Confirm that available data and source rules support any requested realignment.
  • Label mismatched or provisional figures and hold unsupported calculations.
  • Test boundary events and obtain a reporting owner’s and account lead’s review.

The sources behind the sauce.

Primary research and official documentation behind the cited points. The workflow examples and checklists are Croissant’s own guidance.

  1. Google Ads Help: language, number format, time zone and currency settings
  2. Google Analytics Help: set up Analytics for a CMS-hosted website
  3. Google Analytics Help: data freshness