MGID Integration for Car Dealers

High volume native traffic at the lowest entry cost in this family, and the honest state of the connection.

MGID sells native recommendation placements on publisher pages, the same physical unit as the larger networks in this family but drawn from a different and broader publisher pool. Its distinguishing features for a dealership are a documented REST advertiser API and a minimum deposit of one hundred dollars, which is the lowest commercial floor of any network in this directory.

That combination decides what the platform is good for. It is a traffic instrument. You write a headline, you attach a thumbnail, you point the click at a page, and you buy volume by the click across a wide spread of sites. There is no query to match, no shopper graph, and no form inside the ad.

For a single rooftop independent, the practical read is that this is the cheapest way to find out whether a landing page and an offer can convert cold traffic at all. That is a genuinely useful thing to learn before spending real money on channels where the clicks cost ten times more, which is why it earns a place in a dealership advertising plan rather than being dismissed as bargain inventory.

The argument is arithmetic. A hundred dollar deposit and a documented API mean the cost of finding out is close to zero. For a sale event, a service promotion, a lot clearance or a new store announcement, this network will put more clicks on a page per dollar than anything else on this catalogue, and it will do it the same day.

The objection is quality, and it should be stated bluntly rather than managed. Cheap traffic is cheap because the publisher pool is wide, and a wide pool contains sites you would not choose individually. Some placements deliver curious readers, some deliver accidental taps, and the difference between the two only shows up in source level reporting. Running this network well means reading the source report and blocking placements every few days, permanently. A store that sets it and forgets it will buy a lot of clicks and very few people.

The second objection follows from the first. Because the raw click number looks impressive early, this is the easiest channel in the directory to feel good about while achieving nothing. The KPI has to be leads on the landing page and appointments in the CRM, never the traffic graph. Our page on what to expect from car sales leads applies with force here.

Registered, not yet built, and the test for that status is published so it can be checked: an adapter file exists in the ad gateway with a written wire-up checklist, committed and scoped. This one carries five steps.

Authentication is the simplest in this family, a straight API token issued from the advertiser dashboard. There is no consent redirect and no exchange dance, which removes an entire class of work and an entire class of failure from the build. It also means the credential is long lived, so the way it is stored matters more than it would on a network with rotating access tokens.

Access class is PUBLIC. Nobody reviews an application before issuing you credentials, and there is no partner tier standing between a dealership and its own account. Combined with the hundred dollar deposit, that makes this the network with the fewest external obstacles anywhere in this directory. What is missing is our code, and saying so is the entire point of publishing a status instead of a logo.

A design, not a description, because none of it runs today.

The source level reporting row is the one that matters most on this network specifically, because placement blocking is how the channel is made to work. Lead capture is clickout: no form in the unit, so the opt in happens on your page using forms that already live in the CRM.

This platform is not wired in as a one off. It answers the same contract as every other network in the CRM.

A single library defines the operations any advertising platform must support: hand us an authorization URL, exchange the credential for a usable token, list the accounts the 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. That is why this is a five step checklist rather than an open ended engineering effort, and why completing it cannot disturb the one network that already works.

Because the credential here is a long lived token rather than a short lived grant, encryption at rest is doing real work. Tokens 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 the credentials that created them and re-resolve those same credentials afterwards, so disconnecting an account never strands the campaigns built beneath it.

Two routes, and you choose.

The first is the webXintel Ads Network. It is included, our team builds and operates the campaigns from the selections you make in Leads Manager, and it bills as a single line instead of a stack of platform statements. No credential to generate and no deposit to fund.

The second is your own advertiser account. Connect the account your store already holds and campaigns route through it, on your billing, in your name, with your deposit and your spend history intact. On a network where the deposit is a hundred dollars, that route is realistic for almost any store, which is not true everywhere in this catalogue.

One boundary stated plainly: deploying, activating, pausing and reading spend is done by our team today, not from a control in your dashboard. That is a deliberate limit while the connection layer is young, and removing it is on the list rather than in the product.

Five ordered steps. Generate an API token from the advertiser dashboard. Fill the credential block and enable it. Implement account listing and the campaign creation call. Implement budget updates and status changes. Implement reporting, including placement level breakdowns, and the verification call.

The reporting step deserves more weight here than on a comparable network, because placement level data is not a nice extra on this platform, it is the control surface. A build that returned only campaign totals would technically satisfy the contract and would leave the channel unmanageable.

On timing, clicks arrive within hours of a campaign going live. Meaningful lead counts take longer than on the premium networks, generally two to five days, because a wider publisher pool needs more volume before the pattern separates from the noise. That is a statement about how quickly the channel becomes readable, not a prediction of how many leads a store will get, and nobody can honestly give you the second one.

The commercial floor is a hundred dollar deposit rather than a daily minimum, which changes how a test should be planned. Fund it once, run until the placement report has enough rows to act on, and decide before you start what result would make you stop.

The specific gaps, named rather than implied.

We do not emit a vehicle catalog or an inventory feed to this network. No code in our stack generates a product feed for any advertising platform, so vehicle level dynamic native units are not something we deliver here.

We do not run a server side conversions API. This platform supports one and we have not built it. No server side conversion events, no offline conversion upload, and no pixel installation or management. On a clickout channel with a wide publisher pool, that means your landing page and your CRM record are the measurement, and you should size the test accordingly.

We do not export a hashed customer list for matching or suppression, and none of the five steps would create one.

We do not filter or grade the traffic you buy. Placement quality on this network is managed by reading the source report and blocking placements, and that is human work on a schedule, not an automatic quality layer we sell you.

No campaign has ever been deployed here from the CRM, because the code that would do it does not exist yet.

Ask for it by name, with your store and the offer you would run first. Requests are recorded against the platform they name, and that tally is what sets build order, because a dealer with a budget is a better signal than an internal opinion about which logo looks best on a slide.

This network has an unusual argument in the queue. It is the cheapest place in this directory to answer the question every store should answer before it spends seriously anywhere: does my landing page convert a cold click at all. If that is the question you have, say so, and say it that way, because it changes what we would build first and what we would tell you to run.

The managed path is live today and waits on none of this. Platform pricing is on the pricing page and does not vary with the networks you enable.

Does LeadLocate integrate with MGID today?

No. It is registered in the ad gateway with a five step wire-up checklist and no working lifecycle methods behind it. Every call the adapter receives returns a refusal that names the network, so nothing in the CRM can imply a link that is not there.

Can I use my own MGID ad account?

Not through the CRM yet, because the self connect half is unbuilt. Nothing on the vendor side is in the way. The token is issued from the advertiser dashboard with no approval queue, and the deposit is a hundred dollars, so the only obstacle is our code.

What happens if I request MGID?

It is recorded against this network specifically and counted, and the count is the input to build order among the registered adapters. A person replies with a range or a reason. If it sits behind larger networks in the same family, you will be told that plainly.

Is the traffic any good?

It is wide rather than pre-selected, and it becomes good through management. Read the placement report, block the sources that produce taps instead of readers, and repeat every few days. A store unwilling to do that work should spend its money on a narrower channel instead.

How long before the numbers mean anything?

Clicks appear within hours. Lead counts usually need two to five days to separate from noise, because a broad publisher pool takes more volume to read than a premium one. Judging this network on a single day of data will produce the wrong conclusion in either direction.

Does the hundred dollar deposit cover a whole campaign?

It is an account funding minimum, not a campaign budget. It gets the account open and buys a real first sample of clicks. What it will not do is deliver enough volume to compare several headlines across several placements, so plan the second deposit before the first one runs out.

Requests are counted against the platform they name and the count sets build order. Tell us your store and the landing page you want to put under real traffic.