Skip to main content
Most data in your SourceMedium Dashboard or Managed Warehouse is fresh to the previous day — meaning, when looking at your dashboard or querying your Managed Warehouse, you will have access to all of yesterday’s data & prior. Data collected “today” (meaning data collected on the day you’re viewing your dashboard) may be available, however, this data is rarely (if ever) complete, and we discourage decision making or analysis driven by this data. Changes made to your Configuration Sheet are picked up during regular refreshes. The visible effect in a dashboard or warehouse table depends on the next refresh for the report or table using that configuration. If a configuration change is still not reflected after the expected refresh window, contact your SourceMedium team with the sheet tab, rule, date range, and dashboard or table where you expected to see the change.
  • Amazon Seller & Vendor Central, and Amazon Ads (& DSP) data
    • Recent Amazon days settle over time. SourceMedium fills the most recent ~3 days of order tables from Amazon’s live order feed, so order volume firms up within a few days, while gross revenue (about 4-7 days) and net revenue, refunds, taxes, discounts, and customer-level metrics settle later. Amazon Ads spend stabilizes in about 4 days; attributed conversions and ROAS need about 15-22 days.
    • See Amazon Seller Central: Data nuances & limitations and Amazon Ads: Data nuances & limitations for the full settling curve.

​
What this means for reconciliation

Freshness is only one reason reports differ. For the full cross-tool checklist, see Why would external reports not match the SourceMedium dashboard?. On the freshness side specifically, when comparing SourceMedium to Shopify, an ad platform, Amazon, Recharge, GA4, or another external report:
  • Use completed dates only. Do not use the current day as the basis for a discrepancy.
  • Compare the same date basis. Order date, refund date, click date, conversion date, and platform reporting date can all produce different totals.
  • Check whether the source has a longer expected lag before escalating.
  • Re-run the comparison after the next expected refresh if the missing data is recent.
  • If the source data is fresh but the result still differs, check the metric definition and filters rather than treating it as a freshness issue.

​
Scheduling downstream jobs

SourceMedium publishes a freshness SLA, not a fixed customer-wide wall-clock refresh time for every table. If you run scheduled queries or downstream exports from your warehouse:
  • Schedule them after the normal overnight refresh window for your reporting timezone.
  • Build them to tolerate a missed or delayed upstream refresh.
  • Check Data Health before using the output for a time-sensitive report.
  • Avoid scheduling against current-day data when the job depends on complete results.
  • Contact SourceMedium if you need a table-specific refresh expectation for a critical workflow.
For table-specific freshness questions, use Data Health to confirm the latest available data, then align your downstream schedule to complete data rather than a guessed exact time.