Crisp provides access to the latest data from retailer and distributor sources all in one place. Data sources often make changes to their data after the initial data capture to add missing or incomplete data or correct data errors. These data changes are called "restatements". How far back in time Crisp checks for restatements is called the "lookback period".
For Crisp-managed outbound integrations, such as with Snowflake or BigQuery, the Crisp platform automatically handles restatements and ensures that the target datasets always contain the most current data. When integrating with object storage applications, such as such as Google Cloud Storage, AWS S3, or Azure Blob Storage, your ETL pipeline needs to handle this manually.
On each export, Crisp provides all the data for a default lookback period that is configurable by Crisp. The default lookback period is 14 days for daily datasets, which means that 14 days worth of data will be exported each day. For object storage applications (such as Amazon S3, Google Cloud Storage, or Blob Storage), by default, the data will be restated in place by overwriting data files within the lookback period. If you do not want data files to be overwritten with restated data, you can customize your connector set up to create paths based on the export date, creating separate files for restated data. For more, see Object storage paths and file names for outbound connectors.