Run Foursquare from Your Dealership CRM

Location measurement and visit built audiences, and a plain account of where that connection stands.

Foursquare is not primarily an advertising network, and a store should understand that before asking us to connect it. It is a location technology company. It maintains a places database that names and shapes the physical world, a set of developer tools other companies build products on, and a measurement business that infers whether a person who saw an ad later walked into a specific building.

The measurement half is the part that touches automotive. When a vendor tells a dealership that a display campaign produced a lift in showroom visits, the visit signal underneath that claim very often originated with a location data company, and this is one of the largest. Audience segments built from observed visit patterns are sold into most major demand side platforms as well, so a store can buy a targeting segment shaped by where people have physically been rather than by what they typed into a search box.

The practical framing for a dealership is that this is the ruler rather than the channel. You do not run a campaign here the way you run one on a search engine. You buy media somewhere else, then use this class of data to describe who should see it or to grade what happened afterwards.

The argument is that a car is bought in a building. Almost every measurement in digital advertising counts something that happened on a screen, and a store's actual moment of truth is a person standing on the lot. A data source that speaks in visits rather than clicks maps closer to how a dealership earns money than any click metric ever will.

The audience side has a similar appeal. A segment of people observed at competing rooftops, at service drives, or at the credit union across town describes intent in a way keyword targeting cannot reach, and because those segments push into most major demand side platforms they sit next to display and video buying a store may already run.

The honest objection is sample and scale. Visit measurement is modelled from a set of devices that opted into location sharing, not from a census of everyone who walked in. At a national advertiser spending heavily across many markets, the model has enough observations to be directionally useful. At a single rooftop selling a couple of hundred units a quarter, the visit counts land small enough that ordinary noise swamps the signal, and a lift figure computed on a thin sample can be read to mean nearly anything you want it to mean.

The second objection is what a lot looks like from above. Dealership parcels sit beside other businesses, sometimes share a driveway with them, and usually front a road carrying constant traffic. Resolving somebody to your building rather than to the restaurant next door is genuinely difficult, and a visit is not a test drive and certainly not a sale. Our page on geofencing advertising for dealers covers the buying side of the same idea, and it is the more useful read if what you actually want is traffic rather than proof.

Not started, and the published test for that status is one you can hold us to: no adapter file exists in the ad gateway for this platform. No authorization URL, no credential block, no wire-up checklist, and no half written code sitting behind a badge. It is catalogued, which is a different word from connected, and this directory keeps the two apart deliberately.

That distinction changes what a request is asking for. On a registered platform the adapter and its checklist already exist and the open question is scheduling. Here the adapter itself would be the first piece of work, so demand is the entire mechanism rather than a tiebreaker between things already queued.

Access class is PARTNER, and that gate belongs to the vendor rather than to us. Credentials arrive through an application the vendor reviews, and a location data business reviews those with data licensing terms and privacy obligations in front of it, which is slower and more selective than registering an ordinary developer account. That step sits ahead of the engineering however many stores ask, and naming it is more useful to a dealer than implying everything is one sprint away.

Written as a design for something that does not run, so nothing here is mistaken for a description of current behaviour.

Read the last row twice on this page in particular, because a measurement platform is the one place a dealer would reasonably expect a customer list to travel outward for matching. It would not. The lead records themselves stay where they are, inside the CRM, and no export exists that would change that.

A platform we have not built can still be described precisely, because the thing it would join is fixed and already carrying traffic. What is unusual here is that a measurement source does not fit the shape neatly, and that is worth saying before describing the shape.

One library inside LeadLocate defines what any advertising platform must be able to do: hand us an authorization URL, exchange the credential for a usable token, list the accounts that credential reaches, 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. A new platform is that one file written against those seven, which is why a request asks for a defined piece of work rather than an investigation.

Foursquare would answer perhaps four of the seven honestly. There is no campaign to deploy and nothing to pause, so an adapter here would be mostly authorization, account listing, reporting and verification, with two operations returning a refusal that names the reason rather than pretending. That is a design decision worth publishing, because a store comparing entries in this directory deserves to know that not every platform in it is the same kind of animal.

Credentials are encrypted with AES-256-GCM before storage. Every action against any network is written to an append only audit log carrying the company, the network, the user and the detail, timestamped in UTC because the table is shared across dealerships and a company local timestamp cannot be reconciled later. Campaign objects record which credentials created them and re-resolve those same credentials afterwards, so disconnecting an account never strands the work built beneath it.

There are two ways to advertise through LeadLocate and the store picks.

The first is the webXintel Ads Network: included, built and operated by our team from the selections you make in Leads Manager, and billed as one line rather than a stack of platform statements. Nothing to apply for and no credential for you to hold.

The second is your own account. Connect the advertiser account your group already holds and campaigns route through it, on your billing, in your name, with your terms and spend history intact. For this platform neither path exists today, because there is no adapter and the vendor gate has not been approached.

One limit that holds across the whole gateway and is worth stating plainly: deploying, activating, pausing and reading spend is done by our team rather than from a control on your dashboard. That is a deliberate constraint while the connection layer is young, and it is on the list to open up rather than something already in the product.

Four steps, and only two of them are ours. A request from a store that would actually fund the measurement. A queue position earned against every other request in the catalogue. An adapter written against the operations that apply, with a credential block and a verification path. And a vendor reviewed application for access, on the vendor's clock and subject to the vendor's licensing terms.

There is a fifth step that is not technical at all, and it decides whether the other four are worth taking. Visit measurement only reads cleanly when the media underneath it is large enough and long enough to move a number. A two week flight in one town, at a budget a single rooftop can carry, will usually produce a result that is not distinguishable from nothing. That is not a criticism of the platform. It is arithmetic, and a vendor that lets a store spend into it without saying so is doing the store a disservice.

On timing, this is a slow instrument by construction. Visit signals accumulate over a flight and are typically reported after a lag rather than the same afternoon, so nothing here answers a Monday morning question. If your question is where the next thirty leads come from, read what to expect from car sales leads instead and buy a direct response channel.

Nothing is connected, so the gaps have to be listed rather than softened.

We have never made a call to this platform. No adapter file, no credential, no verification, no deployment, and nothing partially written waiting to be finished.

We do not operate a mobile application or a location SDK, and we do not collect device location from shoppers anywhere in the product. Everything this platform observes, it observes through its own panel and its own partners, not through anything of ours.

We do not upload offline conversions and we do not run a server side conversions API. That gap matters more here than on most pages, because closing the loop between a visit and a sold unit is exactly what a store would want from this category, and the mechanism that would do it is not built.

We do not export a hashed customer list for audience matching, suppression or measurement panels, so audience work built from your own database is not available through us.

We do not emit a vehicle catalog or an inventory feed to this or any advertising platform, and we do not install or manage pixels of any kind.

We do not deploy or manage geofences. If a vendor has quoted you a showroom visit lift number, ask which panel produced it and how many devices it saw. We cannot produce that number, and we would rather say so than imply we can.

Ask by name, attach the rooftop, and say what you are trying to prove rather than which vendor you want bought. Requests are recorded against the platform they name and the tally sets build order, because a dealer with a budget and a real question is a better signal than any internal ranking exercise.

Two things make a request in this category stronger. Say how much media would sit underneath the measurement, since a measurement layer over a small buy answers nothing. And say whether you already hold a relationship with the vendor, because a partner gate you have already cleared removes the one part of the timeline nobody on our side can influence.

In the meantime the managed path runs today and waits on none of this. Platform pricing sits on the pricing page and does not vary with which networks you turn on.

Does LeadLocate integrate with Foursquare today?

No. The status is not started, and its published test is that no adapter file exists in the ad gateway for this platform. There is no credential, no checklist and no partial code, and the request count is what decides whether that changes.

Can I use my own Foursquare account?

Not through the CRM. Nothing has been written on our side, and access here is partner gated, so credentials come through an application the vendor reviews under its own licensing terms. Holding an existing relationship would remove the vendor half of that answer but not the engineering half.

What happens if I request Foursquare?

It is recorded against this platform by name and counted, and the count feeds build order across the catalogue. A person answers you with a range or a reason rather than silence. Requests that name a media budget large enough to measure carry more weight.

Can you prove my advertising brought people to the lot?

Not today, and be careful with anyone who says they can. Visit measurement is a model built on a panel of devices that opted into location sharing, not a count of everyone who arrived. On a single rooftop budget the result is often indistinguishable from noise.

Is a store visit the same as a lead?

No, and treating it as one is the most common mistake in this category. A modelled visit is a probability that a device crossed a parcel boundary. It is not a name, a phone number, a test drive or a deal, and it cannot be worked by a salesperson.

Does LeadLocate track where my shoppers go?

No. We operate no mobile application and no location SDK, and we collect no device location anywhere in the product. Any location signal in this category comes from the vendor's own panel and partners, which is one reason the vendor gate exists at all.

Requests are recorded against the platform they name and the tally sets build order. Send your rooftop, the media budget sitting underneath, and the question you need answered.