Handling time zones for analytics sounds like an easy task but having to handle multiple sources, each with their own different way of defining time, gets a bit... messy.

We try to normalize all of the data we import so it's always consistent in reports, but not all sources enable doing that.

For that reason, some of our data sets are normalized, some can be adjusted, and some can't.

Here's what you can expect:

What you have control over

• The time of the Ranks report can be set from your Profile. Changes affect both daily and hourly granularity and are applied immediately.
• The time used to send alerts can be set from your Profile.

What "just works"

• The times displayed in all store status reports is set automatically based on your current time zone (as reported by your browse).

What you don't have control over

• Apple reports its data by days so a time zone isn't really needed. Under the hood, Apple set up a cut off for a day from each region it supports which it uses to call a day. There is no way to change that in Appfigures.

  Note: If you are comparing data between Appfigures and App Store Connect make sure to select the PST option in App Store Connect as it's what the reports we import from Apple are in. They're not really in PST, but that's what Apple calls it.

• Google reports its install data using PST and Financial reports are in UTC. There is no way to change that within Appfigures at the moment.

• Amazon reports its data in UTC. There is no way to change that within Appfigures at the moment.

  Note: If you are comparing your data between Appfigures and Amazon's dashboard your data may not align because Amazon shows reports in your time zone as reported by your browser.