What this is
The Sync Settings Debugger is a tool that allows you to compare data between Propensity and your CRM (such as HubSpot or Salesforce).
It helps you verify whether records are syncing correctly and identify any differences between the data stored in Propensity and the data in your CRM.
This tool is useful for troubleshooting sync issues and confirming that integrations are working as expected.
When to use it
Use the Sync Settings Debugger when you want to:
Confirm that data is syncing correctly between Propensity and your CRM
Investigate discrepancies between Propensity and CRM records
Validate that recent updates have been reflected in both systems
Troubleshoot missing or inconsistent data
How to run the debugger
To run the debugger:
Click you profile icon and go to CRM Sync Settings
Navigate to Debugger
Select your CRM:
HubSpot
Salesforce
Start the debug process
The system will compare records between Propensity and your selected CRM.
Once the process is complete, the page will refresh and display the results.
Understanding the results
After the debugger runs, two options will be available:
Download file
View sample
These outputs provide a comparison between Propensity data and CRM data. The Download file provides the full dataset for detailed analysis, while View sample offers a smaller preview for quick validation.
Download file
The file from the Download button is a CRM comparison file that provides a detailed, record-level view of how data in Propensity aligns with data in your CRM.
Each row represents a contact record and its associated data from both Propensity and your CRM, and includes both CRM data (such as name, email, company, and job title) and Propensity-enriched fields (such as campaign activity, engagement metrics, and warmth scores)
This comparison allows you to:
Verify that records exist in both systems
Confirm that key fields (such as contact details and company information) are consistent
Identify differences between CRM data and Propensity data
Review engagement signals tracked by Propensity (such as impressions, clicks, and website visits)
The file also includes Propensity-specific attributes, such as:
Campaign and channel activity
Recent engagement metrics (impressions, clicks, visits)
Contact warmth and warmth reasons
Enriched fields like skills, interests, and location
Because both CRM and Propensity data are displayed side by side, this output is especially useful for identifying:
Records that exist in one system but not the other
Fields that are not syncing correctly
Data that may be outdated in either system
View sample
The sample file provides a preview of the full comparison dataset, displaying a limited number of records (for example, the first 200 rows).
The structure and fields in the sample file are the same as in the full download, allowing you to review how records from your CRM and Propensity are matched and displayed.
Each contact may appear multiple times in the file, once for each data source (e.g., HubSpot and Propensity), allowing you to compare values across systems.
This sample allows you to:
Confirm that contacts are being correctly matched between your CRM and Propensity
Validate that email-based matching is working as expected
Quickly spot duplicates or missing records
Preview how the full comparison file is structured
In addition to basic identity fields (such as email, name, job title, and company), the sample also includes Propensity attributes such as:
Contact warmth (Hot, Warm, Cold) and last update date
Engagement signals (e.g., ad impressions, clicks, website visits)
Campaign and channel activity
Email verification status and metadata
If discrepancies are identified in the sample, download the full file to review all records in detail.
What the debugger compares
The debugger compares records between Propensity and your CRM to confirm that:
Records exist in both systems
Key data fields are aligned
Sync processes are up to date
The results highlight differences between the two systems, helping you identify where updates may be missing or inconsistent.
Important notes
The debugger does not modify or update data. It is a read-only comparison tool
Results reflect the state of data at the time the debugger is run
Large datasets may take time to process before results are available
If discrepancies are found, further investigation may be required in your CRM or sync configuration