Mon - Sat: 9:00 AM - 6:00 PM
Call: 844-376-2274
Advertising Integrations
AdQuick Integration for Dealerships
Printed and digital outdoor bought at supplier direct pricing, with attribution attached, and where the CRM fits.
LeadLocate does not connect to this platform today, and the request queue is what decides when it gets built. No adapter file for AdQuick exists in the ad gateway, and its credentials sit behind an application the vendor reviews first. The directory publishes the test behind each status word so a dealer can check the claim rather than take it.
What AdQuick actually is, in dealership terms
AdQuick is a buying and planning platform for the whole of outdoor advertising rather than one slice of it. Printed billboards, digital roadside boards, transit, street furniture and programmatic screens all sit in the same inventory search, priced from suppliers directly rather than through a chain of resellers. A buyer can compare a vinyl board on a highway against a digital loop downtown without opening two relationships.
The part that distinguishes it from the rest of this family is measurement. The platform attaches attribution to an outdoor buy using mobile location data, so a campaign report attempts to say how many people exposed to the board later visited a location or reached a website. That is the thing outdoor has always lacked, and it is the reason a dealership would consider this platform over the vendor with a territory and a rate card.
The self serve entry point is low enough for a single rooftop to run a programmatic test, while the planning side is built for buyers spending at a scale a dealer group would recognise. Both doors lead into the same inventory.
Why a dealership would spend money here
The case is comparison shopping and accountability in a category that historically offered neither. A store gets to see what a board actually costs from the supplier, run classic and digital side by side, and receive a report at the end that tries to connect exposure with a visit. For a dealership that has been quoted a rate card by one vendor and had no way to sanity check it, that alone is worth the account.
The honest objection is what the attribution actually is. Location based outdoor measurement is modelled from mobile panel data, which means a sample is observed, matched against exposure areas and extrapolated. It is a genuine improvement on nothing and it is not a receipt. Two vendors measuring the same flight will not produce the same figure, and a dealership that treats a modelled lift number as if it were a conversion count is going to make a bad renewal decision.
The second objection is printed outdoor specifically. A vinyl board has production lead time, an install window and a commitment measured in weeks, so it cannot answer a weekend event and cannot be turned off when the offer changes. That is not a flaw in the platform, it is the physics of the medium, and it belongs in the decision. Where a store needs speed and a countable response, a channel like geofencing answers a different and more immediate question.
Where AdQuick stands with LeadLocate today
Available on request. The published test for that status is that the work is not started and demand decides the order, and there is nothing on our side that softens it. No adapter file exists for this platform in the ad gateway, no credential block is defined for it, and there is no authorization URL or wire up checklist waiting behind a flag.
The access class is PARTNER, which describes the vendor's gate and not ours. Credentials require an application the vendor reviews before issuing them. That is a normal position for a platform whose supply relationships are contractual, and it is worth separating from the advertiser experience, which is comparatively open. Buying is one door, building against the platform is another, and only the second one is what this page reports on.
So the sequence has two parts and we own one. The engineering is scheduled by the request tally. The credential is approved on the vendor's timeline. A date printed on this page would be an invention about the half we do not control, which is why the directory gives you a status and a test instead of a promise.
What data would move, and in which direction
A design rather than a description, because none of it exists yet.
| Direction | What would move |
|---|---|
| Out to the platform | Campaign structure, the markets and unit types selected around the store, budget and flight dates, and the artwork assigned to each format |
| Back from the platform | Units booked, delivery and spend, estimated impressions and the platform's own attribution report, plus the accounts a credential can reach |
| Stored on our side | An encrypted credential, a record of which objects were created and by which credentials, and an append only event log |
| Never moves | Your customer list, your inventory feed, and any hashed audience file built from either |
The second row is the interesting one on this platform, because it is the only one in this family that would carry an attribution report back. It is still a modelled report rather than a lead, and the CRM would hold it as a spend and delivery record next to the channels that produce contactable names.
How the ad gateway works underneath
This page can be specific about an unbuilt platform because networks are not added here as one off projects. A single provider agnostic library inside the CRM sets out what any advertising platform must be able to do: hand us an authorization URL, exchange the code for a token, list the accounts a credential can reach, deploy a campaign, pause or resume it, return spend and results, and prove on demand that the connection still works.
Seven operations, one adapter file per network, and each network answers the identical seven. Twenty networks are registered against that contract and exactly one is implemented. The nineteen that are not return a refusal naming themselves, so a stray call fails readably rather than looking like a vendor outage. AdQuick is not among the twenty, which is why this page carries the weakest status word rather than the middle one.
The plumbing beneath the adapters exists already and would not be rebuilt for a new network. Credentials are encrypted before storage using AES-256-GCM. Every action taken against a network is written to an append only audit log carrying the company, the network, the user and the detail, stamped in UTC deliberately, because those tables are shared across dealerships and a timezone relative timestamp cannot be reconciled after the fact. Campaign objects record which credentials created them and re resolve those credentials later, so a disconnected account never orphans the work built under it.
Managed by us, or connected to your own account
Two routes, and the store picks one. The first is the webXintel Ads Network: included, built and operated by our team from the selections you make in Leads Manager, and invoiced as one line rather than a pile of platform statements. It is live today and nothing here gates it.
The second is your own account. Where a network has been built, you connect the account your store already holds, campaigns route through it, and the billing, the naming and the spend history stay with you. Disconnect and delivery falls back to the managed route.
Neither route reaches AdQuick today. That said, this is a platform a dealer group can open an account with directly, and if the immediate need is to price a board honestly against a rate card you were handed, doing that yourself is faster than waiting for anybody's roadmap. An integration would add the flight and its spend to the same view as the rest of your advertising, which is a reporting benefit rather than an access one.
The constraint that applies across the whole gateway, said on every page in this directory: pushing, pausing and reading numbers from a network is done by our team, not from your dashboard. It is a deliberate limit while the connection layer is young, and it is on the list to open up.
What building this would take, and when you could measure it
Two tracks, and only ours is predictable. The vendor track is an application and a review before credentials are issued. Our track is an adapter file written against the seven operation contract, a credential block added and enabled, then each of the seven operations implemented and verified against a live account.
Measurement here deserves more care than on the rest of this family, precisely because this platform offers a number. Outdoor results are not reliably attributable inside a day, and a modelled lift figure delivered a fortnight later is evidence rather than proof. The disciplined way to run it is to fix the question before the flight: which markets, how many units, what share of the trade area's drive time, what cost per thousand, and what you expect direct traffic and inbound calls to do over the following month.
Then treat the platform's attribution as one input beside your own numbers rather than as the verdict. That is a statement about how a channel produces information, not a forecast of lead volume or closing rate, and the general version of that argument is on what to expect from car sales leads.
What we will not claim about AdQuick
The specific gaps on this platform, one at a time.
We do not retrieve leads from this platform. Lead form retrieval in our stack is written for exactly one network and this is not it. Outdoor collects no opt in in any case, so a flight booked here would arrive in the CRM as spend and delivery rather than as a lead source.
We do not run offline conversion upload, and we do not operate a server side conversions endpoint. That matters more here than elsewhere in this family because attribution is the platform's differentiator. Its measurement is produced by the vendor from its own data. We do not send it your sold units, your service visits or any other outcome file to sharpen that model.
We do not install or manage a pixel. Any site side measurement on your website is whatever you already had.
We do not emit a vehicle catalog. Nothing in our stack generates a unit level feed for any advertising platform, so creative here is your store and one message, not rotating stock.
We do not upload hashed audiences. No customer list becomes a targeting segment anywhere.
No campaign has ever been deployed to AdQuick from the CRM, because no code exists that could send one.
If you want AdQuick on your store
Ask, with your store attached, and say whether the interest is classic outdoor, digital, or the attribution reporting. Those are three different requests wearing one vendor's name, and the third one changes what a build would have to carry back into the CRM.
Requests are recorded against the platform they name and the tally is the input to build order, because a store ready to spend on a channel outranks any roadmap meeting. A person replies with a range or a reason.
Meanwhile the managed route runs today and waits on none of this. If the real question is how outdoor sits alongside everything else a store buys, car dealership advertising lays that out, and pricing for the platform is on the pricing page and does not move based on which networks you turn on.
Frequently Asked Questions
Does LeadLocate integrate with AdQuick today?
No. The status is available on request, whose published test is that the work is not started and demand decides the order. There is no adapter file, credential block or wire up checklist for this platform in the ad gateway.
Can I use my own AdQuick account?
Not through the CRM, since nothing exists to reach it. You can open an account with the vendor directly, and for a store that mainly wants supplier direct pricing to check a quote against, that is the faster path today.
What happens if I request AdQuick?
It is recorded against this platform specifically and counted, and the count feeds build order. A person replies with a range or a reason. On this platform expect a question back about whether you want printed units, digital units or the attribution reporting.
Is outdoor attribution the same as tracking a lead?
No, and the difference matters. Location based outdoor measurement observes a mobile panel, matches it against exposure areas and extrapolates. It is a modelled estimate of lift, not a record of an individual who contacted your store, and it should be read as one input rather than as a verdict.
Would you send my sales data to improve their measurement?
No. We do not run offline conversion upload of any kind, to this platform or any other. Whatever attribution the vendor reports is built from the vendor's own data, without an outcome file from us.
Should a single rooftop buy printed billboards?
Sometimes, but understand the trade. A vinyl board needs production time and an install window and holds for weeks, so it cannot answer a weekend event or follow a changing offer. Digital units inside the same platform are the flexible half, and most single store buyers should start there.
More Resources from LeadLocate
Price a board against the quote you were given
Requests are counted against the platform they name and the tally decides build order. Tell us your market and whether printed, digital or measurement is the point.


LeadLocate™ All rights reserved. Other product and company names mentioned herein are the property of their respective owners.
Answers to your questions:
LeadLocate is an all-in-one lead generation software and CRM platform. We generate in-market sales leads and provide you with all the tools necessary to sell that customer. All of your leads, texts, calls, emails, deals, and files are available in one place, accessible with a single login.
LeadLocate™ All rights reserved. Other product and company names mentioned herein are the property of their respective owners.
Answers to your questions:
LeadLocate is an all-in-one lead generation software and CRM platform. We generate in-market sales leads and provide you with all the tools necessary to sell that customer. All of your leads, texts, calls, emails, deals, and files are available in one place, accessible with a single login.



