Advertising · ScoutX → Google
ScoutX and Google feeds
Three Google feeds come out of the same inventory: a Merchant Center product feed, a Vehicle Listing Ads feed, and a page feed for Dynamic Search Ads. Each is a URL on your own domain that Google fetches.
How it works
- The Merchant Center feed is Google’s product XML, generated from live inventory rather than a nightly export, so a unit that sold this morning is not still being advertised this afternoon.
- The Vehicle Listing Ads feed is emitted in the structured format Google’s vehicle ads programme expects, which is a different shape from the shopping feed and is why it is a separate endpoint.
- The Dynamic Search Ads page feed lists the unit pages Google should build ads against, so your agency targets real URLs rather than whatever the crawler happened to find.
- All three are served from your own domain and resolved by hostname, which is what keeps a group’s stores from feeding each other’s campaigns.
- The endpoints are rate-limited — an ad platform re-fetching a large feed in a loop is a real failure mode, and it should degrade rather than take the site with it.
Other integrations
Lightspeed → ScoutX
Lightspeed DMS
Automatic unit sync from Lightspeed across every franchise you carry.
Motility → ScoutX
Motility
Unit sync from Motility, in either its XML or CSV export.
Your DMS → ScoutX
SFTP inventory feed
Any DMS that can drop a scheduled file — XML, CSV or pipe-delimited.
Questions
Google Merchant Center & Vehicle Ads questions
Do we hand these to our agency?+
Yes — they are URLs. Your agency registers them and Google fetches on its own schedule.
Is the data as current as the website?+
It is generated from the same live inventory the site renders, so a status change reaches the feed on the next fetch.
Can each store have its own feed?+
Yes. Each store’s domain resolves to that store’s inventory.