Beeswax Integration for Car Dealers

A bidder you configure rather than a platform you rent, and why that distinction decides the whole question.

Almost every advertising platform a dealership has ever used is a finished product. You log in, you choose a radius and a budget, and somebody else's software decides what to bid on each impression. Beeswax is the layer underneath that. It is a bidder you configure, where the buying logic itself is the thing you are buying.

In practice that means a customer defines their own bidding rules, brings their own data to score an impression with, and runs a buy that behaves the way they specified rather than the way a packaged platform's optimizer decided. The reason products like this exist is that at large enough volume, the difference between a generic optimizer and a bidder tuned to a specific business is worth real money.

Stated in dealership terms: this is not a channel. It is machinery for buying the same open web display, video and streaming supply that a packaged demand side platform buys, with the decisions moved to your side of the line. It sits behind programmatic display rather than beside it.

The honest case is narrow and worth stating precisely, because a vague case would be flattering and useless. A bidder is the right choice only when the buying logic itself needs to belong to the buyer rather than be rented. That is true for a handful of very large automotive groups and for vendors operating media on behalf of many stores at once, where a single percentage point of efficiency across a large spend pays for the whole apparatus.

The objection is everything else. A configurable bidder is infrastructure, and infrastructure has a staffing cost that does not appear on the media invoice. It wants engineering time, an ad operations habit, someone who reads log level delivery data and a spend base large enough that tuning is measurable rather than superstition. A three rooftop group running a modest monthly display budget will pay for all of that and be unable to detect the benefit, because the sample size will not support the conclusion.

There is also a quieter objection. When the buying logic is yours, the results are yours too, including the bad ones. A packaged platform at least gives you a competent default. A bidder configured badly will spend a dealership's money with great precision on the wrong impressions, and the failure will look like a channel problem rather than a configuration problem. That distinction is worth understanding before anyone signs.

Available on request. The published test for that status is that the work is not started and demand decides the order, and that is exactly the position here. No adapter file exists in the ad gateway for Beeswax. There is no credential block, no authorization URL, no wire up checklist and no partially finished branch waiting to be turned on.

The access class is CERTIFIED. That is the vendor's gate rather than ours: a contract, a certification or a minimum spend is required before API access is granted. For a product of this kind the gate is not a formality either, because the vendor is selling operating infrastructure to customers it expects to have technical staff, and the qualifying conversation reflects that.

So there are two separate locks on this door. Ours is engineering that has not been scheduled. Theirs is a commercial agreement that we cannot clear on a dealership's behalf. Both would have to open, in that order, and the second one is not on our timeline.

Written as a design rather than a description, because none of it runs and pretending otherwise is the exact failure this directory was built to avoid.

The fourth row is the interesting one on this page specifically. The entire premise of a customizable bidder is scoring impressions with signals the buyer supplies. We supply none, so the thing that makes the product worth its cost is the thing we do not do.

Networks are added to LeadLocate through one provider agnostic library, not one at a time as bespoke projects. That library defines 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. Twenty networks are registered against that contract and one of them is implemented. The other nineteen return a refusal that names itself, so a stray call fails loudly and readably rather than looking like an outage at the vendor. Beeswax is not among the twenty, which is a smaller claim than roadmap and an honest one.

The shared plumbing already exists and would not be rebuilt for this platform. Credentials are encrypted before storage with 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 on purpose, because these tables are shared across dealerships and a timezone relative timestamp is one you cannot reconcile afterwards. Campaign objects record which credentials created them and re resolve those same credentials later, so a disconnected account does not orphan the work built under it. That is unglamorous and it is what makes a compliance question a query rather than a phone call.

Two ways to advertise through LeadLocate, and you choose. The first is the webXintel Ads Network: included, built and operated by our team from the selections you make in Leads Manager, arriving as one line rather than a stack of platform invoices. It is live today and independent of every adapter question on this page.

The second is your own account. Where a network is built, you connect the account your store already holds, campaigns route through it, and the billing, naming and spend history remain yours. Disconnect and delivery falls back to the managed path.

Beeswax is unreachable by either path today, and the self connect path carries an additional wrinkle specific to this product. A bidder seat is not something a dealership casually holds. If your group has one, it almost certainly came with an agency or an in house media team attached, and the sensible integration conversation is about reporting reaching the CRM rather than about the CRM operating the bidder.

Across the whole gateway one limit applies and it is stated on every page: pushing, pausing and reading numbers from a network is done by our team, not from your dashboard. That is deliberate while the connection layer is young, and it is on the list to open up.

The order of work is fixed. A commercial agreement first, because no credential is issued without one. Then an adapter file written against the seven operation contract, a credential block, and each operation wired and verified against a live account. The engineering is the predictable half. The agreement is somebody else's timeline entirely.

On measurement, be realistic about what this kind of buying tells you and when. Delivery and spend read within a day. Whether the configuration is any good takes weeks, because the entire argument for a bidder is a marginal efficiency gain and a marginal gain is invisible in a small sample. That is the mathematics of the product, not a criticism of it.

For a dealership the practical consequence is that this is not the channel that answers the question most stores are actually asking, which is whether the phone rang today. Read what to expect from any paid lead source before deciding where a display budget belongs. Nothing on this page is a forecast of lead volume or closing rate, and nobody can honestly give you one.

The gaps that matter here are not the generic ones, they are the ones that sit exactly where this product's value lives.

We do not supply bidding signals or a custom bidding model. The reason to run a configurable bidder is to score impressions with data the buyer brings. We bring none, and no part of our stack produces a scoring feed, a sold customer signal or a propensity model for an advertising platform.

We do not upload hashed audiences. No Custom Audience, no Customer Match list, no first party segment exported anywhere, for this platform or any other.

We do not emit a vehicle catalog. Dynamic creative rendering individual units from a feed requires one and no code in our stack generates one for any ad platform.

We do not run a server side conversions endpoint, offline conversion upload, or pixel installation and management. Those are the standard measurement inputs for open web buying and their absence is the honest headline, not a footnote.

No campaign has ever been deployed to this platform from the CRM. The code does not exist.

Ask, and attach the context, because on this platform the context changes the answer more than usual. Tell us the group size, the monthly open web budget and whether a seat and an operating team already exist. Requests are recorded against the platform they name and the tally decides build order.

You will get a range or a reason from a person. On this one there is a decent chance the reason is that a configurable bidder is the wrong tool for your spend level, and if that is what we think, you will be told so with the arithmetic rather than sold a connector. That is a strange thing for a vendor page to say, which is precisely why this directory says it.

The managed path runs today regardless. Pricing for the platform is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with Beeswax today?

No. The status is available on request, and the published test for it is that the work is not started and demand decides the order. No adapter file, credential block or checklist for this platform exists in the ad gateway.

Can I use my own Beeswax seat?

Not through the CRM, because nothing has been built to reach it. The access class is also CERTIFIED, meaning a contract or minimum precedes any API credential. If your group already operates a seat, the useful conversation is about getting its reporting into the CRM rather than driving the bidder from it.

What happens if I request Beeswax?

It is logged against this platform specifically and counted, and the tally feeds build order. You will hear back from a person with either a range or a reason, including the reason that your spend level does not justify a bidder.

How is this different from a packaged demand side platform?

A packaged platform makes the bidding decisions for you with its own optimizer. A configurable bidder moves those decisions to the buyer, which is only an advantage if the buyer has the data, the staff and the volume to make better ones.

Could you feed my sold customer data into the bidding logic?

No. We do not export customer data to any advertising platform in any form, hashed or otherwise, and we do not produce scoring feeds or propensity models for one. That is a firm line rather than a sequencing question.

Is a bidder worth it for a single rooftop?

Almost never. The gain a bidder offers is marginal efficiency at volume, and a single store's open web budget is too small for that gain to be detectable, let alone larger than the operating cost of running it.

Requests are counted against the platform they name. Send your group size and open web budget and you will get an arithmetic answer, including a no if that is the right one.