RP
RevenueProven
All Help Articles

What happens during the first sync

The first sync after connecting your integrations can take 10 to 45 minutes. This guide explains each phase, what to expect, and how to tell when data is ready.

After you connect your integrations, Revenue Proven runs a background sync to pull and process your data. The first sync is longer than subsequent syncs because it needs to build the full historical picture across all lookback windows.

Sync phases

The sync pipeline runs through a series of phases in a fixed order. It starts with a campaign search to discover all campaigns in your ad account, then pulls engagement data across each of the five lookback windows, then fetches organization details for each engaged company. After the LinkedIn phases, it pulls CRM data from HubSpot or Salesforce, runs the matching algorithm, and finally calculates attribution. Progress is shown on the dashboard home page.

  • Campaign search: discovers all campaigns in your connected ad account.
  • Engagement pull: fetches company-level ad analytics across 7, 30, 60, 90, and 180 day windows.
  • Organization lookup: resolves company names, website domains, and country data.
  • CRM pull: syncs accounts, deals, contacts, and pipeline stages from HubSpot or Salesforce.
  • Matching: links LinkedIn companies to CRM accounts using domain and fuzzy name matching.
  • Attribution: calculates influenced pipeline and revenue for each matched account.

How long the first sync takes

The duration depends primarily on the size of your LinkedIn Ads account. Accounts with a few campaigns and modest spend typically complete in 10 to 20 minutes. Large accounts with many campaigns running across long periods can take up to 45 minutes. Data appears progressively as each phase completes, so you may see partial results before the full sync finishes.

After the first sync

Once the sync completes, you will see the full Company Insights table and Campaign Analytics populated with data. Subsequent syncs run on a daily schedule and are much faster because they only process incremental changes since the last sync.