For the complete documentation index, see llms.txt. This page is also available as Markdown.

Understanding reporting data delays and time zones in the new interface

Real-time reporting is here! Metrics shown on the Performance, Keywords and Products report will now display data as recent as 1 hour ago. All data is shown based on the retailer's configured time zone (e.g. Brisbane, Australia – AEST, UTC +10).

How recent is the performance data?

Most of the reporting data in the new interface is currently updated every hour. The last updated time stamp is also displayed above every report showing the exact time when the report was last updated. The Onsite Campaign Performance report, Keywords, Products report and Campaign report has hourly refreshed performance data.

Note that the Match Type, Wallet Balance & History, Enhanced Metrics and Offsite dashboard will continue to get updated once a day. Data may appear 12–36 hours behind your local time.

What time zone is used in reports?

All reporting data is displayed in the time zone configured by the retailer. This is set at the retailer account level and cannot be changed by users.

Because of this:

  • You may see data that looks out of sync with your local time.

  • If you work across multiple retailers, keep in mind that each one may have a different time zone, which affects how daily performance is calculated and displayed.

  • For example, if you're located in New York and viewing data for a retailer set to Brisbane time, the “day” used in reporting may not match your local day exactly.

We display the retailer’s time zone clearly in the interface to help you interpret performance consistently and correctly.

Recent changes to the legacy interface

To improve consistency between the legacy and new interfaces, we’ve recently updated the legacy interface to use the same retailer-specific time zone logic.

  • Previously, the legacy interface aligned to your local browser time zone, which may differ from the retailer's configured time zone.

  • In the most recent update, the legacy interface now uses the retailer’s time zone for reporting, with a delay of approximately 1 hour (this is the same as the new interface).

  • This change helps reduce discrepancies between the two platforms when comparing campaign performance.

Examples of Retailer Time Zones

Below are common retailer timezones.

Retailer

Time Zone

Offset

Retailer A (Australia)

Brisbane – Australian Eastern Standard Time (AEST)

UTC +10

Retailer B (USA)

New York – Eastern Time (ET)

UTC -5 / -4 (Daylight Saving)

Retailer C (UK)

London – Greenwich Mean Time (GMT) / British Summer Time (BST)

UTC 0 / +1

Retailer D (Germany)

Berlin – Central European Time (CET) / Central European Summer Time (CEST)

UTC +1 / +2

Retailer E (Japan)

Tokyo – Japan Standard Time (JST)

UTC +9

Note: All data in the UI will align to the time zone of the retailer you are viewing. This time zone cannot be changed by users.

Common Questions

I am seeing discrepancies in data between the legacy and new UI.

There shouldn't be any discrepancies between the two interfaces. Please raise a ticket with our support team who can investigate further.

Can I change the reporting time zone?

No. The reporting time zone is fixed based on the retailer you’re viewing and cannot be changed by users. This ensures consistency across all users within the same retailer account.

When will real-time reporting be available again?

It's available now! Metrics shown on the Performance, Keywords and Products report will now display data as recent as 1 hour ago. All data is shown based on the retailer's configured time zone (e.g. Brisbane, Australia – AEST, UTC +10).

Note that the Match Type, Wallet Balance & History, Enhanced Metrics and Offsite dashboard will continue to get updated once a day. Data may appear 12–36 hours behind your local time.

Last updated