A Webhook allows you to receive additional data or status updates during the flow.
It is most commonly used when you send a lead to an advertiser, but they cannot return the final response immediately. In that case, you need to either poll their system or wait for them to send the result later. This is where the Webhook step is used.
Settings
- Pingtree waits until webhook finishes – If enabled, the ping tree will wait until the webhook receives the data. Use this only when you are sure the advertiser will send the response. Otherwise, we recommend setting a timeout.
- Timeout – Available only when Pingtree waits until webhook finishes is enabled. Defines how long the system should wait before the scenario is marked as failed.
- Lead ID pairing – Used when the advertiser does not send the lead identifier in the expected parameter names. You can map their identifier type and specify the request key where the value should be taken from.
- Webhook ID – Each webhook must have its own ID. If you delete a webhook and later recreate it, you can reuse the previous ID so the advertiser does not need to change anything on their side.
- Endpoint – The URL you provide to the advertiser so they can send the data back to your sce
Matching an incoming webhook to a specific lead is handled according to the standard process:
- Via PalDock Conversion ID – only this parameter is required, since it is always unique in the system.
- Via Advertiser External ID – the External ID is required. On its own, it may not be unique, but uniqueness is ensured in combination with the PalDock Advertiser ID.
If the pairing does not match any waiting webhook, the advertiser will receive the following response:
- {“code”:404,”message”:”Waiting Webhook not found for provided token and identifiers”}
