Sync Frequency for Inbound and Outbound Data

Claravine syncs data on different schedules depending on the integration type. This article covers how often data moves in and out of the platform, and how to trigger a sync manually when you need one.

Inbound Integration Sync Frequency (Template Level)

Scheduling a data sync tells the Data Standards Cloud how often an integration pulls data from a connected source, such as Meta Ads Manager. Admins set this frequency in the integration configuration section of the template.

Inbound integrations default to bringing in data every 8 hours, but can be set to every 4 hours if needed.

The sync brings any new or updated ad data from the platform into the Pending menu of its respective template for review and validation. Administrators can enable automatic submission at the template level. See Automatically Submit Data for more information.
 

File-Based Inbound Data Frequency

When you first connect a bucket, Claravine imports all the files already in it. After that, Claravine checks the bucket every 15 minutes for new files. There is no configuration required.

Outbound Data Push Frequency

Outbound integrations push data in real time. A row submission triggers the push immediately, so data reaches the destination without waiting on a fixed schedule. There is no configuration required.
 

Manually Triggering Inbound Sync (Dataset Level)

A manual sync gives users more control by triggering an extra run outside that schedule. Use a manual sync when:

• You're testing a new integration and want to verify data flow immediately.
• Campaign data needs to come in urgently for a time-sensitive launch.
• You're troubleshooting a data discrepancy and need to confirm the latest state from the source system.

Manual syncs are limited to four per hour to avoid putting undue stress on your system. Once a sync finishes, your data is up to date.

To trigger a manual sync:

1. From the Datasets page, click on the template name.
2. Open the Integrations tab. Installed integrations display as tiles. Only inbound integrations show a Run Now option.
3. Select the inbound integration tile and click Run Now.
   • If a sync is already running, you'll see a message immediately.
   • If you've hit the four-per-hour limit, you'll see a message and can try again once it resets.
4. The sync appears in your list of Pending Submissions. Manual syncs aren't logged in the Integration Activity Log, since that log only tracks automated runs.

Full Dataset Resend for File-Based Outbound Integrations (Dataset Level)

If you need to push all of a dataset's data downstream again, rather than just newly submitted or edited rows, use the Send Entire Dataset button. Where available, it's the fastest way to resend everything to a connected destination without exporting and re-uploading a file, or resubmitting rows one at a time. It's the recommended option for a full resend, since resubmitting rows individually can trigger errors on older records if required fields were added after they were first submitted.

This button is available only on file-based outbound integrations: S3, SFTP, Google Cloud Storage, and Snowflake. 

To resend the entire dataset:

1. From the Datasets page, click on the template name.
2. Open the Integrations tab. Installed integrations display as tiles. Only outbound file-based integrations show a Send entire dataset option.
3. Select the outbound integration tile and click Send entire dataset.
   • The entire dataset will resend to that destination with the exact file configuration as designed.