Search

Personal Links

slack button (do not delete)

How to Integrate Knock with Marketo

How to Integrate Knock with Marketo

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
image
  1. 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.

image

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 who booked 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
image

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

Custom Field
Field Type
Description
Knock: Created
Dropdown select
Indicates if this Marketo
Knock: Connected
Dropdown select
Indicates whether this contact has sent a message via Slack

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.
image

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
image

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

Knock Unique Data

Knock Person Enrichment includes the fields mentioned below.

Knock Person Enrich

Field
Field Type
Description
Person Role
String text
The lead’s job title or function at their company. Example: VP Marketing, SDR.
LinkedIn Profile
URL
Direct link to the lead’s LinkedIn profile.
Profile Image URL
URL
Link to the lead’s profile photo.
Country
String text
The country where the lead is located. Prefer ISO-3166 country names or codes.
Phone
String text
Lead’s phone number

Attribution

Field
Field Type
Description
Origin Channel
String text
Top-level channel that started the visit. Examples: Direct, Organic Search, Paid Search, Paid Social, Referral, Email.
Origin Source
String text
Specific source within the channel. Examples: Google, LinkedIn, Newsletter, Partner site.
Origin Campaign
String text
Value of utm_campaign.
Origin Content
String text
Value of utm_content.
Referrer URL
URL
Full URL the visitor came from.
Entry Page
URL
First page the visitor viewed on your site.
UTM Term
String text
Value of utm_term.
UTM ID
String text
Value of utm_id.
GCLID (Google)
String text
Google Ads click identifier captured on arrival.
FBCLID (Facebook)
String text
Meta click identifier captured on arrival.
MSCLKID (Microsoft)
String text
Microsoft Ads click identifier captured on arrival.
LI_FAT_ID (LinkedIn)
String text
LinkedIn click identifier captured on arrival.

Knock Signals

Field
Field Type
Description
Intent Score
String text
Knock’s score for this contact’s buying intent. High means strong intent.
Intent Signals
String text
Actions that contributed to the score. Examples: Checked Pricing, Watched Demo, Read Reviews.
Intent Type
String text
The intent of the person: Buying, Partnership, Job Seeker, Support, Spam. This is only for contacts who sent a message though Knock.
Segments
String text
All Knock segments currently matching this contact. Examples: Save the lead.

Knock Chat

Field
Field Type
Description
First Touchpoint
String text
Chat link name. Examples: Website Footer
Touchpoint URL
String text
Chat link URL
Chat Owner
User lookup
The email of the rep who assigned as the owner of this contact chat
Responding Rep
User lookup
The email of the rep who first responds to the contact
Rep Responding Time
Number (minutes)
Minutes between the rep being added to the chat and their first reply.
Chat Status
String text
The lead progress in knock engagement funnel
Total Messages Sent
Number
Total messages sent by the lead

Knock Meeting

Field
Field Type
Description
First Meeting Booked
Date/Time
Timestamp of the first meeting scheduled via Knock for this contact.
Booked Meeting Owner
User lookup
The teammate who owns the meeting.
Meeting Type
String text
Category of the meeting. Examples: Intro, Discovery, Demo, Technical, Pricing, Follow-up.
Booked Meeting Time
Date/Time
The time of the last meeting booked
Last Meeting Booked
Date/Time
The time of the last meeting booked
Number of Meetings
String text
Total number of meeting booked by this contact

Knock Impact

Field
Field Type
Description
First Seen
Date
The first time the contact was detected by Knock
Last Seen
Date
The last time the contact was detected by Knock
Created
String text
Value is true if the contact was created by Knock
Connected
String text
Value is true if the contact was connected though Knock

Knock Company Enrich

Field
Field Type
Description
Company Headquarter
String text
City, state/province, and country of the company’s main office.
Company Size
String text
Number of employees
Company Industry
String text
Primary industry classification for the company.
Company Status
String text
Ownership status. Examples: Private, Public, Acquired.
Founded Date
Date
The company’s official founding date.
Last Funding
String text
Most recent funding round type. Examples: Seed, Series A, Series B, Series C, Debt, Grant.
Total Funding
Number
Cumulative capital raised to date.
Annual Revenue
Number
Latest reported annual revenue

FAQ

‣
Does Knock automatically sync all leads to Marketo?
‣
What qualifies as an “Accepted” lead?
‣
How does Knock handle duplicate persons?
‣
Does Knock overwrite existing Marketo data?