Sync Data Source
Last updated: 2026-06-10
Sourcesible Product Documentation · Activation
Overview
Sync Data Source allows you to mirror raw data from a connected ad platform Data Source such as TikTok Ads, Google Ads, or Facebook Ads directly into a warehouse Destination like BigQuery. This enables advanced analysis and reporting on your ad platform data without leaving your data infrastructure.
Before creating a Sync Data Source, ensure you have at least one Data Source connected (e.g., TikTok Ads, Google Ads, Facebook Ads) and a BigQuery Destination connected.
Creating a Sync Data Source
Open the Sync Wizard
In the left navigation, click Sync. Click Sync in the top-right corner and select Sync Data Source from the dropdown.
Select Data Source
On the Select Data Source screen, select the Data Source you want to sync by clicking its radio button, then click Next.
Only Data Sources that have been connected via the Data Sources setup appear in this list. If your source is missing, set up the connection first before returning here.
Select Destination
On the Select Destination screen, select the Destination you want to push data to, then click Next.
For Sync Data Source, BigQuery is the supported Destination. Sourcesible will automatically create the necessary table structure in BigQuery to store the incoming data.
Set Up Sync
Enter a Sync Name (a unique name for this sync you can update it anytime under Settings) and an optional Sync Description. Under Source Name, review the selected Data Source and its associated ad account these are read-only. Under Sync to Destination, confirm the sync direction shown. Under Historical Sync Time Frame, select how far back in time you want to fetch data for the first sync. Click Next.
The Historical Sync Time Frame only applies to the initial sync run. All subsequent runs will fetch only new data since the last sync.
Set Schedule
Choose your Schedule Type: Manual (trigger each sync manually, no automatic runs) or Daily (run automatically every day note that data will reflect the previous day due to source availability). Click Finish.
Running the Sync
After creation, the Overview tab will prompt you to trigger your first run. Click Run Sync to begin. The button will change to Processing... while the sync is in progress. Once complete, a success banner will appear and the Sync Runs table will update.
Sourcesible creates the table structure in BigQuery automatically on the first run. You do not need to pre-create the tables.
Next Steps
With your Sync Data Source running, you can manage it from the Sync list page.
View Sync Run History Monitor past runs and diagnose failures from the Overview tab.
Edit Sync Settings Update the Sync Name, description, or source configuration from the Setup tab.
Change the Schedule Switch between Manual and Daily from the Schedule tab.
Query Synced Data in BigQuery Use the synced ad platform data for downstream analytics and reporting.
Tips and Troubleshooting
Sync Runs Successfully But No Tables Appear in BigQuery
Symptom: The Sync Run shows Success but no new tables are visible in the BigQuery dataset.
Cause: The ad platform account may have no data available for the selected Historical Sync Time Frame, or the BigQuery dataset location does not match the project region.
Fix: Verify that the source ad account has campaign or reporting data available for the selected time period. If needed, delete the Sync and recreate it with a longer Historical Sync Time Frame such as 6 months.
Data Source Not Appearing in Step 1
Symptom: The ad platform source you want to sync is not listed in the Select Data Source screen.
Cause: The Data Source connection has not been set up in Sourcesible yet, or the connected source has been disconnected.
Fix: Navigate to Data Sources in the left navigation and verify the source is connected and active. If it is missing, create a new Data Source connection before returning to Sync.
Sync Status Shows "Disconnected"
Symptom: An existing Sync Data Source shows Disconnected status on the Sync list page.
Cause: The underlying Data Source connection or Destination connection has expired typically due to an expired OAuth token on the ad platform side.
Fix: Navigate to Destinations and verify the BigQuery connection is still Connected. Navigate to Data Sources and reconnect the affected ad platform source. Return to Sync after reconnecting, trigger a Run Sync manually to confirm the connection is restored.