ADF/XML Integration

ADF (Auto-Lead Data Format) is an XML schema standardised by the automotive industry for transmitting structured lead data between ad platforms / lead providers and dealer CRMs. Every major auto CRM -- VinSolutions, eLead, DealerSocket, DriveCentric, ProMax, AutoRaptor -- accepts ADF as its primary inbound lead format because it carries vehicle-of-interest, trade-in, customer intent, and contact data in a single structured document.

LeadSync converts each Facebook, Google, LinkedIn, or TikTok lead submission into a properly formatted ADF/XML document and emails it to your dealer CRM's ADF intake address. The XML is included both inline in the email body and as a lead.xml attachment, so any CRM that supports ADF email parsing accepts the lead immediately. No API credentials, no middleware, no IT setup at the dealership.

No. The only thing you need from the dealership is the CRM's ADF intake email address (every dealer CRM has one -- it lives in the lead source / inbound leads section of CRM settings). Paste it into LeadSync, map your fields, and leads start syncing. There are no API keys to provision, no firewall changes, and no developer involvement at the dealer level.

Every major dealer CRM that accepts ADF email intake -- which is essentially all of them. Confirmed: VinSolutions, eLead CRM (CDK Global), DealerSocket, DriveCentric, ProMax, AutoRaptor, Pentana DealerPRO, Keyloop. If your CRM accepts ADF leads from any third-party provider (Cars.com, AutoTrader, Edmunds, etc.), it accepts ADF leads from LeadSync.

Yes. The ADF spec has dedicated nodes for vehicle year, make, model, new/used status, and customer intent (buy, lease, sell, trade-in, test-drive). LeadSync's field mapping includes ADF destinations for each of these, so questions like "Which model are you interested in?" or "Are you trading in a vehicle?" land in the right CRM column rather than a free-text notes field.

They land in the customer comments block as a labelled key/value list, alongside the form name and any explicit comments. So a custom question like "Preferred contact time?" appears in your CRM's notes / comments column as "Preferred contact time? Evenings" -- visible to the sales rep working the lead and not silently dropped.

Yes. The CRM Email Address(es) field accepts a comma-separated list. LeadSync sends the same ADF/XML email to every address on the list, so a multi-rooftop dealer group can route a single Facebook ad campaign's leads into each store's CRM simultaneously. A central BDC system and a regional CRM can both receive the same lead in parallel.

Yes. The same ADF/XML pipeline handles Facebook Lead Ads, Instagram Lead Ads, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own LeadSync connection but they all serialise into the same ADF format your dealer CRM accepts.

No. The ADF email goes out the moment the lead webhook arrives -- typically under five seconds from the prospect tapping Submit on the ad to the email landing at the CRM intake address. Most dealer CRMs parse the email and create the contact record within another 30 seconds, so the full path from form submission to contact-in-CRM is usually under one minute.