How to Set Up Field Mappings
Field mappings define how columns from your source data (vAuto CSV, HomeNet XML, etc.) map to Carfluence's normalized schema.
Why Field Mappings Matter
Different data sources use different column names:
- •vAuto:
List Price - •HomeNet:
AskingPrice - •Custom CSV:
Asking_Price
All of these need to map to Carfluence's price field. Field mappings handle this translation.
Viewing Current Mappings
bash
GET /api/v1/mappings/:integrationId/previewThis returns:
- •A list of source fields (column headers from your data)
- •The currently mapped Carfluence field for each
- •Sample values from the most recent file
Updating Mappings
bash
PATCH /api/v1/mappings/:integrationId
{
"mappings": {
"Source_Column_Name": "carfluence_field",
"Another_Column": "another_field"
}
}Carfluence Standard Fields
| Field | Type | Description |
|---|---|---|
vin | string | 17-character VIN (required) |
stock_number | string | Dealer stock number |
year | number | Model year |
make | string | Manufacturer |
model | string | Model name |
trim | string | Trim level |
price | decimal | Current asking price |
internet_price | decimal | Online/internet price |
mileage | number | Odometer reading |
exterior_color | string | Exterior color |
interior_color | string | Interior color |
body_style | string | Body type (Sedan, SUV, Truck, etc.) |
condition | string | New or Used |
description | text | Vehicle description |
photos | string | Comma-separated photo URLs |
Auto-Detection
For known integration types (vAuto, HomeNet, Elead), Carfluence auto-detects most field mappings. You only need to customize mappings for:
- •Non-standard column names in your export
- •Custom fields unique to your dealership
- •Fields that the auto-detection mapped incorrectly
Dashboard Method
In the dashboard:
- 1Go to Integrations > Click your integration
- 2Click the Field Mappings tab
- 3You'll see a two-column view: Source Field on the left, Carfluence Field on the right
- 4Use the dropdown to change any mapping
- 5Click Save Mappings