{
    "kind": "term",
    "name": "Tealium for Automotive",
    "count": 3,
    "items": [

    
        {
            "weight": "65",
            "url": "https://docs-preview.tealium.com/server-side/data-connect/manage-data-connect-integrations/authenticom/",
            "title": "Authenticom DealerVault Data Connect Integration Setup Guide",
            "body": "<p>The Authenticom integration with Tealium Data Connect lets you import the following vendor data feeds:</p>\n<ul>\n<li>Inventory</li>\n<li>Part Inventory</li>\n<li>Sales</li>\n<li>Open Repair Orders</li>\n<li>Special Order Parts</li>\n<li>Service</li>\n<li>Service Appointment</li>\n</ul>\n<h2 id=\"requirements\">Requirements</h2>\n<ul>\n<li>Tealium EventStream or AudienceStream</li>\n<li>Tealium Data Connect</li>\n<li>Tealium DataAccess (for EventStore or EventDB)</li>\n<li>Authenticom API access</li>\n</ul>\n<h2 id=\"create-an-authenticom-integration\">Create an Authenticom integration</h2>\n<p>Use the following steps to create an Authenticom integration with Tealium Data Connect:</p>\n<ol>\n<li>Set up a Tealium Connect data source.</li>\n<li>Contact your Implementation Engineer or Customer Success Manager to get the recipes imported into your Data Connect environment.</li>\n<li>Establish a connection to the Authenticom API.</li>\n<li>Select a data type and vendor.</li>\n<li>Send events to Tealium.</li>\n<li>Set up an event feed for leads.</li>\n<li>Test with trace and activate the recipe.</li>\n</ol>\n<h2 id=\"step-1-set-up-a-tealium-connect-data-source\">Step 1: Set up a Tealium Connect data source</h2>\n<p>Set up a Tealium Connect data source. For more information, see <a href=\"/server-side/data-connect/manage-data-connect-integrations/tealium-connect-data-source/\">Set up a Tealium Connect data source</a>.</p>\n<h2 id=\"step-2-contact-tealium\">Step 2: Contact Tealium</h2>\n<p>Contact your Implementation Engineer or Customer Success Manager, and they will import the integration into your environment.</p>\n<h2 id=\"step-3-establish-a-connection-to-the-authenticom-api\">Step 3: Establish a connection to the Authenticom API</h2>\n<p>To establish a connection to the Authenticom API, perform the following steps:</p>\n<ol>\n<li>Go to <strong>Data Connect &gt; Integrations</strong>.</li>\n<li>Select the <strong>Authenticom</strong> connection.</li>\n<li>Do not change <strong>Base URL</strong>.</li>\n<li>Enter the <strong>Subscription Key</strong>, which is in the Authenticom Developers API portal in production.</li>\n</ol>\n<figure><a class=\"slb\" href=\"/images/server-side/data-connect/authenticom-data-connect-integration-establish-connection.png\"><img src=\"https://docs.tealium.com/images/server-side/data-connect/authenticom-data-connect-integration-establish-connection.png\"\n          alt=\"Establish connection\"\n          title=\"Establish connection\"/>\n     </a>\n </figure>\n<h2 id=\"step-4-select-a-data-type-and-vendor\">Step 4: Select a data type and vendor</h2>\n<p>To select the data type and vendor, perform the following steps:</p>\n<ol>\n<li>Go to the recipe named <strong>Authenticom - DealerVault</strong>.</li>\n<li>Select step 4 of the recipe <strong>Retrieve dealers with updated data since a given date</strong>.</li>\n<li>Select the data type that you want to import into Tealium. The following data types are available:\n<ul>\n<li><code>INV</code>: Inventory.</li>\n<li><code>PTINV</code>: Part Inventory.</li>\n<li><code>SL</code>: Sales.</li>\n<li><code>OPENRO</code>: Open Repair Orders.</li>\n<li><code>SOP</code>: Special Order Parts.</li>\n<li><code>SV</code>: Service.</li>\n<li><code>SV_APPT</code>: Service Appointment.</li>\n</ul>\n</li>\n<li>In the top-right of the window, click <strong>Save</strong>.</li>\n</ol>\n<figure><a class=\"slb\" href=\"/images/server-side/data-connect/authenticom-data-connect-integration-select-data-type.png\"><img src=\"https://docs.tealium.com/images/server-side/data-connect/authenticom-data-connect-integration-select-data-type.png\"\n          alt=\"Select data type and vendor\"\n          title=\"Select data type and vendor\"/>\n     </a>\n </figure>\n<h2 id=\"step-5-send-events-to-tealium\">Step 5: Send events to Tealium</h2>\n<p>To send events to Tealium, perform the following steps:</p>\n<ol>\n<li>Go to <strong>Send events in Tealium events V2</strong>.</li>\n<li>Configure the data that you want to send to Tealium.</li>\n</ol>\n<figure><a class=\"slb\" href=\"/images/server-side/data-connect/authenticom-data-connect-integration-send-events.png\"><img src=\"https://docs.tealium.com/images/server-side/data-connect/authenticom-data-connect-integration-send-events.png\"\n          alt=\"Send events to Tealium\"\n          title=\"Send events to Tealium\"/>\n     </a>\n </figure>\n<p>For additional information, see <a href=\"/server-side/data-connect/manage-data-connect-integrations/create-recipe/#step-2-configure-an-action\">Create a recipe: Configure an Action</a>.</p>\n<h2 id=\"step-6-set-up-an-event-feed-for-leads\">Step 6: Set up an event feed for leads</h2>\n<figure><a class=\"slb\" href=\"/images/server-side/data-connect/authenticom-data-connect-integration-set-up-event-feed.png\"><img src=\"https://docs.tealium.com/images/server-side/data-connect/authenticom-data-connect-integration-set-up-event-feed.png\"\n          alt=\"Set up event feed\"\n          title=\"Set up event feed\"/>\n     </a>\n </figure>\n<p>Use the following steps to create an event feed:</p>\n<ol>\n<li>Go to <strong>EventStream &gt; Live Events</strong> and click <strong>+ Add Event Feed</strong>.</li>\n<li>In the <strong>Create Event Feed</strong> dialog, enter a <strong>Title</strong> and any <strong>Notes</strong>.</li>\n<li>(Optional) Click <strong>Add Label</strong> to select labels to apply to this event feed.</li>\n<li>Under <strong>Event Data Storage</strong>, enable the feed for EventStore or EventDB.</li>\n<li>Set an <strong>Attribute Condition</strong> for the feed to capture events that match new lead events.</li>\n<li>Click <strong>Save</strong>.</li>\n<li>Save and publish your profile.</li>\n</ol>\n<h2 id=\"step-7-test-with-trace-and-activate-the-recipe\">Step 7: Test with trace and activate the recipe</h2>\n<p>Before activating the recipe, perform thorough testing. Once testing is successful, activate the recipe to start the automated data integration process.</p>\n<p>Use the following steps to test with trace and activate the recipe:</p>\n<ol>\n<li>Go to <strong>Trace</strong>.</li>\n<li>Under <strong>New Trace</strong>, click <strong>Start</strong>. A dialog with a trace ID appears.</li>\n<li>Copy the trace ID and click <strong>Continue</strong>.</li>\n<li>Go to <strong>Data Connect &gt; Integrations</strong>.</li>\n<li>In the <strong>Integrations</strong> screen, perform the following steps for recipes that send new leads from Authenticom to Tealium:\n<ol>\n<li>Select your recipe.</li>\n<li>Select the <strong>Tealium Events V2 action</strong> to edit it.</li>\n<li>Under <strong>Attributes to add</strong>, add a <code>tealium_trace_id</code> key and paste the trace ID in the <strong>Value</strong>.</li>\n<li>Click <strong>Save</strong>.</li>\n<li>From the <strong>Start recipe</strong> list, click <strong>Test recipe</strong>.</li>\n</ol>\n</li>\n<li>Return to the <strong>Trace</strong> interface to inspect the log details.</li>\n<li>After you are done testing, click <strong>Stop test</strong>.</li>\n<li>To activate the recipe, click <strong>Start recipe</strong>.</li>\n</ol>\n"
        }  

    , 
        {
            "weight": "66",
            "url": "https://docs-preview.tealium.com/server-side/data-connect/manage-data-connect-integrations/dealertrack/",
            "title": "DealerTrack Data Connect Integration Setup Guide",
            "body": "<p>The DealerTrack integration with Tealium Data Connect lets you import the following data.</p>\n<ul>\n<li>Deal History</li>\n<li>Service Appointments</li>\n<li>Open Repair Orders</li>\n<li>Closed Repair Orders</li>\n</ul>\n<h2 id=\"requirements\">Requirements</h2>\n<ul>\n<li>Tealium EventStream or AudienceStream</li>\n<li>Tealium Data Connect</li>\n<li>Tealium DataAccess (for EventStore or EventDB)</li>\n<li>OpenTrack access</li>\n</ul>\n<h2 id=\"create-a-dealertrack-integration\">Create a DealerTrack integration</h2>\n<p>Use the following steps to create a DealerTrack integration with Tealium Data Connect:</p>\n<ol>\n<li>Set up a Tealium Connect data source.</li>\n<li>Establish a connection to the DealerTrack API.</li>\n<li>Create a recipe to send data from DealerTrack to Tealium.</li>\n<li>Send events to Tealium.</li>\n<li>Set up an event feed for data.</li>\n<li>Test with trace and activate the recipe.</li>\n</ol>\n<h2 id=\"step-1-set-up-a-tealium-connect-data-source\">Step 1: Set up a Tealium Connect data source</h2>\n<p>Set up a Tealium Connect data source. For more information, see <a href=\"/server-side/data-connect/manage-data-connect-integrations/tealium-connect-data-source/\">Set up a Tealium Connect data source</a>.</p>\n<h2 id=\"step-2-establish-a-connection-to-the-dealertrack-api\">Step 2: Establish a connection to the DealerTrack API</h2>\n<p>To establish a connection to the DealerTrack API, perform the following steps:</p>\n<ol>\n<li>Go to <strong>Data Connect &gt; Integrations</strong>.</li>\n<li>Click <strong>Connections</strong>, and then click <strong>Create</strong>.</li>\n<li>Select the <strong>DealerTrack</strong> connection.</li>\n<li>Under <strong>Base URL</strong>, enter <code>https://ot.dms.dealertrack.com</code>.</li>\n<li>Enter your <strong>Username</strong> and <strong>Password</strong>.</li>\n<li>Click <strong>Connect</strong>.</li>\n</ol>\n<figure><a class=\"slb\" href=\"/images/server-side/data-connect/dealertrack-data-connect-integration-establish-connection1.png\"><img src=\"https://docs.tealium.com/images/server-side/data-connect/dealertrack-data-connect-integration-establish-connection1.png\"\n          alt=\"Establish connection 1\"\n          title=\"Establish connection 1\"/>\n     </a>\n </figure>\n<figure><a class=\"slb\" href=\"/images/server-side/data-connect/dealertrack-data-connect-integration-establish-connection2.png\"><img src=\"https://docs.tealium.com/images/server-side/data-connect/dealertrack-data-connect-integration-establish-connection2.png\"\n          alt=\"Establish connection\"\n          title=\"Establish connection\"/>\n     </a>\n </figure>\n<h2 id=\"step-3-create-a-recipe-to-send-data-from-dealertrack-to-tealium\">Step 3: Create a recipe to send data from DealerTrack to Tealium</h2>\n<p>To create a recipe to send data from DealerTrack to Tealium, perform the following steps:</p>\n<p>For more information on how to create a new recipe, see <a href=\"/server-side/data-connect/manage-data-connect-integrations/create-recipe/\">Create a recipe in Data Connect</a>.</p>\n<ol>\n<li>Go to <strong>DataConnect &gt; Integrations</strong>.</li>\n<li>In the <strong>Integrations</strong> screen, click <strong>Create &gt; Recipe</strong>.</li>\n<li>Create a new recipe that triggers from the Schedule app. For information on how to create a recipe that triggers from an app, see <a href=\"/server-side/data-connect/manage-data-connect-integrations/create-recipe/\">Create a recipe in Data Connect</a>.</li>\n</ol>\n<p>The <a href=\"#actions\">Actions</a> section below contains details on what data is possible to retrieve from DealerTrack.</p>\n<h2 id=\"step-4-send-events-to-tealium\">Step 4: Send events to Tealium</h2>\n<p>To send events to Tealium, perform the following steps:</p>\n<ol>\n<li>Go to <strong>Send Events in Tealium Events V2</strong>.</li>\n<li>Configure the data that you want to send to Tealium.</li>\n</ol>\n<figure><a class=\"slb\" href=\"/images/server-side/data-connect/dealertrack-data-connect-integration-send-events.png\"><img src=\"https://docs.tealium.com/images/server-side/data-connect/dealertrack-data-connect-integration-send-events.png\"\n          alt=\"Send events to Tealium\"\n          title=\"Send events to Tealium\"/>\n     </a>\n </figure>\n<p>For additional information, see <a href=\"/server-side/data-connect/manage-data-connect-integrations/create-recipe/#step-2-configure-an-action\">Create a recipe: Configure an Action</a>.</p>\n<h2 id=\"step-5-set-up-an-event-feed-for-leads\">Step 5: Set up an event feed for leads</h2>\n<figure><a class=\"slb\" href=\"/images/server-side/data-connect/dealertrack-data-connect-integration-event-feed.png\"><img src=\"https://docs.tealium.com/images/server-side/data-connect/dealertrack-data-connect-integration-event-feed.png\"\n          alt=\"Event feed\"\n          title=\"Event feed\"/>\n     </a>\n </figure>\n<p>Use the following steps to create an event feed:</p>\n<ol>\n<li>Go to <strong>EventStream &gt; Live Events</strong> and click <strong>+ Add Event Feed</strong>.</li>\n<li>In the <strong>Create Event Feed</strong> dialog, enter a <strong>Title</strong> and any <strong>Notes</strong>.\n<ul>\n<li>The event feed title is dependent on how lead events come into Data Connect.</li>\n</ul>\n</li>\n<li>(Optional) Click <strong>Add Label</strong> to select labels to apply to this event feed.</li>\n<li>Under <strong>Event Data Storage</strong>, enable the feed for EventStore or EventDB.</li>\n<li>Set an <strong>Attribute Condition</strong> for the feed to capture events that match new lead events.</li>\n<li>Click <strong>Save</strong>.</li>\n<li>Save and publish your profile.</li>\n</ol>\n<h2 id=\"step-6-test-with-trace-and-activate-the-recipe\">Step 6: Test with trace and activate the recipe</h2>\n<p>Before activating the recipe, perform thorough testing. Once testing is successful, activate the recipe to start the automated data integration process.</p>\n<p>Use the following steps to test with trace and activate the recipe:</p>\n<ol>\n<li>Go to <strong>Trace</strong>.</li>\n<li>Under <strong>New Trace</strong>, click <strong>Start</strong>. A dialog with a trace ID appears.</li>\n<li>Copy the trace ID and click <strong>Continue</strong>.</li>\n<li>Go to <strong>Data Connect &gt; Integrations</strong>.</li>\n<li>In the <strong>Integrations</strong> screen, perform the following steps for recipes that send new leads from DealerTrack to Tealium:\n<ol>\n<li>Select your recipe.</li>\n<li>Select the <strong>Tealium events V2 action</strong> to edit it.</li>\n<li>Under <strong>Attributes to add</strong>, add a <code>tealium_trace_id</code> key and paste the trace ID in the <strong>Value</strong>.</li>\n<li>Click <strong>Save</strong>.</li>\n<li>From the <strong>Start recipe</strong> list, click <strong>Test recipe</strong>.</li>\n</ol>\n</li>\n<li>Return to the <strong>Trace</strong> interface to inspect the log details.</li>\n<li>After you are done testing, click <strong>Stop test</strong>.</li>\n<li>To activate the recipe, click <strong>Start recipe</strong>.</li>\n</ol>\n<h2 id=\"actions\">Actions</h2>\n<p>The following actions can be tracked through this integration:</p>\n<h3 id=\"search-deal-by-origination-date\">Search Deal by Origination Date</h3>\n<table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Company Number</td>\n<td>The company number. For example, <code>ZE7</code>.</td>\n</tr>\n<tr>\n<td>Enterprise Code</td>\n<td>The enterprise code. For example, <code>ZE</code>.</td>\n</tr>\n<tr>\n<td>Server Name</td>\n<td>The name of the server. For example, <code>arkonap.arkona.com</code>.</td>\n</tr>\n<tr>\n<td>Origination Date Start</td>\n<td>Date of the car deal, search beginning with this date. The format is <code>YYYY-MM-DD</code>.</td>\n</tr>\n<tr>\n<td>Origination Date End</td>\n<td>Date of the car deal, search ending with this date. The format is <code>YYYY-MM-DD</code>.</td>\n</tr>\n<tr>\n<td>Deal Status</td>\n<td>The status of the deal, if blank or not sent it will pull all deal statuses. Acceptable parameters are <code>Accepted</code>, <code>Capped</code>, <code>Closed</code>, <code>Unaccepted</code>, or blank.</td>\n</tr>\n</tbody>\n</table>\n<h3 id=\"appointment-lookup\">Appointment Lookup</h3>\n<table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Company Number</td>\n<td>The company number. For example, <code>ZE7</code>.</td>\n</tr>\n<tr>\n<td>Enterprise Code</td>\n<td>The enterprise code. For example, <code>ZE</code>.</td>\n</tr>\n<tr>\n<td>Server Name</td>\n<td>The name of the server. For example, <code>arkonap.arkona.com</code>.</td>\n</tr>\n<tr>\n<td>Date From</td>\n<td>Starting Date of Appointment Search, this is the day of the actual appointment, not when it was created. The format is <code>YYYY-MM-DD</code>.</td>\n</tr>\n<tr>\n<td>Date To</td>\n<td>Ending Date of Appointment Search, this is the day of the actual appointment, not when it was created. The format is <code>YYYY-MM-DD</code>.</td>\n</tr>\n<tr>\n<td>Created Date Time Start</td>\n<td>When to start the search of when Appointments were created. The format is <code>yyyy-mm-ddThh:mm:ssZ.</code></td>\n</tr>\n<tr>\n<td>Created Date Time End</td>\n<td>When to end the search of when Appointments were created. The format is <code>yyyy-mm-ddThh:mm:ssZ</code>.</td>\n</tr>\n</tbody>\n</table>\n<h3 id=\"open-repair-order-lookup\">Open Repair Order Lookup</h3>\n<table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Company Number</td>\n<td>The company number. For example, <code>ZE7</code>.</td>\n</tr>\n<tr>\n<td>Enterprise Code</td>\n<td>The enterprise code. For example, <code>ZE</code>.</td>\n</tr>\n<tr>\n<td>Server Name</td>\n<td>The name of the server. For example, <code>arkonap.arkona.com</code>.</td>\n</tr>\n<tr>\n<td>Created Date Time Start</td>\n<td>When to start the search of when Open Repair Orders were created. The format is <code>yyyy-mm-ddThh:mm:ssZ</code>.</td>\n</tr>\n<tr>\n<td>Created Date Time End</td>\n<td>When to end the search of when Open Repair Orders were created. The format is <code>yyyy-mm-ddThh:mm:ssZ</code>.</td>\n</tr>\n</tbody>\n</table>\n<h3 id=\"get-closed-repair-orders\">Get Closed Repair Orders</h3>\n<table>\n<thead>\n<tr>\n<th>Parameter</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Company Number</td>\n<td>The company number. For example, <code>ZE7</code>.</td>\n</tr>\n<tr>\n<td>Enterprise Code</td>\n<td>The enterprise code. For example, <code>ZE</code>.</td>\n</tr>\n<tr>\n<td>Server Name</td>\n<td>The name of the server. For example, <code>arkonap.arkona.com</code>.</td>\n</tr>\n<tr>\n<td>Final Close Date Start</td>\n<td>When to start the search for final closed repair orders. The format is <code>yyyy-mm-ddThh:mm:ssZ</code>.</td>\n</tr>\n<tr>\n<td>Final Close Date End</td>\n<td>When to end the search for final closed repair orders. The format is <code>yyyy-mm-ddThh:mm:ssZ</code>.</td>\n</tr>\n</tbody>\n</table>\n"
        }  

    , 
        {
            "weight": "0",
            "url": "https://docs-preview.tealium.com/server-side-connectors/cdk-connector/",
            "title": "CDK CRM Connector Setup Guide",
            "body": "<h2 id=\"api-information\">API Information</h2>\n<p>This connector uses the following vendor API:</p>\n<ul>\n<li>API Name: CDK Global API</li>\n<li>API Version: v1</li>\n<li>API Endpoint: <code>https://api.fortellis.io</code></li>\n<li>Documentation: <a href=\"https://apidocs.fortellis.io/apis/1b0047b1-feec-42e9-be1b-d3285493ac9a\">CDK CRM Direct Post Sales Leads</a></li>\n</ul>\n<h2 id=\"configuration\">Configuration</h2>\n<p>Go to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see <a href=\"/server-side/connectors/about/\">About Connectors</a>.</p>\n<p class=\"note\"><i class=\"fa fa-exclamation-triangle\"></i>When you add this connector you are prompted to accept the vendor&rsquo;s data platform policy.</p>\n<p>After adding the connector, configure the following settings:</p>\n<ul>\n<li><strong>Organization ID</strong>\n<ul>\n<li>To find your Fortellis Organization ID (Entity ID), log into your Fortellis account, hover over your name, and click <strong>Organization Management</strong>. The Entity ID is displayed on the page.</li>\n</ul>\n</li>\n<li><strong>Subscription ID</strong>\n<ul>\n<li>Select the Subscription ID.</li>\n</ul>\n</li>\n<li><strong>Endpoint</strong>\n<ul>\n<li>Select the endpoint. The default endpoint is <strong>Prod</strong>.</li>\n</ul>\n</li>\n</ul>\n<h2 id=\"actions\">Actions</h2>\n<table>\n<thead>\n<tr>\n<th>Action Name</th>\n<th style=\"text-align:center\">AudienceStream</th>\n<th style=\"text-align:center\">EventStream</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Send Lead</td>\n<td style=\"text-align:center\">✗</td>\n<td style=\"text-align:center\">✓</td>\n</tr>\n</tbody>\n</table>\n<p>The following section describes how to set up parameters and options for each action.</p>\n<h3 id=\"send-lead\">Send Lead</h3>\n<h4 id=\"prospect\">Prospect</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Request Date</td>\n<td>Date that the API call was made.</td>\n</tr>\n</tbody>\n</table>\n<h4 id=\"id\">ID</h4>\n<p>Use this to send the lead source.</p>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>ID Source</td>\n<td>Name of the source that created this ID.</td>\n</tr>\n<tr>\n<td>ID Sequence</td>\n<td>A number used to track the history of this piece of data.</td>\n</tr>\n<tr>\n<td>ID Value</td>\n<td>The ID value.</td>\n</tr>\n</tbody>\n</table>\n<h4 id=\"vehicle\">Vehicle</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Interest</td>\n<td>The customer&rsquo;s interest type in a vehicle. Accepted values: <code>buy</code>, <code>lease</code>, <code>sell</code>, <code>trade-in</code>, <code>test-drive</code>.</td>\n</tr>\n<tr>\n<td>Status</td>\n<td>Identify vehicle as <code>new</code> or <code>used</code>.</td>\n</tr>\n<tr>\n<td>Year</td>\n<td>Model year of the vehicle.</td>\n</tr>\n<tr>\n<td>Make</td>\n<td>Manufacturer of vehicle.</td>\n</tr>\n<tr>\n<td>Model</td>\n<td>Model of vehicle.</td>\n</tr>\n<tr>\n<td>VIN</td>\n<td>Vehicle Identification Number of the vehicle.</td>\n</tr>\n<tr>\n<td>Stock</td>\n<td>Vendor&rsquo;s stock number for vehicle.</td>\n</tr>\n<tr>\n<td>Trim</td>\n<td>Trim description.</td>\n</tr>\n<tr>\n<td>Units</td>\n<td>The unit of measurement of the odometer: <code>mi</code> for miles or <code>km</code> for kilometers.</td>\n</tr>\n<tr>\n<td>Value</td>\n<td>The reading on the odometer.</td>\n</tr>\n<tr>\n<td>Body Style</td>\n<td>Generic body style, such as <code>SUV</code>, <code>Sedan</code>, <code>Coupe</code>, etc.</td>\n</tr>\n<tr>\n<td>Transmission</td>\n<td><code>A</code> (Automatic) or <code>M</code> (Manual).</td>\n</tr>\n<tr>\n<td>Number of Doors</td>\n<td>Number of doors on vehicle.</td>\n</tr>\n<tr>\n<td>Price Type</td>\n<td>The type of price. Accepted values: <code>quote</code>, <code>offer</code>, <code>msrp</code>, <code>invoice</code>, <code>call</code>, <code>appraisal</code>, <code>asking</code>.</td>\n</tr>\n<tr>\n<td>Currency</td>\n<td>ISO 4217 currency code.</td>\n</tr>\n<tr>\n<td>Delta</td>\n<td>The <code>Delta</code> value and <code>Relative To</code> properties can be used to express the price as a percentage relative to another value, such as the invoice. Accepted values: <code>absolute</code>, <code>relative</code>, <code>percentage</code>.</td>\n</tr>\n<tr>\n<td>Relative To</td>\n<td>The <code>Delta</code> value and <code>Relative To</code> properties can be used to express the price as a percentage relative to another value, such as the invoice. Accepted values: <code>msrp</code>, <code>invoice</code>.</td>\n</tr>\n<tr>\n<td>Price Source</td>\n<td>The source where this value came from, such as <code>Kelley Blue Book</code>.</td>\n</tr>\n<tr>\n<td>Price Amount</td>\n<td>The amount of the price.</td>\n</tr>\n<tr>\n<td>Price Comments</td>\n<td>Explanatory note for pricing, such as <code>Anniversary Edition</code>.</td>\n</tr>\n<tr>\n<td>Comments</td>\n<td>Comments about vehicle.</td>\n</tr>\n<tr>\n<td>Financing Method</td>\n<td>Identifies financing option. Accepted values: <code>cash</code>, <code>finance</code>, <code>lease</code>.</td>\n</tr>\n<tr>\n<td>Financing Amount Type</td>\n<td>Payment numbers for financing. Accepted values: <code>downpayment</code>, <code>monthly</code>, <code>total</code>.</td>\n</tr>\n<tr>\n<td>Financing Amount Limit</td>\n<td>Finance amount limit. Accepted values: <code>maximum</code>, <code>minimum</code>, <code>exact</code>.</td>\n</tr>\n<tr>\n<td>Financing Amount Currency</td>\n<td>ISO 4217 currency code.</td>\n</tr>\n<tr>\n<td>Financing Amount Value</td>\n<td>Amount to finance.</td>\n</tr>\n<tr>\n<td>Financing Balance Type</td>\n<td>Type of balance. Accepted values: <code>finance</code>, <code>residual</code>.</td>\n</tr>\n<tr>\n<td>Financing Balance Currency</td>\n<td>ISO 4217 currency code.</td>\n</tr>\n<tr>\n<td>Financing Balance Value</td>\n<td>Remaining balance value.</td>\n</tr>\n<tr>\n<td>Interior Color</td>\n<td>Interior color.</td>\n</tr>\n<tr>\n<td>Exterior Color</td>\n<td>Exterior color.</td>\n</tr>\n<tr>\n<td>Preference</td>\n<td>A number indicating order of preference, with <code>1</code> being the favorite.</td>\n</tr>\n</tbody>\n</table>\n<h4 id=\"customer\">Customer</h4>\n<p>Details about a customer looking to transact a vehicle.</p>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Contact Name Part</td>\n<td>The part of the name of the contact. Accepted values: <code>first</code>, <code>middle</code>, <code>suffix</code>, <code>last</code>, <code>full</code>.</td>\n</tr>\n<tr>\n<td>Contact Name Type</td>\n<td>The type of contact. Accepted values: <code>individual</code>, <code>business</code>.</td>\n</tr>\n<tr>\n<td>Contact Name Value</td>\n<td>The text of the name.</td>\n</tr>\n<tr>\n<td>Email Preferred</td>\n<td>Indicates if the email address is the preferred method of contact (versus a phone number).</td>\n</tr>\n<tr>\n<td>Email Value</td>\n<td>The email address.</td>\n</tr>\n<tr>\n<td>Contact Phone Type</td>\n<td>The type of phone. Accepted values: <code>voice</code>, <code>phone</code>, <code>fax</code>, <code>cellphone</code>, <code>pager</code>.</td>\n</tr>\n<tr>\n<td>Contact Preferred Call Time</td>\n<td>The preferred time to contact the phone number. Accepted values: <code>morning</code>, <code>afternoon</code>, <code>evening</code>, <code>nopreference</code>, <code>day</code>.</td>\n</tr>\n<tr>\n<td>Phone Preferred</td>\n<td>Indicates if the phone is the preferred method of contact (versus email).</td>\n</tr>\n<tr>\n<td>Phone Number</td>\n<td>The phone number.</td>\n</tr>\n<tr>\n<td>Contact Address Type</td>\n<td>The type of address. Accepted values: <code>work</code>, <code>home</code>, <code>delivery</code>.</td>\n</tr>\n<tr>\n<td>Contact Street Address Value</td>\n<td>The number and name of the street.</td>\n</tr>\n<tr>\n<td>Contact Apartment Number</td>\n<td>Apartment number of customer.</td>\n</tr>\n<tr>\n<td>Contact City</td>\n<td>The name of the city.</td>\n</tr>\n<tr>\n<td>Contact Region Code</td>\n<td>State or province.</td>\n</tr>\n<tr>\n<td>Contact Zip Code</td>\n<td>The postal code (zip code).</td>\n</tr>\n<tr>\n<td>Contact Country</td>\n<td>ISO 3166 country code.</td>\n</tr>\n<tr>\n<td>Customer Comments</td>\n<td>Comments captured from the customer.</td>\n</tr>\n</tbody>\n</table>\n<h4 id=\"vendor\">Vendor</h4>\n<p>Provides information about the vendor, usually the dealer, that the customer has requested service from.</p>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Vendor Sequence</td>\n<td>A number used to track the history of this piece of data.</td>\n</tr>\n<tr>\n<td>Vendor Source</td>\n<td>Name of the source that created this ID.</td>\n</tr>\n<tr>\n<td>Vendor ID Value</td>\n<td>The ID of the vendor.</td>\n</tr>\n<tr>\n<td>Vendor Name</td>\n<td>Name of the vendor or dealer.</td>\n</tr>\n</tbody>\n</table>\n<h4 id=\"provider\">Provider</h4>\n<p>Identifies the service provider that originated the lead.</p>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Provider Name Part</td>\n<td>The part of the name of the contact. Accepted values: <code>first</code>, <code>middle</code>, <code>suffix</code>, <code>last</code>, <code>full</code>.</td>\n</tr>\n<tr>\n<td>Provider Name Type</td>\n<td>The type of provider. Accepted values: <code>individual</code>, <code>business</code>.</td>\n</tr>\n<tr>\n<td>Provider Name Value</td>\n<td>The text of the name.</td>\n</tr>\n<tr>\n<td>Service</td>\n<td>Name of service that originated the lead (subsource).</td>\n</tr>\n<tr>\n<td>Lead Type</td>\n<td>Type of lead. Accepted values: <code>internet</code>, <code>phone</code>, <code>showroom</code>, <code>campaign</code>.</td>\n</tr>\n</tbody>\n</table>\n"
        }  

    ]
}