What are Webhooks?
Webhooks take the data collected by PathFactory on an individual by individual basis, and submit this data to an application outside of PathFactory.
Webhooks are the connectors which send data gathered by PathFactory to your third party systems. Examples of third party systems you can connect to include Marketing Automation Platforms, Business Intelligence Platforms, and Customer Relationship Management software.
There are three different types of webhooks, each of which caters to a specific type of visitor engagement, and which will be triggered to send data whenever one of those types of engagements happens.
|
Note
|
You only need to create one of each type of webhook. For example, once you set up a Visitor Activity Webhook, this one webhook will send data for all the different Visitor Activities you create. |
Types of Webhooks
Form Capture
The Form Capture Webhook is triggered when a visitor submits a Standard PathFactory Form.
The data that the visitor entered in the form is sent with this webhook as well as some additional information on where and when the form was submitted. For more information on the data that can be sent in the Form Capture Webhook check out Webhook Field Definitions.
For instructions on how to set up a Form Capture Webhook click here.
|
Warning
|
This event will not trigger if an external form is used. If you are using an Eloqua, Marketo, Pardot or any other external form in your Content Tracks you will not be able to trigger a Form Capture Webhook. This is because the form fill is automatically sent to your MAP. Instead, you need to add a Capture Tag to your external form, which ensures that PathFactory receives the form fill data. |
Visitor Session
The Visitor Session Webhook is triggered by any session (ie. anytime a visitor views a Content Track).
A visitor session begins when a visitor arrives in a Content Track, and ends when that visitor has stopped engaging with content for thirty minutes. This webhook is triggered when a visitor session ends. This means that the webhook will trigger and send data to the external system thirty minutes after the visitor has finished engaging with content.
The data sent though this webhook provides an overview of the level of engagement the visitor had with your Content Track and the content assets inside them during the session. For more information on the data that can be sent in the Visitor Session Webhook check out Webhook Field Definitions.
For instructions on how to set up a Visitor Session Webhook click here.
Visitor Activity
The Visitor Activity Webhook is triggered when a visitor to a Content Track has met one or more of the predefined activities set in the Visitor Activities Configuration.
To use this webhook you must first set up your visitor activities. The data from this event is sent thirty minutes after the visitor last engaged with a content asset.
|
Note
|
See this article for more information on visitor activities. |
The data sent though this webhook depends on the visitor activity that you set up. For more information on the data that can be sent in the Visitor Activity Session Webhook check out Webhook Field Definitions.
For instructions on how to set up a Visitor Activity Webhook click here.
Why do you use Webhooks?
Webhooks allow your PathFactory platform to automatically connect with your third party system and send data every time someone visits or interacts with your PathFactory content track.
The division of webhooks into three separate categories allows for more granular data to be collected, which gives you more detail on your visitors and makes it easier to organize and glean insights from your data.
How do Webhooks work?
|
1. Connect |
Create one webhook for each of the three webhook types to connect with your external system. You only need one of each webhook type; for example, any action you have defined as an important visitor activity will be sent with the single Visitor Activities Webhook. |
|
2. Trigger |
A webhook is triggered by an event—someone visiting your Content Track, someone filling out a form in your content track, or engaging with your content in a way you have defined as significant (as defined by your Visitor Activities). |
|
3. Send |
The data collected for a particular event is sent from PathFactory to the external system you connected it with. |
More Information on Webhooks
How do Webhooks Relate to Integrations?
Webhooks are a type of integration. “Integrations” refers to the ability to connect two systems so that they can work together, and a webhook is a way of automatically sharing data between PathFactory and any external system you use to manage prospect data.
How do Webhooks Relate to Visitor Activities?
Webhooks are triggered by Visitor Activities. You can define as many different visitor activities as you want, but you only need one webhook (a Visitor Activity webhook) to send all that data to your external system. Visitor activities are all the different ways that visitors are interacting with your content tracks that you have defined as important, and the webhook is what sends that event data to your external system.