Ducted

Microsoft Automotive Ads
feeds.

Dealer inventory in Bing.

A smaller channel than Google or Meta, and a cheap one to add: a dealer already producing a Google VLA feed can serve Microsoft from the same mapped catalog with a second output. Same source, same mapping work, one more place the inventory shows up.

The Microsoft feed has its own shape: records are routed to a campaign from inside the feed itself, which is why target_campaign sits in the required list below; target_ad_group is optional and narrows the routing further.

What the feed needs

Generated from the Ducted Microsoft Automotive Listing template, the same field rules your mapping is validated against.

55 fields: 8 required, 12 recommended, 35 optional. 1 field changes level with the market, the product or how the record is sent.

FieldLevelAccepted values / example
countryrequiredUS
final_urlrequired
image_urlsrequired
makerequired
modelrequired
titlerequired
target_campaignrequired
vehicle_idrequired
vehicle_typeoptional
required for vehicles that aren't cars (Microsoft defaults an empty vehicle_type to car_truck)
car_truck · boat · commercial_trailer · commercial_truck · commercial_van · motorcycle · powersports · rv_camper
body_stylerecommended
cityrecommended
co2_emissionrecommended119
co2_emission_unitrecommendedg/km · g/mi
drivetrainrecommended
enginerecommended
exterior_colorrecommended
fuel_typerecommended
interior_colorrecommended
staterecommended
trimrecommended
yearrecommended2020

Field rules from the official spec, verified 2026-10-01.

Also supported, always optional (34): price, target_ad_group, address, availability, callout, contextual_keywords, condition, custom_parameters, daily_payment, dealer_discount, dealer_name, description, down_payment, due_at_signing, email, final_mobile_url, fuel_efficiency_average, fuel_efficiency_city, fuel_efficiency_highway, fuel_efficiency_unit, latitude, longitude, mileage_unit, mileage_value, monthly_payment, payment_term, payment_type, phone_number, sale_price, state_of_vehicle, tracking_template, video_url, vin, zip_code

Where Microsoft vehicle feeds get rejected

Missing campaign routing

target_campaign is required in every record (target_ad_group is optional). Feeds built for other channels rarely carry it, so it is the first thing to map.

Missing image URLs

image_urls is required: one or more URLs separated by semicolons. An empty value, or a path that is not a URL, takes the record out; a comma inside a URL is flagged until it is percent-encoded.

Missing country

Every record states the market it serves as an ISO country code. A feed without the country column fails at the first record.

No price and no monthly payment

price is required unless monthly_payment is provided for leases and finance. A record with neither is rejected.

Validate your vehicle feed for free →

From source to a live feed URL

  1. Connect the source. HomeNet, DealerOn, DealerMasters, All Auto Network, Revvable, a file, a feed URL or a REST API. No source at all? Website Indexing builds one from the dealer site.
  2. AutoMap the fields. Every source column is scored against the vehicle template and the best match is pre-filled. You confirm or tweak.
  3. Transform what needs it. Casing, currency and number formats, conditional values, fallbacks for fields the source sometimes leaves empty.
  4. Validate before you send. The health check names the field, counts the affected records and shows example rows from your own data.
  5. Serve a permanent URL. The platform fetches your feed on a schedule; feed pull tracking shows when it last did.

The rest of the automotive stack

One mapped catalog serves every channel; each page covers what that platform's feed needs.

Automotive feedsGoogle VLAMeta AutomotiveTikTok Automotive

One more channel from the catalog you already mapped.

Add a Microsoft output to an existing vehicle project, or start free and map your first.

Create free accountCheck an existing feed