Time Zones in Reporting
This page has been deprecated and the content will not be refreshed as of February 2013.
When you create a report request, specify the date range time period based on the time zone of the campaign. If the report request spans multiple campaigns, the report will include the report data in the time zone of each respective campaign (the data is not reported in the local time zone of the user that clicked the data). If the report request spans multiple accounts (for example, an account performance report), the service selects one of the campaigns at random from each of the accounts and uses that campaign's time zone. Because the selection of the campaign time zone is random, you should not rely on the time zone being accurate for these types of reports.
The report data is stored in the time zone of the campaign (taking into account daylight saving time for those time zones that support daylight saving time). For example, if the time zone of the campaign is Pacific Time and a click occurs at noon Eastern Time, the time of the click is recorded as 9:00 AM. If you request a report for the campaign using hourly aggregation, the report data will include a click that occurred at 9:00 AM (the report data is not adjusted based on the local time zone of the user). If your report request specifies multiple campaigns in different time zones, the clicks that occurred in each campaign are summed for each hour relative to their respective time zones.
Note that when a user clicks an ad, it can take up to four hours for the system to process the click and make it available for reporting. If you schedule a report that requires the previous full day of data, you should consider the three-to-four hour rolling window and the time zone of the campaign before making your request. For example, if the time zone of the campaign is set to Pacific Time (UTC-08:00), consider running the report at 5:00 AM Pacific Time (four hours for the rolling window plus a one-hour buffer).