Parsing Webhook Responses in Trackdrive

Where Response Parsing Lives

Outgoing webhooks, buyer conversions, and shared response
parsers all use the same response parsing UI. The form fields
you will see in any of these screens are:

• Was The Response Acceptable? A condition that decides whether the partner's HTTP response counts as a success. This drives retry behavior and conversion tracking.
• Extract Value From Response Body: A regex, JSON path, or XPath expression that pulls a value out of the partner response body. The extracted value is then available to downstream logic.
• Check If Response/Extracted Value Contains: A substring or pattern test on either the raw response or the extracted value. Combined with "Was The Response Acceptable?", this lets you treat a 200 response with a body of {"status":"rejected"} as a failure.

Where to Find These Fields

The same three fields appear in:

• Outgoing webhook URL configuration.
• Buyer conversion webhook configuration.
• Standalone response parser records reused across multiple webhooks.

Editing them in any one place affects only that webhook;
response parsers are the abstraction to share parsing logic
across many webhooks at once.