Skip to content
Knowledge Base

Why Is My Export Missing the Most Recent Data?

Last updated

If your scheduled export to BigQuery or another destination is missing the most recent day of data, the export is usually running before your data sources finish their nightly sync. Set the export's time zone to match your data sources and schedule it at least 2 hours after they sync.

Why This Happens

Two schedules decide what your export contains:

  • Your data sources' daily sync. Power My Analytics syncs each data source once a day at its sync time. By default, the sync starts at 3 AM in the data source's time zone (the time zone of the platform account you connected, or UTC), and Facebook and Instagram sources sync at 3 AM Pacific Time. A source's sync time can be changed, so check yours rather than assuming the default.
  • Your export's schedule. A Daily, Weekly, or Monthly export runs at the hour you chose, in the Timezone saved with the export. When you create an export, the Timezone starts out as the time zone of the computer you're using, so it can differ from the time zone your data sources sync in.

Your export copies the data that's available when it runs. If it runs before the nightly sync has finished, the most recent day can be missing or incomplete in your destination.

Note: Hourly exports run every hour, so a later run picks up data that finished syncing after an earlier run.

How to Fix It

  1. Check when your data sources sync. In your hub, go to Sources, click the three-dot Action menu next to a data source, and select Edit sync time to see its time zone and hour.
  2. Update your export's schedule. Go to Exports and choose your destination (for example, Exports > BigQuery). Open the export's three-dot action menu, select Edit export, and under Schedule:
    • Set the Timezone to the time zone your data sources sync in.
    • Choose an hour at least 2 hours after your data sources' sync time. For example, if your data sources sync at 3 AM Eastern Time, schedule the export for 5:00 AM Eastern Time or later. Allow extra time if the sync time falls between 3 AM and 7 AM Pacific Time, when most nightly syncs run.
    • Save your changes.
  3. Fill in the missing day. After the nightly sync has finished, open the export's three-dot action menu and select Run export now.
  4. Check your data table's date range. In Reports > Data Builder, edit the data table you export and make sure its Available Data Range is a rolling range, such as Last 30 Days, that is at least as long as your export's refresh period. See Set Up Rolling Updates.

If your data sources sync at different times, schedule the export at least 2 hours after the last of them. For example, if you export Google Ads data that syncs at 3 AM Eastern Time and Facebook Ads data that syncs at 3 AM Pacific Time, schedule the export for 5:00 AM Pacific Time or later.

If Your Time Zone Is Ahead of UTC

Rolling date ranges such as Last 30 Days are calculated in UTC (Coordinated Universal Time) at the moment your export runs. If your time zone is ahead of UTC, as in Australia, New Zealand, and much of Asia, an export that runs before midnight UTC ends its date range one day earlier than you expect, so your most recent day is left out even after the nightly sync has finished.

To include it, schedule the export for a time after midnight UTC, as well as at least 2 hours after your data sources sync. For example, midnight UTC is 11:00 AM in Sydney during daylight saving time (10:00 AM the rest of the year), so a daily export scheduled for 11:00 AM Sydney time or later includes the previous day.

Still Missing Data?

If the most recent day is still missing after your export runs on its new schedule, open the export's three-dot action menu and select View logs to check for errors. If you need more help, submit a ticket with the export's name, its destination, and the dates that are missing.

Related Articles