Search

Personal Links

slack button (do not delete)

CRM Sync Monitoring

CRM Sync Monitoring

Monitor CRM data synced from Knock

The CRM data sync monitoring view is a read-only audit view that helps you understand how Knock-connected leads are represented and updated in your CRM.

This view does not control syncing or trigger any data writes.

A lead becomes Knock connected when they start a chat or book a meeting through Knock. After a lead connects, Knock may create or update a CRM record based on your field mapping configuration.

By default, the monitoring view shows:

  • CRM records associated with Knock-connected leads
  • Data written through configured field mappings
  • CRM fields created by Knock
image

What you can do with CRM data sync monitoring

Use this view to:

  • Identify which leads or contacts connected to Knock by starting a chat or booking a meeting
  • Verify that those connected records were correctly created or updated in your CRM
  • Review the results of field mappings, including which CRM fields received data
  • Confirm override behavior for fields where override is enabled
  • Audit how Knock updates CRM records after a lead connects

Access CRM data sync monitoring

To open the monitoring view:

  1. Open your Knock dashboard
  2. Go to CRM Integrations
  3. Select your CRM (HubSpot, Salesforce, or Marketo)
  4. Click Synced Contacts, Accounts, or Persons (Marketo)
image

What the monitoring table shows

The monitoring table lists CRM records associated with leads that connected to Knock through a chat or meeting.

Records are sorted by First sync date, which represents the first time a Knock-connected lead resulted in data being written to the CRM record.

Each row represents a single CRM record. Each column represents a CRM field, including both Knock-created fields and native CRM fields.

Supported CRM record types

The available record types depend on your CRM’s native data model:

  • Salesforce: Leads, Contacts, Accounts
  • HubSpot: Contacts, Companies
  • Marketo: Persons

The monitoring view reflects each CRM’s native object model.

Knock fields vs. native CRM fields

Fields labeled with “Knock” are custom CRM fields created by Knock.

These fields are used to:

  • Track that a lead connected to Knock
  • Store metadata related to Knock conversations or meetings
  • Distinguish Knock-written data from native CRM data

Native CRM fields are never modified unless they are explicitly mapped in your Knock field mapping configuration.

View mapped and overridden field values

The monitoring table shows values written to mapped CRM fields, including fields configured to override existing data.

Use this view to:

  • Validate field mappings
  • Confirm override behavior
  • Troubleshoot unexpected CRM values

Create and customize monitoring views

You can customize the monitoring table to support auditing and troubleshooting:

  • Select which fields (columns) are displayed
  • Reorder columns to compare Knock fields with native CRM fields

These customizations apply only to the monitoring table UI and do not affect CRM schema, conversations, or sync behavior.

Date columns added by Knock

Knock adds read-only date columns in the monitoring table to show when a lead connected to Knock and when the CRM record was last updated by Knock.

  • First sync date – When Knock first wrote data to the CRM record after the lead connected
  • Last updated date – When Knock most recently updated the record.

FAQ

‣
Why don’t I see all CRM records here?
‣
What does “Knock connected” mean?
‣
Does appearing in this table mean Knock created the CRM record?
‣
Can this view change or overwrite CRM data?
‣
What do the date columns represent?