SyncHub acts as both a connector service and data store. Once you’ve [added your cloud software as a connection](/connectors/getresponse/knowledge-base/gettingyourdata) in your SyncHub account, we use that software’s API to begin incrementally syncing your data and staging it in your database. SyncHub then continues to regularly check the API for any additions or modifications made to your data, and updates the database accordingly.
We use two mechanisms to keep your date up-to-date - webhooks and runs.
### Webhooks
Webhooks are the preferred method for keeping your data up to date - see [this article](/connectors/getresponse/knowledge-base/incomingwebhooks) for more information.
### Runs
If webhooks are not available, we need to poll your cloud service on a regular basis to check for new data. We call these "_runs_", and you can control how they occur using two levers: run size and run frequency.
**Run size** is the size of the chunk of data requested during each API call. It is measured in terms of time, but the exact filter depends on your particular endpoint.
> For example: If your endpoint filters on _modification date_ and your run size is two days, then we'll download records modified within a particular two day period. Alternatively, if your endpoint filters on _Job Start Date_ then we'll check for jobs _started_ within the given two day period.
You can check the date filter type, and adjust the run size via your endpoint configuration.
**Run frequency** is how often a run is made. For example, if your run frequency is set to 1 hour, then your data will be updated every 1 hour.
Whether you can change the run frequency for your data tables is [determined by your plan](https://www.synchub.io/pricing). The exception to this is when you [add a new connection](/connectors/getresponse/knowledge-base/gettingyourdata): regardless of your plan, SyncHub will automatically set the run frequency to 1 minute. This helps speed up the process of bringing in your historical data. Once your data is up to date, it will return to normal.
You can configure your run frequency for a specific endpoint via its endpoint settings, or you can [bulk update multiple endpoints at once](/connectors/getresponse/knowledge-base/bulkupdatefrequency).