TrackDrive on your landing pages
TrackDrive is good at the part after the dial: picking the buyer, pricing the call, checking caps and hours and deciding if it converted. All of that works better when the call arrives with something to go on. A number swapped onto a page with no qualification and no tokens gives TrackDrive a phone number and a time stamp.
A LanderLab page gives it more. The quiz asks what buyers filter on and sends the wrong callers elsewhere, the click's UTMs and gclid stay on the URL, and TrackDrive's optimizer script in the page's custom code shows a pool number and stamps all of it on the call as tokens. Visitors who fill the form instead of dialing aren't lost either: the page's webhook posts them to TrackDrive's Leads API, where a schedule can call them back. TrackDrive then sends each caller to the buyer who pays the most for exactly that caller.
Pay-per-call routing with TrackDrive
With TrackDrive's number on a LanderLab page, the calls the page drives are tracked in TrackDrive and routed to your buyers by the rules you set there. The page brings the caller, and TrackDrive decides where the call goes and records how it went.
Each visitor's number comes from a Number Pool tied to an Offer, held for that visitor's session and then freed for the next one. The call record carries the session's attribution, so you can see which traffic source, campaign and landing page produced each converted call.
A bid on every call
TrackDrive runs ping/post for calls: buyers bid on a call before it connects, and the caller goes to the one who values it most. Instead of one flat rate for every call, each call can sell at the best price on offer at that moment.
Always-on buyers at a fixed price compete in the same auction as buyers who return a live bid on every ping. A call that arrives with the state and the answers buyers care about is a call more of them can bid on.
Calls matched to buyer hours, caps and geography
You paid for the click that made the phone ring, so the call has to reach a buyer who can take it. TrackDrive matches each call on the buyer's hours, caps and geography and can screen out duplicates, so a caller doesn't land on a closed office, a buyer who is full for the day, or one who won't pay for a repeat caller.
Quiz answers as TrackDrive tokens
TrackDrive's script sends the page's query string with the number request, and custom tokens set on the pool are captured too. With LanderLab's Forward URL Parameters and Include Quiz Data on, the answers reach the call page's URL and land on the call as tokens.
That turns your quiz into routing. An auto insurance buyer who only wants Ohio drivers with two or more vehicles gets those callers, while the rest go to buyers who pay for them, and fewer of the clicks you pay for end in a call with nowhere to go.
TrackDrive callbacks for visitors who fill the form
Some visitors would rather type than dial. The page's webhook can post each of those leads to TrackDrive's Leads API under your offer's lead token, with the answers and the UTMs as data that TrackDrive turns into tokens. Inbound and outbound calls with that lead inherit the tokens, so a callback is routed and reported like any other call.
From there TrackDrive's Lead Automation can send a text and an email, wait, then call the lead and route the conversation to a buyer. A quiz page can run both paths at once: the number for people ready to call, the form for everyone else.
