
Feeds vs. Product Importer API
Both feeds and the Product Importer API serve as tools for delivering product information and generating product datasets, but they are tailored to distinct requirements and use cases.👍 Feed vs. Product DatasetBelow is a detailed comparison:
- The feed is the raw input file provided by the client, while the product dataset is the organized and processed output created by Criteo for use in campaigns.
- Feeds require ingestion and transformation to create product datasets that are ready for operational use.
Feature | Feeds | Product Importer API |
|---|---|---|
Data Format | XML, CSV, JSON | JSON |
Ingestion Speed | Slower, due to file processing | Faster, enabling almost real-time updates |
Automation | Requires manual uploads or scheduling | Fully automated via API endpoints |
Flexibility | Limited | High, with granular update capabilities |
Use Case | Suitable for small catalogs or periodic updates | Designed for large catalogs and updates |
Which to choose?The Product Importer API is perfect for clients with extensive inventories (over one million products) who require faster data ingestion and more control over product updates. In contrast, feeds are better suited for simpler scenarios (smaller product counts, one ingestion per day) or when API integration isn’t possible.Head this way for the Feed upload guide, or this way for the Product Importer API guide.
If you need assistance to choose between feeds and/or the Product Importer API, please contact your Criteo representative.