Data Freshness Rates and Update Times

Network Data from API-based data connectors + File-based (Google Drive & s3) data connectors

Data such as cost which is pulled from your partner ad networks and other media sources (learn more).

The freshness of the data depends on the technology used to pull the data.

To find out if a specific data connector is API-based, see the Data Connectors in Detail section.

For integrations using a different method, the Data Connectors page will display an icon indicating how Singular receives data, such as through GDrive or an Amazon s3 shared bucket.

By default data is pulled twice a day:

• The first data pull begins at midnight (customer's Singular Account time zone) and takes several hours, depending on the data load.
• The data should be ready for viewing in your reports in the morning at 8:00 a.m. in your time zone.
• A second data pull is run at 1:00 a.m. PST/PDT to add in any data that may have accumulated since the earlier pull.

Note: You can see the last update time and the next scheduled update time for each data connector in the Data Connectors page (Settings > Data Connectors).

Singular starts pulling yesterday's data first, then starts pulling data for further back. The data pull for yesterday's data may be completed earlier.

The status messages in the Data Connectors page reflect the status of the data for yesterday.

The first time you set up a data connector, it triggers an immediate data pull (doesn't wait for midnight) and pulls data 3 months back.

• For most networks, we pull data for 7 days back each time by default, to get not only the stats for yesterday but also the most up-to-date stats for the entire past week.
• For Facebook, Google, IronSource, AdAction and some other networks, we pull 30 days back.
• For Amazon Media, we pull 45 days back.

Network Data from Email-based data connectors

Integrations that are email-based will display an email icon in the Data Connectors page.

Singular processes the data immediately when we receive the email report.

Tracker Data from Singular's Attribution Tracker

Data such as installs, revenue, and post-install events, arriving from the Singular tracker (learn more).

• New data can be viewed in close to real time in user-level logs (see the Export Logs and User-Level Data FAQ). Allow 5-10 minutes for data processing.
• Data can also be viewed in real time in the Testing Console (see the Testing Console FAQ). Allow several seconds to a minute for data processing.
• New data is aggregated and pulled into the reporting system every hour, in a process that may take up to an hour. This means that the tracker data you see in aggregated reports (e.g., the Reports page or the Reporting API). is up to 2 hours old.
• Cohort data is calculated each time you run a report.

Tracker Data from Third-party attribution providers

Data such as installs, revenue, and post-install events, arriving from a third-party MMP/attribution provider.

Data from third-party trackers is pulled through data connectors, just like network/agency data. See the appropriate data connector type above.

Filled ad requests, bid requests/responses, aggregated ad revenue, and other data to help you track your ad monetization efforts (learn more).

Data is pulled twice a day:

• The first data pull begins at midnight (customer's time zone) to have the data ready in the morning. 
• A second data pull is run at 1:00 a.m. PST/PDT to add in any data that may have accumulated since the earlier pull.

If you need a higher frequency of pulls, reach out to your Customer Success Manager to discuss your options.

For details about how Singular works with specific ad monetization partners, see Ad Monetization Data Connectors in Detail.

Ad Revenue Attribution Data

Ad revenue per campaign, to help you understand your campaign ROI by looking at cost, in-app purchase revenue, and ad revenue (learn more).

The data update rates and times depend on the method you use to get ad revenue attribution data.

• If you use API or interpolation, data is updated daily and is available to you in the morning. Due to the limitations of the mediation platforms, the data you see reflects two days ago (no data for yesterday).
• If you use an SDK integration, data is received by Singular in real time. It is aggregated and pulled into the reporting system hourly, in a process that may take up to an hour. This means that data you see in the Reports page, the reporting API, etc. is up to 2 hours old.

For more information, see Ad Revenue Attribution FAQ and Troubleshooting.

SKAdNetwork Data: Facebook and Google

Install attribution data as shared by Apple's SKAdNetwork solution (learn more). Data refresh depends on the type of integration that Singular has with each SKAdNetwork-supporting partner network.

Data is pulled once a day at midnight (customer's time zone) to have the data ready in the morning.

For more information, see Facebook Ads SKAdNetwork Integration and Google Ads SKAdNetwork Integration.

5 days back

SKAdNetwork Data: Twitter

Data is pulled once a day at noon (customer's time zone) and is ready at 3 p.m. For more information, see Twitter SKAdNetwork Integration.

1 day back

SKAdNetwork Data: Other networks

• For networks with postback-based integrations, postbacks are processed by Singular in real time and you can view the data after 5-10 minutes through the Export Logs page (see the Export Logs and User-Level Data FAQ).
• Data is aggregated and pulled into the reporting system hourly, in a process that may take up to an hour. This means that data you see in the SKAN reporting pages or the reporting API is up to 2 hours old.

Data Destinations (Aggregate Data Schemas)

If you use the data destinations feature, Singular automatically exports your data to a data warehouse or third-party platform of your choice (learn more).

Data is pushed to the data destination every 6 hours. The actual freshness of the data you see in your data destination depends on when Singular originally pulled it from the source (the data connector and/or tracker). In some data schemas, you can see exactly how fresh the data is by looking at the data_connector_timestamp_utc field.

Data Destinations (User-Level Data Schemas)

Data is pushed to the data destination hourly. The freshness of the data you see in your data destination depends on when it was pulled from the tracker. 

You can expect 95% of events to be exported to your system within 3 hours after they occurred. A small minority of events may take a longer time to be processed and exported.