Managed SFTP For Criteo
Give Criteo a stable, monitored SFTP source for catalog feeds and customer-data files — no server of your own to patch and no box exposed to the internet.
See File TransferCriteo runs on a current product catalog. Catalog feeds — and the customer-data files behind audience targeting — are delivered over SFTP or FTP on a recurring schedule, and the ads are only as good as the freshness of that feed. The part that breaks is rebuilding the catalog file in the format Criteo expects and getting it delivered on time, every time the feed runs.
Files.com is the SFTP endpoint that runs that delivery. Your commerce platform, PIM, and partner systems send source data to your Files.com site over SFTP, FTPS, or HTTPS; an Automation validates each one, converts it into the catalog or customer-data format Criteo expects, and delivers it to Criteo on the schedule the feed runs. Every transfer is logged, so you have a record of exactly which catalog reached Criteo and when.
Give Criteo a stable, monitored SFTP source for catalog feeds and customer-data files — no server of your own to patch and no box exposed to the internet.
See File TransferConvert and reshape source CSV, XML, and JSON into the catalog or customer-data format Criteo expects, and pull values out of each file to route it, before it goes out.
See Transform & ExtractAn Automation rebuilds each catalog feed from current source data and delivers it to Criteo on the cadence the feed runs, and retries on failure instead of paging someone.
See AutomationsEvery catalog and customer-data file that goes to Criteo is logged — what was sent, when, and by which workflow — so you can answer exactly which feed reached Criteo.
See The Audit LogReceive, transform, route, and audit every file moving to and from Criteo — on one platform, with no server of your own to run.
No credit card required • Free for 7 days • Live in minutes