Taboola Realize Integration for Car Dealers

The largest native network on the open web, and where that connection honestly stands inside the CRM.

Taboola places recommendation units at the bottom and inside the body of news and publisher pages. The advertiser side of that business is now branded Realize, and the reach is the largest of any native network because Taboola also serves Yahoo native inventory. When a shopper finishes an article about winter tires and sees a block of suggested reading, some of those tiles are paid placements, and one of them can be your store.

For a dealership the useful mental model is that this is not search and it is not social. There is no query to match against and no profile graph to target. It is contextual placement at very large scale, priced by the click, on inventory that almost never runs out. A store can go from nothing to thousands of clicks on a vehicle detail page or an event page inside a few hours, which no other channel in this catalogue does as fast.

The unit itself is a headline and a thumbnail. That constraint matters, because it means the creative work is copywriting rather than video production, and a small store can compete on it without an agency retainer.

The honest case is visible activity at low unit cost. Native traffic is cheap, it starts immediately, and it fills the top of a funnel that search alone cannot fill because search is capped by how many people are typing. If a store has just taken over a franchise point, or is running a weekend sale event, this is the fastest way to put real traffic in front of a landing page and see whether the offer holds up.

The honest objection is intent, and it is a serious one. Nobody clicking a recommendation unit was shopping for a car thirty seconds earlier. Compared with a search click, the person is further from a purchase, more likely to bounce, and more likely to have clicked because the headline was interesting rather than because they want what you sell. Cost per click is low precisely because cost per sale is not automatically low.

The second objection is placement quality. Recommendation inventory sits next to whatever else the publisher accepted, and a dealer who cares about where the brand appears should ask for the block and allow lists before spending, not after. That is a normal part of planning dealership advertising and it is worth doing here more than most places.

Registered, not yet built. The published test for that status is that an adapter file exists in the ad gateway with a written wire-up checklist, committed and scoped. That is precisely what is on disk: an adapter for this network with a five step checklist and no working lifecycle methods behind it.

Every call the adapter receives, whether it is a deploy, a pause, a report or a verification, returns a refusal that names the network. A dealer will never see a green light here that is standing in for nothing. Loud refusals are the whole reason nineteen unbuilt adapters can sit inside a live system without anyone being misled by them.

Access class is PUBLIC, and that is the vendor's gate rather than ours. Taboola issues advertiser API credentials on an OAuth2 client credentials grant obtained from inside the advertiser account, with no partner review queue standing in front of it. There is no application to wait on, which is unusual in this family and is one reason this network sits near the front of the native build order.

Written as a design, because none of it runs today.

Lead capture on this network is clickout, meaning there is no in feed form. The click lands on a page you control, and the actual opt in happens on our own trade appraisal or finance form, inside the CRM that will work the lead. That is a real difference from a social lead form and it changes how the landing page has to be built.

This network is not a special case. It is one implementation of a contract that every advertising platform in the CRM answers.

There is a single library inside LeadLocate defining what any network must be able to do: hand us an authorization URL, exchange the credential for a token, list the accounts you are entitled to, 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 finishing this platform is a scoped checklist rather than an open ended project, and why finishing it cannot disturb the one network that is already implemented.

Tokens are encrypted before storage using AES-256-GCM. Every action taken against any 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 the table is shared across dealerships and a local timestamp is one nobody can reconcile afterwards. Campaign objects record which credentials created them and re-resolve those same credentials later, so disconnecting an account does not strand the work built underneath it. None of that has to be reinvented here, which is exactly why the remaining work is five steps long.

Two ways to advertise through LeadLocate, and you pick which one.

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 arrives as one line on your invoice instead of a stack of platform statements. Nothing to set up and no credential to file.

The second is your own advertiser account. Connect the account your store already has and campaigns route through it instead, on your billing, in your name, with your spend history intact. For this network that second path is what this page is about, and it is the half that is unfinished.

One limit stated plainly, because it applies across the whole gateway and you would find it out anyway: pushing, activating, pausing and reading spend from a network is done by our team today, not from a button on your dashboard. That is a deliberate constraint while the connection layer is young, and opening it up is on the list.

The checklist inside the adapter is five steps and it is ordered. Obtain client credentials from inside the advertiser account. Fill the credential block and enable it. Implement the token exchange and account listing. Implement campaign creation, status changes and budget updates against the advertiser endpoints. Implement reporting and the verification call.

Nothing on that list waits on a third party decision, which is what PUBLIC access buys you here. The minimum spend picture is the same story: the self serve floor on this network is low, low enough that a single rooftop can test it, though the current figure should be confirmed against the advertiser terms at the time you open the account rather than taken from a page.

On measurement, the shape is unusual and worth planning around. Clicks appear within hours of a campaign going live, because inventory is effectively unlimited and delivery is immediate. Leads take longer, typically one to three days, because the opt in happens on your landing page after a low intent click rather than inside the ad. Reading day one click volume as if it were lead volume is the single most common way a store misjudges this channel. What arrives fast is data, not buyers.

This is the section that makes the rest of the page worth reading.

We do not emit a vehicle catalog or an inventory feed to this network or any other. There is no code anywhere in our stack that generates a product feed for an advertising platform. Inventory Link ingests your feed and merchandises your units on your own properties, which is a different job entirely.

We do not run a server side conversions API. This network offers one, and that is exactly why it needs saying. No server side conversion events, no offline conversion upload, and no pixel installation or management of any kind. Conversion measurement on a clickout channel therefore rests on your landing page and the CRM record, not on a signal we send back.

We do not export a hashed customer list for audience matching or suppression, and no part of the five step checklist would create one.

No campaign has ever been deployed to this network from the CRM, because the code that would do it is not written. Anyone describing this integration as working today is describing the plan.

Say so with your store name attached, and say what you would run first. Requests are recorded against the platform they name and the tally is the input to build order, because a dealer ready to spend on a channel is a better signal than any internal roadmap meeting.

This platform carries real leverage in that queue for reasons of reach: it is the largest network in its family and the credential path has no vendor review in front of it, so the distance between a request and a working connection is shorter here than on most of the catalogue. If what you actually want is one of the gaps above rather than the connection itself, say that instead, and you will get a range or a reason rather than silence.

The managed path runs today and does not wait on any of this. Platform pricing is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with Taboola Realize today?

No. It is registered in the ad gateway, which means an adapter file exists with a five step wire-up checklist and no working lifecycle methods behind it. Every call the adapter receives returns a refusal naming the network rather than failing quietly.

Can I use my own Taboola Realize ad account?

Not through the CRM yet, because the self connect half is the part that is unbuilt. The credential itself is easy to obtain, since access here is public and needs no vendor review, so nothing on your side blocks it once the adapter is finished.

What happens if I request Taboola Realize?

The request is recorded against this network specifically and counted. That count decides build order among the registered adapters. A person answers you with a range or a reason, and if the honest answer is that it sits behind three other networks, that is what you get told.

Will I get leads on the first day?

You will get clicks on the first day, usually within hours. Leads generally take one to three days, because the opt in happens on your landing page rather than inside the ad unit. Treating early click volume as lead volume is the fastest way to misread this channel.

How do leads actually get captured if there is no form in the ad?

Lead capture here is clickout. The ad sends the shopper to a page you control, and the opt in happens on a trade appraisal, finance or vehicle enquiry form that already lives in the CRM. Native in feed forms are a different mechanic and this network is not one of them.

Why is this network branded Realize now?

Realize is the current name of the advertiser side of the platform. The publisher side and the recommendation units are the same business. If you already hold an advertiser login, it is the same account relationship under a newer name.

Requests are counted against the platform they name, and the count decides what gets built next. Tell us your store and the first offer you would put behind a click campaign.