How to Integrate Knock with Marketo

The Knock + Marketo integration connects real-time lead engagement data from Knock directly into Marketo, helping marketing teams stay aligned and prioritize attribution channels based on revenue impact.

What You Can Do with the Knock-Marketo Integration

• Automatically sync leads from Knock to Marketo
• Enrich person info in real time. Read more
• Sync attribution data per lead. Read more
• Enrich company info in real time. Read more
• View first-party intent signals and lead actions in Marketo. Read more
• Map Knock unique data to Marketo fields

How to Activate the Knock-Marketo Integration

You can activate the integration from the Knock App in Slack or directly via the Knock Dashboard.

Option 1: From Slack

1. Go to the Knock app in your Slack workspace
2. If you don’t see it, go to Slack’s sidebar:
• Click Apps → Manage → Browse Apps and search for "Knock"
3. In the Knock App Home, scroll to the Administration section
4. Click Start under the Marketo Integration
5. Make sure you have admin rights in Marketo to complete the connection

Option 2: From the Knock Dashboard

1. Open the Knock Dashboard
2. Go to the Getting Started or Integrations section
3. Select Marekto, then click Start Integration

4. Access the Marketo Integration page and click Connect

Invite Marketo Admin to the Dashboard

If you are not the admin of Marketo, click on the Invite button at the top left, and send an invitation to the Marketo Admin.

How Knock Creates Persons in Marketo

This section explains when and how Knock creates Persons and companies in Marketo, and how you can control which leads are synced.

Person Creation in Marketo

1. By default, Knock creates accepted leads only in Marketo. Accepted leads include:
• Leads assigned to a human representative during a chat
• Leads who book a meeting using Knock Scheduling
2. Control which Persons are created in Marketo
1. Use the settings to decide when Knock creates Persons in Marketo. Choose which leads are added as Persons
1. None - No Persons are added to Marketo. Commonly used when multiple CRM connections exist and you want to prevent duplicate records.
2. Engaged - Leads who started a chat or attempted to book a meeting.
3. Accepted - Leads assigned to a human representative or attempted to book a meeting.
2. Filter Persons by intent type - Choose which intent types trigger Person creation:
1. Buying
2. Support
3. Partnership
4. Job seeker
3. Control email eligibility - Choose how Knock handles email types when syncing Persons:
• Only business emails
• All accepted leads, including personal email addresses

Fields created when a new Person is added

When a lead is accepted, Knock creates a new Marketo Person with the following standard fields:

• First Name
• Last Name
• Email
• Company

Person Custom Fields Added by Knock

Mapping Knock Fields to Marketo

Mapping Knock fields to your own Marketo fields is optional. You may choose to map fields if you want Knock data to:

• Populate existing Marketo fields, or
• Trigger Marketo workflows that rely on specific fields

Field mapping defines which Marketo field receives data from each Knock field. Only mapped fields can receive Knock data.

How to Map Knock Fields

To create a field mapping:

1. Choose a field category from the list
2. Select the Knock field you want to map
3. From the dropdown, choose the Marketo field that should receive the Knock data. Only compatible Marketo field types are available for selection.

How Mapped Fields are Updated

For any field you choose to map, Knock updates the mapped Marketo field only when:

• The field is empty, or
• The Override option is explicitly enabled for that field
• Unmapped Marketo fields are never modified.

You can map Knock fields only to compatible CRM field types with write permissions:

• String fields - recommended for most Knock fields
• Date fields - used only for Knock date-type fields (for example, First Seen)
• Integer fields - used only for Knock numeric fields (for example, Response Time)

Important: The target CRM field must not belong to the Knock Data field group. All other incompatible fields are automatically filtered out to prevent write errors and ensure reliable field mapping.

How the Override Option Works

The Override option controls whether Knock can replace existing values in a mapped Marketo field. Override settings are configured per field mapping.

1. Enable or disable Override - To manage the Override setting:
1. Map a Knock field to a Marketo field
2. Use the Override toggle next to the mapped Marketo field to turn it on or off
2. Override behavior
• Override off - Knock writes a value only if the Marketo field is empty
• Override on - Knock writes or updates the value even if the Marketo field already contains data
3. Additional details
• Use the CRM sync monitoring table to review how mapped and overridden fields are written in Marketo
• For Knock-specific data (such as chat activity, meeting status, signals, and impact data), we recommend enabling Override to ensure the most up-to-date information is written to Marketo

Create New Marketo Fields Directly Through Knock

Save time and stay organized by creating custom Marketo fields without ever leaving Knock. Instead of switching between platforms, you can build and map new fields on the spot - tailored exactly to your workflow.

How to create a new Marketo field in Knock:

1. Choose a field to map, then select "Create New Field" from the dropdown.
2. Enter a unique field label that clearly identifies the data it will capture.
3. Click Create Property - Knock will instantly create the field in Marketo and map the value to it automatically.

This eliminates manual setup in Marketo and ensures your custom fields are ready to use the moment you need them.

Apply Mapping to Past Records

Field mappings apply to records Knock creates or updates going forward. To sync a mapped field to historical records, use Apply to Past Records.

How to run a backfill:

1. In the field mapping table, find the mapped field you want to backfill, click the three-dot menu, and select Apply to Past Records.
2. A preview panel opens showing the estimated number of records that will be updated and skipped. The write behavior defaults to the Overwrite setting configured for that field - you can change it before applying.
3. Click Apply to confirm, or Cancel to exit.
4. Once the backfill completes, a confirmation notification will show the number of records updated.

Verify the results in Marketo:

1. In Marketo, go to Contacts (or Companies).
2. Filter by Knock: Created = True or Knock: Connected = True to view Knock-touched records.
3. Open a few records and confirm the mapped field has been populated as expected.

Note: The backfill applies to all records Knock has created or updated in Marketo - including both Knock-connected and Knock-created records. This scope is broader than the CRM Sync Monitoring table, which only shows Knock-connected records, so the preview count may be higher than what you see in monitoring.

Person Enrichment & Duplication Handling

• Knock will not overwrite existing person data
• Knock only fills in empty fields
• If the person email already exists in Marketo, Knock updates that person
• No duplicate persons will be created

Next Up - Mapping data to your CRM

The following page lists every field Knock can write to your CRM - across Contacts and Companies. Use it as the source of truth when configuring field mapping for HubSpot, Salesforce, or any other connected CRM.

FAQ

On this page

• How to Integrate Knock with Marketo
• What You Can Do with the Knock-Marketo Integration
• How to Activate the Knock-Marketo Integration
• Option 1: From Slack
• Option 2: From the Knock Dashboard
• Invite Marketo Admin to the Dashboard
• How Knock Creates Persons in Marketo
• Person Creation in Marketo
• Fields created when a new Person is added
• Person Custom Fields Added by Knock
• Mapping Knock Fields to Marketo
• How to Map Knock Fields
• How Mapped Fields are Updated
• How the Override Option Works
• Create New Marketo Fields Directly Through Knock
• Apply Mapping to Past Records
• Person Enrichment & Duplication Handling
• Next Up - Mapping data to your CRM
• FAQ