A Webhook or Action Didn't Do What I Expected

Integrations

When a webhook sent the wrong data, a receiving platform didn't record a call, or an action such as Mailchimp didn't do what you expected, start by seeing what Trackdrive sent and what came back. This article walks through the causes, most common first, and where to check each one on your own screens.

The Receiving Platform Rejected the Request

What you see: the other platform has no record of the call or lead, or shows it without the values you expected.

Where to check: open the call and go to its Webhook Logs tab, or open Webhook Logs under Reports to see the logs of every call. Each log shows the request Trackdrive sent, with its URL and Request Body, the Response Code, and the Response Body the other platform returned.

The fix: read the response. A response code in the 400s with a message about a missing or invalid field means the request needs that field, which you add to the webhook's URL or body. A code in the 500s, or a timeout, is a question for the receiving platform.

Example: a postback returns 404 with an empty body because the URL points at a path the other platform no longer serves. Correcting the URL on the webhook makes the next calls arrive.

A Token Went Out Blank

What you see: the other platform reports a value as missing, and the request on the Webhook Logs tab shows an empty spot where a token such as a click id or partner token should be.

Where to check: compare the request on the call's Webhook Logs tab with the values the call holds. On the call's Call Overview, the Contact Fields section lists the call's fields and tokens.

The fix: a token the call has no value for is sent blank. If the Contact Fields section doesn't show the token, check that the token's name in the webhook matches the name on the call. If the call holds the value but the request sent it blank, contact Trackdrive support with the call's id and the time the webhook fired.

Example: a postback URL ends with a partner's webhook token, and on a few calls the log shows the URL with that part empty while the call's Contact Fields section shows the token. That is a case for support.

A Mailchimp Action Sent No Email

What you see: an Add To Mailchimp Audience action ran on a call or lead, but the person never received an email.

Where to check: open the call and read its Call Logs, or the lead's logs when no call fired the action. A line saying Mailchimp added the email address to the audience means the action did its job. A line saying Mailchimp refused to add it gives Mailchimp's reason, and when a call fired the action, the request and Mailchimp's reply show on the call's Webhook Logs tab.

The fix: the action adds the lead's email address to the Mailchimp audience chosen in the action's List, and sends no email itself. Send the email from Mailchimp, with an automation or journey that starts when someone joins that audience.

Example: a schedule's Mailchimp action adds each new lead to a welcome audience, and nothing in Mailchimp emails new members. Adding a welcome journey for that audience in Mailchimp sends the email.

A Mailchimp Action Was Skipped on a Re-Test

What you see: the log says the action skipped adding the email address because it already ran for this lead or call within 24 hours, and names when it may run again.

Where to check: the same log line on the call's Call Logs, or the lead's logs.

The fix: each Mailchimp action runs once per lead in 24 hours, or once per call when a call action or a call disposition fires it. To test again, use a fresh lead or call, or wait until the time the log names.

Example: a tester places a call, applies the disposition that fires the action, and applies it again a minute later to test a change. The second time the action is skipped, and a new test call runs it.

Calls Didn't Reach Google Ads

For calls that didn't upload as Google Ads conversions, see "How the Google Ads Integration Works (After Setup)".

When to Contact Support

If none of these explains it, contact Trackdrive support with the call's id and the time the webhook or action ran.

Contact TrackDrive

Questions?

We're here to help. Reach out and a Voice Marketing Cloud Specialist will get back to you.

Email support@trackdrive.com
Request A Demo

Request A Demo.

See how you can improve your marketing and the customer experience with the Voice Marketing Cloud.

Request a demo