Fix sync errors and connection issues.
If the LinkedIn connection fails during OAuth, check that: (1) you have Admin access to the LinkedIn Ads account, (2) your organization hasn't restricted third-party app access in LinkedIn Admin settings, (3) you're not using a browser extension that blocks OAuth redirects (common with privacy extensions), and (4) you're signing in with the correct LinkedIn account. Try disconnecting and reconnecting from Settings → Connections.
HubSpot OAuth failures typically happen when: (1) your HubSpot plan doesn't include API access (requires Starter or above), (2) you don't have super admin permissions in the portal, or (3) your HubSpot portal has IP restrictions that block our servers. Check your HubSpot Settings → Integrations → Private Apps to verify API access is enabled.
Common Salesforce connection issues include: (1) the connecting user doesn't have "API Enabled" permission, (2) your org has IP restrictions on the connected app, (3) you selected "Production" but need "Sandbox" (or vice versa). Check Setup → Users → Permission Sets to verify API access. If your org uses SSO, ensure the OAuth flow can complete outside your SSO provider.
If a sync has been running for more than 30 minutes, it may be stuck. Go to Dashboard → Sync Status and check for error messages. Common causes: (1) LinkedIn API rate limits during peak hours — the sync will auto-retry, (2) CRM timeout on very large datasets (50,000+ companies), (3) temporary API outage on LinkedIn or your CRM side. Click "Cancel Sync" and retry after 15 minutes.
If companies that engage with your LinkedIn ads aren't showing in RevenueProven: (1) check the "Unmatched Companies" view — they may have engaged but don't match any CRM record, (2) verify the CRM company has a website domain populated, (3) check your date range — the engagement may fall outside your selected lookback window. Domain matching requires the CRM company to have a website field.
Duplicates typically come from your CRM data, not RevenueProven. If the same company appears twice, check your CRM for duplicate company records with slightly different domains (e.g., "acme.com" and "www.acme.com"). RevenueProven normalizes domains before matching, but if your CRM has two distinct company records with the same domain, both will appear. Merge the duplicates in your CRM and re-sync.
OAuth tokens expire periodically. If you see a "Token expired" or "Authentication failed" error, go to Settings → Connections and click "Reconnect" for the affected integration. This initiates a fresh OAuth flow. If you manually revoked access from LinkedIn or HubSpot settings, you'll need to reconnect. RevenueProven automatically refreshes tokens when possible, but manual revocation requires re-authorization.
Small discrepancies between RevenueProven numbers and your CRM are normal and caused by sync timing — your CRM may have been updated after the last sync. Trigger a manual sync to get the latest data. Larger discrepancies usually mean some deals or companies aren't matching. Check the "Unmatched" view and verify CRM domain coverage. RevenueProven only attributes deals it can match to LinkedIn-engaged companies.