What Is ADF/XML (Auto-lead Data Format)?
ADF/XML, short for Auto-lead Data Format, is a standardized XML structure that the automotive retail industry uses to transmit sales leads between systems. When a shopper submits a form on a marketplace, manufacturer site, dealer website or chat tool, the lead is commonly packaged as an ADF/XML document and delivered to the dealer’s CRM, usually by email to a dedicated lead-intake address or through a direct integration.
The format was created by an industry group in the late 1990s so that vendors and dealers would not need a custom integration for every lead source. Despite newer API-based options, ADF remains widely supported by dealer CRMs and lead providers.
Why ADF/XML Matters
- Interoperability: one standard format means almost any lead provider can deliver into almost any dealer CRM.
- Automation: leads arrive as structured records, not free-text emails, so the CRM can create customer records, assign sales staff and trigger auto-responses.
- Attribution: source and provider fields make it possible to track which vendor or campaign produced each lead.
- Speed: automated intake reduces the delay between a shopper’s inquiry and the first response.
How ADF/XML Works
An ADF document is a plain text XML file with defined elements. A typical lead includes:
- Request date: when the lead was created.
- Vehicle: interest type such as buy or lease, status (new or used), year, make, model, trim, VIN and stock number.
- Customer: name, email, phone and address fields, plus any comments or questions.
- Vendor: the dealership the lead is intended for.
- Provider: the source system or lead vendor, often with a service or campaign name.
- Optional trade-in and financing details when the form collected them.
The sending system builds the XML and emails it as the message body or an attachment to the CRM’s lead address, or posts it to an endpoint. The CRM parses the fields and creates a lead record. Because ADF is plain XML, many modern platforms also translate between ADF and API formats such as JSON.
How ADF/XML Affects Marketing
For agencies and dealer marketers, ADF is the plumbing that connects campaigns to sales results. Getting it right matters for both follow-up and reporting.
- Send campaign leads in ADF. Leads from landing pages, Meta lead forms or Google lead form assets should be converted to ADF so they land in the CRM with proper source tags rather than sitting in a separate inbox.
- Use consistent source naming. Agree on provider and service values, such as “Agency Name – Google Ads – Used Trucks”, so CRM reports can attribute leads accurately.
- Include vehicle details. Passing the stock number or VIN lets salespeople respond with specifics instead of a generic reply.
- Test before launch. Send test leads and confirm they appear in the CRM correctly assigned and tagged.
- Close the loop. Matching CRM sales back to lead sources lets you evaluate cost per sale, not just cost per lead, and feed offline conversions to ad platforms.
For example, an agency running Facebook lead ads for a dealer could use an integration that converts each lead into ADF and emails it to the CRM. The BDC sees the lead instantly, and the store can later report sales by campaign.
Best Practices
- Route every lead source into the CRM through ADF or a supported integration so nothing gets lost.
- Document a standard naming convention for provider and campaign fields.
- Include vehicle identifiers and the shopper’s comments whenever they are available.
- Run monthly tests on each lead source to catch broken integrations.
- Protect personal data in transit and only send leads to addresses the dealer has confirmed.