CRM sync problems
Fix missing CRM records, fields that landed in the wrong place, and reference matches that ignore the company and the deal sitting in front of your seller.
When matching looks random, the CRM connection is usually mapping the wrong fields or missing permission to read the record.
Checklist
- In Admin → Integrations, confirm the connector is connected and not showing an auth error.
- Open the CRM record. Can the integration user see it? Sharing rules and field-level security hide more than people expect.
- Revisit field mapping: industry, country, and amount must point at the fields sellers actually fill in.
- Check whether you tested in sandbox and the team is working in production — two connections, two mappings.
- Look at recent sync errors. A single required field in the CRM can stall a batch.
Related guides
- Connect your CRM
Link Salesforce, HubSpot, Dynamics 365, or Pipedrive so matching can use the company and the deal that are already open in the CRM sitting in front of you.
- Salesforce
Connect Salesforce, map the fields that matching needs, and open the right customer proof from the opportunity your seller is working in Salesforce now.
- HubSpot
Connect HubSpot CRM so companies and deals can drive reference matching, with the same careful field mapping you would use for Salesforce or any other CRM.
- Match a prospect to a reference
Find the best-fit customer proof for a live deal, then request it with recorded consent so the right advocate is asked only in the right way for that deal.