Facebook aia Integration

Dealership inventory turns over constantly, vehicles sell, prices change, and new trade-ins arrive daily. Manually rebuilding ad creative every time a vehicle sells or a price drops is not sustainable at scale. Connecting a live feed means Meta always advertises what is actually on the lot.

1. New arrivals become eligible for ads automatically, without a campaign rebuild.
2. Sold vehicles can be marked unavailable so shoppers are not sent to a listing that no longer exists.
3. Price and mileage changes sync into ad copy without manual edits.
4. Vehicles can be dynamically retargeted to shoppers who viewed a specific VIN on the dealer's site.

A feed automation tool like Feedance removes the manual CSV upload step by transforming a dealer's existing inventory export (from a DMS, website, or third-party inventory provider) into the exact field structure and format Meta expects, on a recurring schedule.

Meta's automotive catalogs accept the same container formats used across Commerce Manager: CSV, TSV, ATOM XML, or RSS XML. An automated feed delivered via a hosted URL (rather than a one-off manual file upload) is the recommended setup, since Commerce Manager can then fetch it on a recurring schedule instead of requiring someone to re-upload a file by hand.

In Commerce Manager, the catalog must be created with the type set to Auto and the vertical set to Vehicles — this is what unlocks the automotive-specific field set and the Automotive Inventory Ads objective, rather than treating each vehicle as a generic product.

Meta's vehicle catalog uses a mix of fields shared with standard product catalogs (title, price, url, image) and fields unique to automotive inventory (VIN, mileage, body style, new/used status). Field names must be entered in English and match Meta's specification exactly, including underscores and casing, or the row will be rejected or ignored.

Additional recommended fields include trim, drivetrain, interior_color, condition, sale_price, availability, and date_first_on_lot, all of which improve filtering, matching, and ad relevance without being strictly mandatory for the catalog to process.

Feedance maps your existing vehicle inventory export, whether it comes from a dealer management system (DMS), website CMS, or a third-party inventory provider, into Meta's automotive catalog field structure, so you do not have to manually rebuild your export every time Meta adjusts a field name or you onboard a new store.

1. Connect your inventory source (DMS export, website feed, or spreadsheet) to Feedance.
2. Select the Facebook Automotive Inventory Ads template so field mapping defaults to the vehicles vertical (vin, make, model, mileage, state_of_vehicle, etc.) instead of generic product fields.
3. Map any dealer-specific column names (for example, an odometer or stock-number field with a different label) to Meta's expected field names.
4. Publish the transformed feed as a hosted URL and set a refresh schedule.
5. Add that URL as the data source when creating your Vehicles catalog in Meta Commerce Manager.

Commerce Manager lets you schedule catalog feed fetches hourly, daily, or weekly. For inventory that changes as frequently as a dealership's, daily updates are the practical minimum, and hourly is preferable if pricing or stock status changes multiple times a day, since a stale feed risks advertising vehicles that have already sold.

Feedance can regenerate and republish your automotive feed on a matching schedule, so availability, price, and mileage changes on the dealer's side flow through to Meta without a manual re-upload.

Most automotive catalog rejections in Meta Commerce Manager stem from a small set of recurring issues:

1. Missing or misnamed required fields — a column present in your export but not named exactly as Meta's specification (for example, Mileage instead of mileage.value) is treated as missing, not just mismatched.
2. Invalid price format — prices submitted without a currency code, or in an unsupported number format, are flagged as invalid and the affected listings are excluded from ads.
3. Stale availability — vehicles left marked as available after they have sold lead to Commerce Manager's Issues tab flagging mismatches once click-through or conversion data reveals the listing is no longer valid.
4. Non-English field headers — Meta requires column headers in English; localized header names in the source file will cause fields to go unrecognized even if the values themselves are correct.

Commerce Manager's Issues tab and downloadable error reports identify the specific rows and fields at fault, which is the fastest way to isolate whether a rejection is a mapping problem versus a data-quality problem.

1. Populate the VIN field even though it is not strictly required — it improves deduplication and enables VIN-level retargeting of shoppers who viewed a specific vehicle on your site.
2. Keep state_of_vehicle, price, and mileage perfectly in sync with your DMS; these are the fields most likely to make an ad feel misleading if stale.
3. Fill in as many recommended fields as possible (trim, exterior_color, fuel_type, transmission, drivetrain) — these structured fields power Meta's filtering and audience matching, directly affecting which shoppers see which vehicles.
4. Set availability to update automatically the moment a vehicle sells, rather than relying on a periodic manual check, to avoid wasted spend on sold inventory.
5. Use consistent vehicle_id values across feed refreshes so Meta can track performance history per vehicle rather than treating each refresh as new inventory.

Is Facebook AIA the same as Meta's regular product catalog ads?
No. AIA uses a separate 'Auto > Vehicles' catalog type with automotive-specific required fields (VIN, mileage, body style, new/used status) that do not exist in the standard e-commerce catalog used for Meta Ads.

What feed formats does Meta accept for vehicle catalogs?
CSV, TSV, ATOM XML, and RSS XML are all supported; a hosted, scheduled feed URL is recommended over manual file uploads.

Is VIN a required field?
VIN is a recommended field rather than a strictly required one, but omitting it weakens matching and rules out VIN-level retargeting, so most dealers include it.

How often does the feed need to refresh?
Commerce Manager supports hourly, daily, or weekly scheduled fetches; daily is a practical minimum for dealership inventory, with hourly preferred for high-turnover lots.

Can Feedance handle DMS exports that do not match Meta's field names?
Yes — Feedance maps arbitrary source column names (from a DMS export, website feed, or spreadsheet) to Meta's exact expected field names before publishing the feed.