Last updated: March 18, 2026
Transfer Schedules
Every transfer runs on a schedule you define. Detrics supports a range of frequencies from hourly to monthly.
Available Frequencies
| Frequency | Behavior |
|---|
| Every hour | Runs once per hour, every hour |
| Every 2 hours | Runs every 2 hours |
| Every 3 hours | Runs every 3 hours |
| Every 6 hours | Runs every 6 hours |
| Every 12 hours | Runs every 12 hours |
| Daily | Runs once per day at your chosen hour |
| Weekly | Runs once per week on your chosen day and hour |
| Monthly | Runs once per month on your chosen day and hour |
Timezone Handling
Schedules are interpreted in the timezone set on the destination. If your destination’s timezone is America/New_York and you schedule a transfer to run daily at 6:00 AM, it will always run at 6:00 AM Eastern time — even when Daylight Saving Time shifts occur.
Detrics handles DST transitions automatically:
- Spring forward (clock jumps from 2:00 AM to 3:00 AM): If your scheduled time falls in the skipped hour, Detrics runs at the next valid time
- Fall back (clock repeats 1:00-2:00 AM): Detrics runs once at the first occurrence
Choosing a Frequency
| Use Case | Recommended Frequency |
|---|
| Real-time campaign monitoring during peak events | Every 1-3 hours |
| Standard daily reporting | Daily |
| Weekly summary reports | Weekly |
| Monthly rollups or low-volume platforms | Monthly |
| Intra-day optimization for active campaigns | Every 6-12 hours |
For most use cases, Daily is the best starting point. Platform APIs typically don’t finalize data faster than once per day, so syncing more frequently gives you fresher data but the numbers may still shift. Hourly syncs are most useful during active campaign periods when you need rapid feedback.
Manual Syncs
You can trigger a sync at any time by clicking Sync Now on a transfer’s detail page. Manual syncs don’t affect the regular schedule — the next scheduled run happens at its normal time.
Refresh Windows
The refresh window controls how many days of data Detrics re-fetches on each Incremental sync. It only applies to tables assigned the Incremental sync mode on their transfer.
Why Refresh Windows Matter
Marketing platform data isn’t final when it first appears. Several factors can cause numbers to change after the initial report:
- Attribution delays — A user clicks an ad today but converts 3 days later. The conversion is attributed back to the click date
- Data processing lag — Platforms may take 24-48 hours to finalize metrics
- Billing adjustments — Spend figures may be adjusted after the fact
The refresh window ensures Detrics re-fetches this “settling” data and keeps your warehouse accurate.
| Platform | Recommended Window | Why |
|---|
| Google Analytics 4 | 1-2 days | Data typically finalizes within 48 hours |
| Meta Ads | 3-7 days | Attribution windows can extend up to 7 days depending on settings |
| Google Ads | 3-7 days | Conversion tracking may update for several days |
| TikTok Ads | 2-3 days | Standard attribution delay |
| LinkedIn Ads | 2-3 days | Standard attribution delay |
| Shopify | 1-2 days | Order data is usually immediate |
| Pinterest Ads | 2-7 days | Depends on attribution window settings |
How the Refresh Window Interacts with Sync Frequency
The refresh window and sync frequency work together:
- Daily sync, 3-day window: Each day, Detrics re-fetches the last 3 days. Data older than 3 days is locked and never touched again
- Hourly sync, 3-day window: Each hour, Detrics re-fetches the last 3 days. More frequent updates to recent data, but the window stays the same
- Weekly sync, 7-day window: Each week, Detrics re-fetches the last 7 days
The refresh window is set per table, not per transfer. This means you can have one table with a 2-day window (for analytics data that finalizes quickly) and another with a 7-day window (for ad data with longer attribution) in the same transfer.
Setting the Refresh Window
When a table is assigned Incremental sync mode on a transfer, you’ll configure a refresh window setting. The value is in days. If you’re not sure, start with the platform’s recommended default — you can always adjust later without losing data.
Historical Sync Range
The historical sync range determines how far back Detrics fetches data on the first sync of a transfer. This only affects the initial load; subsequent syncs use the refresh window (incremental) or re-fetch the full range (full refresh/append).
Available Ranges
| Range | Best For |
|---|
| Last month | Quick testing or recent-data-only use cases |
| Last 3 months | Standard starting point for most use cases |
| Last 6 months | Seasonal analysis, quarter-over-quarter comparisons |
| Last 12 months | Year-over-year analysis |
| Last 24 months | Deep historical analysis |
| All time | Complete data export from the platform |
Longer historical ranges mean larger initial syncs. An “all time” sync for a large Meta Ads account with years of data and dozens of campaigns may take significant time to complete. Start with 3-6 months and expand with a resync if you need more history.
What Happens After the Initial Sync
After the first sync completes:
- Incremental tables: Only the refresh window is re-fetched on each subsequent sync. Historical data outside the window is preserved and never re-fetched
- Full Refresh tables: The full date range is re-fetched every time (historical range determines the extent)
- Full Append tables: The full date range is re-fetched and appended every time
