How often does DataDoe fetch data?
There are three ways DataDoe fetches data:
- Fetch periods: Each morning, DataDoe pulls data according to the fetch period set for each table. Some tables also have intraday fetches for lower latency data.
- Real-time: DataDoe receives data in real time and makes it available to users as soon as possible.
- Continuous fetch: DataDoe detects changes in Amazon and updates the data accordingly.
What should I do if my data is not updated on time?
If your data is not updated on time, please contact us (opens in a new tab).
What time does the daily fetch happen?
The daily fetch starts every day at 2am in the local time zone of each Seller or Vendor. The first data is typically available by 3am, and 95% of the data is available by 5am.
Each table's fetch period defines when DataDoe refreshes it. You can check each table's refresh schedule in the interactive Data Scheme.
What is continuous fetch?
Continuously fetched data is updated automatically whenever DataDoe detects changes in Amazon.
Which tables have intraday updates?
The following tables receive intraday updates through scheduled fetches or continuous polling. These updates refresh data that changes during the day.
| Raw Data Source | Data Tables Affected | Real-time update | Refresh at |
|---|---|---|---|
raw_sp_api_report_orders | Order Line Items | Orders are available up to 1 hour after being placed. | 2am, 8am, 10am, 1pm, 4pm, 7pm |
refined_sp_api_finances_transactions | Settlements & P&L Components | No | 2am, 10am, 4pm |
raw_sp_api_vendor_purchase_orders | Vendor Purchase Orders | No | Every 2 hours |
raw_sp_api_orders_details_pii | Order Details PII | Data is available up to 1 hour after the order is fetched. | - |
raw_sp_api_report_listings_data | Listings | No | 2am, 10am, 1pm, 4pm |
raw_ads_api_report_advertised_products_sd raw_ads_api_report_advertised_products_sp raw_ads_api_report_purchased_products_sb | Ads Performance by ASIN & Date | No | 2am, 8am, 1pm, 4pm |
raw_ads_api_report_legacy_campaign_sb_all raw_ads_api_report_campaign_sd raw_ads_api_report_campaign_sp raw_ads_api_report_campaign_st | Ads Performance by Campaign & Date | No | 2am, 8am, 1pm, 4pm |
raw_sp_api_report_fba_inventory_planning | FBA Inventory Health, Listings | No | 2am, 10am, 1pm, 4pm |
raw_sp_api_report_restock_inventory | FBA Restock Recommendations, FBA Inventory Health | No | 2am, 1pm |
raw_sp_api_report_v2_seller_performance | Seller Account Health Metrics | No | 2am, 1pm |
raw_sp_api_report_myi_all_inventory_data | none | No | 2am, 1pm |
Ads Performance by Campaign & Date and Ads Performance by ASIN & Date fetch data at 2am, 8am, 1pm and 4pm in the marketplace time zone. The daily fetch rereads 21 days; each intraday fetch rereads 5 days. This includes Sponsored Brands. Data becomes available after processing, and Amazon can revise it in later reports. These schedules do not confirm that a day is complete or final. Sponsored Brands ASIN estimates can also lag the source reports.
Settlements & P&L Components fetches start at 2am, 10am and 4pm, including weekends. The 2am fetch rereads 8 days. The 10am and 4pm fetches reread 2 days, including the current day. US and Canada use Pacific time (America/Los_Angeles) for the 10am and 4pm fetches, including daylight saving. Other marketplaces use their local time zone. Amazon may leave out orders from the last 48 hours. These times are when the fetch starts. Rows appear after Amazon publishes them and after DataDoe finishes processing and export.
Vendor Purchase Orders are checked for new and changed orders every 2 hours. Orders appear after Amazon makes them available and DataDoe completes sync and export processing.
What real-time data does DataDoe have?
DataDoe receives near real-time data from Amazon Marketing Stream (AMS) and Seller Central/Vendor Central SP-API Notifications. These are available as integrated Data Scheme tables (continuous fetch, disabled by default).
Can DataDoe send webhooks for real-time data?
Yes, for SP-API Notifications. Amazon Marketing Stream (AMS) data is not available as webhooks. See Webhooks for details.
SP-API Notifications
Vendor Central supports these notifications: Detail Page Traffic Event, Item Inventory Event Change, Item Sales Event Change, Listings Item Issues Change, and Shipment Tracking Milestone Changed. In Settings > Data and in the Data Scheme, they appear under both Seller Central and Vendor Central. Each table has one ON/OFF state and one retention setting for your Organization, so a change on one tab also applies to the other. Shipment Tracking Milestone Changed also requires the AMAZON_SHIPMENT_TRACKING_SUBSCRIBE Action for each tracking identifier.
Amazon Marketing Stream (AMS)
| Data Table | Data Latency |
|---|---|
| AMS Campaigns | less than 1 hour |
| AMS Campaign Ad Groups | less than 1 hour |
| AMS Campaign Ads | less than 1 hour |
| AMS Budget Usage | less than 1 hour |
| AMS Campaign Diagnostics | less than 1 hour |
| AMS Campaign Targets | less than 1 hour |
| AMS Traffic | less than 1 hour |
| AMS Conversion | less than 1 hour |
| AMS SB Clickstream | less than 1 hour |
| AMS SB Rich Media | less than 1 hour |
| AMS SP Budget Recommendations | less than 1 hour |
AMS data is not available as webhooks.
Data Latency counts from when Amazon sends a message to DataDoe. These tables usually reach BigQuery in less than 1 hour. AMS Budget Usage usually reaches BigQuery about 30 minutes after Amazon sends a reading. It keeps the latest reading Amazon has sent for each campaign, and Amazon decides when to send a new one, so it does not match the ads console minute by minute.
AMS Traffic and AMS Conversion use hourly totals. Amazon sends the first rows for an hour about 1 to 2 hours after the hour starts and keeps sending corrections for that hour later. Each row adds to the hour's totals, so sum the rows instead of taking the latest one.

