Trackdrive + VICIdial: calls and leads

When teams ask us for this

You buy insurance or legal calls

Trackdrive traffic lands in a VICIdial in-group, on your agents, with the tokens attached if you route over SIP.

You buy leads from the same platform

The lead path posts to an endpoint that calls add_lead, DNC-checked on arrival.

You need the traffic source on the screen

Trackdrive tokens travel as SIP headers and are read in the dialplan before the agent is connected.

You need to reconcile against invoices

Trackdrive's call or lead identifier is written into VICIdial at creation.

Trackdrive does call tracking and lead distribution, and shows up constantly in insurance and legal buying. Like Phonexa it spans both sides, so "integrate Trackdrive" is really two jobs on one account.

Integrations on demand. We are not a Trackdrive partner and there is no connector to enable. Our team wires it as scoped work, quoted per setup.

Calls

Trackdrive routes a bought call to a destination you nominate. Point it at a SIP address or a DID on your VICIfast box and it lands in a VICIdial in-group.

Take SIP if the agent needs context. Trackdrive holds tokens about the caller - the offer, the publisher, the traffic source - and a SIP delivery can carry them as headers for the dialplan to read with PJSIP_HEADER(read,...). A DID delivery carries the caller ID and nothing else.

Leads

Trackdrive posts the record to a URL you nominate. That endpoint translates it into a non_agent_api.php call with function=add_lead, writes Trackdrive's own identifier to vendor_lead_code, and scrubs against DNC on arrival rather than at dial time.

Setup

Provision the in-group for calls, the list for leads, or both.
Create the SIP endpoint or DID, and the posting endpoint, as applicable.
Configure the destination and the lead delivery in Trackdrive.
Agree which tokens travel and under what names.
Map tokens to VICIdial fields.
Test both paths with live traffic before switching volume on.

It also runs the other way

Everything above is traffic arriving. The dialer can call Trackdrive as well: VICIdial fires their API mid-call with the lead substituted into the URL, and the caller is transferred live if Trackdrive accepts. Common in legal and insurance, where the qualifying call is yours and the transfer is the product.

A transfer accepted during the conversation is worth considerably more than a record posted after it, and it is a separate piece of work from the inbound path. See live transfer on a buyer API response for the hooks and the failure modes.

Gotchas

Token names drift. A renamed token in Trackdrive silently produces an empty field on the agent screen rather than an error.

Their timeout and your ring time are different clocks. If your in-group rings past Trackdrive's timeout, the call is marked failed and may be routed to another buyer mid-ring.

Concurrency caps belong on their side. Set the cap to what your floor answers, not what your trunk carries.

One identifier, end to end. Write Trackdrive's call or lead ID into VICIdial at creation. Reconciling an invoice without it is a manual search through timestamps.

Questions we get asked

Are you a Trackdrive partner?

No. There is no certified connector. We wire it to your server as scoped work, quoted per setup.

Calls or leads - which do you wire?

Either or both. They are separate jobs on the same account and are tested independently.

What happens when a token is renamed?

The dialplan reads an empty string. Nothing errors; the agent screen is simply blank where the value used to be. Token names need to stay stable.

Can Trackdrive route a call away mid-ring?

Yes, if your in-group rings past their timeout. The call is marked failed on their side and may go to another buyer while your agent is still being alerted.

Where should the concurrency cap live?

On Trackdrive's side, set to what your floor can answer rather than what your trunk can carry.