Our Attribution Analytics SDK tries to mitigate this issue by queuing the network request and trying it up to 5 times when the device connects.

Users may download the app, but only run it when they don't have network access.(Apples reports vary by reason and fiscal time frames.) Users may download the app, but run it on a different day.Users may download the app, but may not run it or may run it after a look-back period expires from the click.However, please note that Installations are only reported based on opt-in in App Analytics, so they will always appear lower in App Analytics when compared to another service. This is indeed the measure closest to what developers track through other third parties, as it is counted upon app open, and includes re-downloads.For CET, set your user timezone to CET and generate a similar report for the territory, etc. Now you can compare these install numbers to iTunes Connect reports for these territories. Then generate a report in the platform for US, Canada, and Latin America. When you change the timezone setting, you must logout and log back in for the timezone change to take effect for your Attribution Analytics reports. For PST, first set your user timezone to PST if it is not already. In order to reconcile platform reports with iTunes Connect reports, you must reconcile territory by territory. As such, reports are generally available by 8:00 AM PST for the previous day. Reports are generated after the close of business in the final time zone (which is PST). Australia, New Zealand: Western Standard Time (WST).Europe, Middle East, Africa, Asia Pacific: Central Europe Time (CET).US, Canada, Latin America: Pacific Standard Time (PST).

iTunes Connect reports uses the following: While the Attribution Analytics platform reports all installs using the account or user timezone, iTunes has different timezone for reporting.

ITunes Connect reports operate in different timezones for different territories.

Play store itunes