Set up a webhook integration for a YouTube lead form

A webhook integration allows you to automatically send information from one app to another using a unique URL. You can create a webhook integration to link your YouTube lead form to your customer relationship management (CRM) software. After you add a webhook integration to your lead form, you’ll receive your leads in real time.

Get started with webhook integration

To add the webhook integration to your lead form, you'll need to generate a webhook URL and a key.

The webhook URL is the delivery path. After a person submits their information in a lead form, an HTTP POST request is sent to the configured URL, allowing the lead data to go directly into the CRM system. The key is used to validate the leads sent.

There are two ways to generate the webhook URL and key:

• Create the webhook integration: If you have the ability to do so, you can create the webhook integration and then generate a webhook URL and key. Learn more about generating a webhook URL and key.
• Use a third-party integration: You can use Zapier, a third-party integration provider, to generate a webhook URL and key. Learn more about using Zapier.

Add a webhook integration to a new lead form

Follow the directions in Create a lead form in a new line item.

Edit a webhook in an existing lead form

1. Navigate to your insertion order and click the name of the line item containing the lead form.
2. Click Line item details.
3. Click the Lead form extension menu button , then the pencil icon to edit.
4. Scroll down and click Next to navigate to the Lead form preferences page.
5. Navigate to the Lead delivery section and add your Webhook URL and Key.
6. Click Send test data and verify that your CRM receives the data correctly. 
7. Click Save.

Error states

Depending on your initial actions after adding a webhook, you may see one of the following error states:

• Error state A is when form is saved without sending test data (successfully).
• Error state B is data that is not sent.
• Error state C is data sent without Google receiving a response.
• Error state D is data sent, but Google receives an incorrect response (different than "HTTP 200").
• Success state is data sent, and Google receives a correct response.