When you connect a SaaS integration, Stitch will begin the process of syncing not only that integration’s recent data, but the historical data as well. Unless defined otherwise, Stitch will use the integration's default starting date to begin syncing historical data.
While it's possible to change the starting date for the majority of SaaS integrations, there are a few things you should keep in mind before doing so. In this doc, we'll cover:
Each integration has a default starting date, which tells Stitch how far back to query for historical data. The majority of integrations have a default starting date of -1 year from the Stitch connection date.
If an integration has a default starting date of -1 year and was connected to Stitch on October 1, 2016, for example, a historical sync would go back to October 1, 2015.
A rollup of the default starting dates for all SaaS integrations can be found in the last section of this doc.
Default Starting Dates & Data Discrepancies
If you believe you’re missing data, try to narrow it down to a specific timeframe. If that timeframe falls outside the default starting date, this may be the root cause of the discrepancy. Check out the Data Discrepancy Troubleshooting Guide for more troubleshooting tips.
An integration's start date can be defined when you initially connect the integration to Stitch or after the fact.
Before changing an integration's start date, we recommend considering the following points. Note that these points shouldn't cause worry or discourage you from setting up historical syncs - they're only intended to give you a comprehensive look at this process.
Note that this feature is not available for some integrations. Pardot, for example, doesn't use date-based replication, making this date-based approach incompatible.
If you don't want to use the integration's default starting date when connecting a new integration, you can do the following:
Note that it may take some time for Stitch to perform a structure sync for the integration and begin replicating data.
If successful, a confirmation message will display indicating the historical sync has been queued. The integration's historical data will begin replicating according to that integration's defined Replication Frequency.
Check out the table below for the default starting dates for each of our integrations and any limitations there may be about historical syncs. Note that in most cases, it's possible to retrieve data beyond the default starting date, but the amount of data Stitch replicates may be massive.
|Integration||Default Starting Date
(from date of Stitch connection)
|Bing Ads||1 year|
|Facebook Ads||1 year
|Google AdWords (NEW)||30 days|
|Google Adwords (deprecated)||15 days|
|Google ECommerce||15 days|
|Google Analytics||30 days|
* Facebook Ads: We can run a historical sync all the way back to January 1, 2013.
** Mixpanel: Going back further than 7 days is possible, but note that the potential amount of data to be replicated could be massive.
✝ Webhook integrations do not, by design, have historical data. Some integrations - like Segment - may be able to “replay” data depending on their app’s abilities and/or your account level. Contact that integration's support team if you have questions.