Introduction

Lookup files serve as an auxiliary resource in your product feed system, providing a flexible solution for incorporating additional information that might not be included directly in the main product feed.

These files are particularly useful when you need to supplement the existing feed with extra data without altering its fundamental structure.

Key characteristics of lookup files

Purpose

Supplemental data: Lookup files are intended to store additional information that, for various reasons, cannot be directly added to the main feed. This can include extended descriptions, custom attributes, or any other data that enhances product listings.

Storage

Location on Criteo's SFTP: By default, Criteo’s SFTP servers contain a specific folder named /vlookup where lookup files should be stored. This standardized location ensures that Criteo systems can reliably access and integrate these files into the broader feed processing workflow.

File format

CSV file requirement: The lookup file must be formatted as a CSV (Comma-Separated Values) file. This format is widely supported and allows for straightforward handling of tabular data.
Separator: It is recommended to use a semicolon (;) as the separator in lookup files. This helps avoid common issues with comma-separated data, such as conflicts arising from commas within data fields.

Content structure

SKU ID and extra fields: The primary column should be the SKU ID, which uniquely identifies each product. This ID should match exactly with the SKU IDs used in the main product feed to ensure proper linkage. Following the SKU ID, each additional column should represent a separate field containing the supplemental data.

Best practices

Consistency in SKU IDs: Ensure that SKU IDs in the lookup file exactly match those in the main product feed. Any discrepancies can lead to issues in data merging and utilization.
Regular updates: Keep the lookup file updated in sync with changes in the product feed. This alignment is crucial for maintaining the accuracy and relevance of the data presented to Criteo's systems.
Secure and structured data handling: When updating the lookup file on the SFTP server, make sure to follow secure data handling protocols to prevent unauthorized access and ensure data integrity.

Using lookup files effectively allows you to expand the depth and breadth of product information available for your campaigns without overcomplicating the primary feed structure, thereby enhancing both performance and manageability.

Example file

To illustrate a sample lookup CSV file as described, we'll create a file that includes columns for SKU ID, Store ID, Price, and Tracking Code. This file will use a semicolon (;) as the separator, adhering to the recommendation for lookup files. Here’s how the sample CSV content might look:

sku_id;store_id;price;custom_filter
12345;001;29.99;CF12345A
23456;002;49.99;CF23456B
34567;003;19.99;CF34567C
45678;004;59.99;CF45678D

Breakdown of each column:

sku_id: This is the unique identifier for each product. It must match the SKU ID used in the main product feed.
store_id: Represents a unique identifier for the store or location where the product is available.
price: The selling price of the product at the specified store.
custom_filter: An extra filter that can be sent in ad calls to allow only specific products to show up pages like special sales or deals.

The columns in this example are just for demonstration purposes.

The lookup file that you send can contain any extra data that you wish to include. You can tailor the columns to fit your specific needs, adding any additional fields that provide valuable context or information for your product listings.