Dealersocket

Australia

Dealerstudio has the ability to push to Dealer Socket, however it requires the dealer to provide an email address connected with Dealer Socket so that the leads can be pushed in. The leads are then pushed into Dealer Socket using an XML format. A dealer can also provide multiple Dealer Socket email addresses, where each email address corresponds to a different location/bucket within Dealer Socket.

Sample XML

The lead is sent in ADF (Auto-lead Data Format) XML. A typical payload looks like this:

<?xml version="1.0"?>
<adf>
  <prospect>
    <id sequence="1" source="examplemotors.com.au">examplemotors.com.au-123456</id>
    <requestdate>24-08-18 09:15:00</requestdate>
    <vehicle interest="buy" status="new">
      <year>2024</year>
      <make>Toyota</make>
      <model>RAV4</model>
      <vin>JTMWFREVXHD000000</vin>
      <stock>STK1234</stock>
      <odometer>15</odometer>
      <price>45990</price>
      <comments>I'd like a quote on the RAV4 Cruiser.</comments>
    </vehicle>
    <customer>
      <contact>
        <name part="first">Jane</name>
        <name part="last">Smith</name>
        <email>jane.smith@example.com</email>
        <phone type="cellphone" time="nopreference">0400000000</phone>
      </contact>
      <comments>I'd like a quote on the RAV4 Cruiser.</comments>
    </customer>
    <vendor>
      <id sequence="1" source="examplemotors.com.au">DS-CODE-123</id>
      <vendorname>Example Motors</vendorname>
    </vendor>
    <provider>
      <name>examplemotors.com.au</name>
    </provider>
  </prospect>
</adf>

How we map data into the XML

XML element	Dealer Studio data
prospect > id	Website domain (or dealership name) combined with the lead id
requestdate	Lead created date/time
vehicle (interest="buy", status)	Vehicle of interest; status is new or used based on the car or enquiry type. Included only when vehicle details are present
vehicle > year/make/model/vin/stock/odometer/price	The car of interest (make/model fall back to the manufacturer and enquiry details)
vehicle > comments	The customer’s enquiry message
customer > contact > name	Customer first and last name
customer > contact > email	Customer email
customer > contact > phone	Customer phone number
customer > comments	The customer’s enquiry message (plus any deposit/reservation notes)
vendor > id	DealerSocket code (used to route the lead to the correct bucket/location)
vendor > vendorname	Configured vendor name, otherwise the website name
provider > name	Configured provider name, otherwise the website domain, source, or dealership name

United States

In the United States, Dealer Studio can push into Dealer Socket via API. Please contact the support team to set this up.