Website events never say who the visitor is. They carry the company, the visitor’s job function and seniority when Knock2 knows them, and the company’s ICP score. Never a name, email address, phone number or LinkedIn profile.
Turn on website events
1
Install the tracking script
Website events come from the Knock2 tracking script, so it needs to be on every page you want events from. See Install the tracking script.
2
Switch them on
In the Knock2 dashboard, go to Settings > Script > Website events and turn on Send website events. Only workspace admins can change this.
3
Choose how often
Every page view (recommended) sends an event on each page, and each event says whether it’s the first in the visit. Once per visit sends a single event per visit.
4
Set your fit score
Good fit above score decides when an event marks the company as a good fit (
icp.is_fit). The default is 50. The score itself is always included, so you can also apply your own rule.Listen for the event
The tracking script sends the same event three ways. Use whichever fits your setup.What’s in the event
string
The visit. The same on every page of one visit, so you can use it to count once per visit or as the event ID when you also send the conversion from your server.
boolean
True for the first scored event in this visit. Count events where this is true to count once per visit. An event sent before the company was scored doesn’t use it up.
string
The path of the page this event is for.
object
The company the visit came from: name, domain, industry, employee range, country and LinkedIn company page. Fields Knock2 doesn’t know are
null.object | null
Who in the company the visitor probably is, inferred for this visit.
null when Knock2 only knows the company.object
How well the company fits your ideal customer profile.
boolean
True when the company is on your existing customers list in Knock2, so current customers browsing your site can be left out of acquisition metrics.
Timing
Knock2 identifies and scores the company after the visitor’s first page loads. Each page waits up to about 30 seconds for a score. If none arrives, the event is sent withscore: null and the next page in the visit tries again. On single-page apps, a new event is sent when the visitor moves to a new page.
No event is sent for a visitor whose company Knock2 couldn’t identify, for a visitor who has opted out (including Global Privacy Control), or on pages you’ve excluded in Settings > Script > Excluded pages.
Examples
LinkedIn Ads conversion for ICP visits
Meta Pixel, deduplicated with the Conversions API
If you also send the same conversion from your server through Meta’s Conversions API, give both the same event ID so Meta counts it once.event_id in your server-side event.
Filter on persona
Google Tag Manager
1
Create the variables
Add Data Layer Variables for
knock2.icp.is_fit, knock2.first_in_session, knock2.is_existing_customer and, if you filter on persona, knock2.persona.job_function.2
Create the trigger
Add a Custom Event trigger for the event name
knock2_visitor_identified, firing on events where knock2.icp.is_fit equals true (and knock2.first_in_session equals true to count once per visit).3
Attach your conversion tag
Use the trigger on your LinkedIn Insight Tag, Meta Pixel or Google Ads conversion tag.