Provider Refresh & Retrieval Settings

days_to_refresh: The amount of data (in days) pulled back via the nightly refresh cycle

max_retrieval_days: The amount of data (in days) brought in during the first/initial retrieval (additional retrievals will stack on top of this)

📌 SQL / custom database connectors inherit the standard ~730-day default. SQL / custom database connectors (such as SQL Generic, Snowflake Share, ClickHouse, and Vertica) do not set a custom retrieval window of their own, so they fall back to the standard 730-day (2-year) default — the same default that applies to most native API providers. They are neither given a shorter limit nor a special extension; they simply inherit the default. As with all providers, the maximum retrieval window is a configurable per-provider value rather than a single universal hard-coded ceiling, so individual providers in the table below may differ.

📌 Note on Amazon Ads — data_retention_days vs. max_retrieval_days: Amazon Ads has a separate data_retention_days field that is distinct from the max_retrieval_days value (120) shown in the table above. max_retrieval_days controls how far back the initial data retrieval reaches; data_retention_days governs how long Amazon retains data on their side. These two values are independent and should not be confused with one another.