Criteo runs on feed files: product catalogs, local inventory, offline sales. You upload them to Criteo’s server, or Criteo pulls them from yours. Files.com serves both directions: the server Criteo’s crawl reads, or the scheduled delivery to Criteo’s own. It shapes feeds from whatever your commerce platform exports and monitors every cadence, so campaigns never run on stale data.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Performance campaigns are only as good as their feeds: the product catalog that sets prices and availability, the local inventory that scopes them per store, the offline-sales files that close the loop. Criteo’s intake is flexible: upload to its SFTP/FTP, or let it pull from yours. The pipeline behind the intake is the advertiser’s to run, and it usually runs on a script and a hope.
Files.com is the pipeline, run as a service. Exports land however the commerce platform delivers, TransformScript shapes them to the feed spec, Automations stage or deliver on cadence in either direction, and monitoring catches the stale catalog before the campaigns advertise it.
Catalogs pulled or delivered, offline sales closed into the loop, and feeds that never quietly go stale.
Criteo can download feed files from your own SFTP or FTP server on its crawl schedule. Files.com is that server as a service: a permanent endpoint with a scoped credential for Criteo’s fetch, holding a fresh catalog every time it looks.
Where the setup uses Criteo’s own SFTP/FTP, Automations deliver each prepared feed there on cadence: named to convention, retried on failure, logged on every hand-off.
Criteo processes CSV, TSV, and XML feeds. The commerce platform’s export is rarely that exact shape. TransformScript converts and remaps in the flow, so the crawl always finds a valid file.
Offline-sales flat files teach the campaigns what in-store actually happened. The same pipeline carries them: exported, reshaped, delivered on cadence, with the customer data in them cleared from staging after delivery.
Store-level inventory runs as its own feed family. Folder trees per market and per store keep the feeds separated, each on its own credential, under one audit trail.
A catalog feed that stops updating keeps advertising yesterday’s prices and out-of-stock products. Delivery monitoring alerts when a feed’s delivery window closes without a fresh file.
Fresh campaign data comes from the pipeline, not from someone remembering to run it.
Push to Criteo or let its crawl pull from you: every hand-off runs on a scoped credential and writes to one audit trail, so you can say exactly which catalog file Criteo got, and when.
Files.com checks every feed against the spec you define (count, size, naming, even the file contents) before it ships. A malformed export gets caught in staging, not bounced by Criteo ingestion.
A crawl reads one path on a schedule. Automations replace the file at that path with each new export: same name, new contents. That is the exact contract a scheduled fetch wants.
The staging pipeline that feeds Criteo fans the same catalog out to Google Ads and every other destination in the media plan, each reshaped to its own spec. One export from the commerce platform feeds all of them.
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
What marketing and e-commerce teams ask most when wiring feed pipelines.
Catalogs shaped and delivered on cadence, offline sales closed into the loop, and an alert when a feed misses its delivery window.
No credit card required • Free for 7 days • Live in minutes