Sign in

Welcome to our Support Center

Get help with integration and live campaigns

Welcome to our Support Center. Get help with integration and live campaigns

Criteo Feed Specification (Job board)

The product feed is a data file which contains organized information about all the job offers on your site, and this information will be used to build the dynamic ads.

In this article, you will find details about what you can include in your feed and how to format each field.

It is important to keep in mind the following points when building your product feed:

  • Product information should not contain HTML tags or style tags
  • The product IDs in the feed must match the product IDs passed in the tags.
  • To make sure Criteo can retrieve your product feed, please use one of these formats:

Format

Detail

Download

CSV/TSV

This format is based on the Comma-separated value or the Tab-separated value. The header must be declared in the first row of the file.Field names can contain spaces or underscores (e.g. image_link or image link)

 Feed example

 XML

This format should respect the basics of the XML structure. Products are represented by a set of XML nodes. The product list must start by <?xml declaration tag. 

 Feed example

For more information regarding the protocols that can be used to import your feed check how Criteo imports your feed. 

1. PRODUCT INFORMATION TO PROVIDE

1.1. MANDATORY FIELDS

id

This field is required for all products in the feed, and cannot be empty/blank.

The id is a unique alphanumeric product identifier that represents one, and only one, job offer.

  • Character Requirements: The id must only contain ASCII characters, and must not contain quotation marks.
  • Limit: 240
  • Type: String
  • Example: 123456

title

This field is required for all products in the feed, and cannot be empty/blank.

The title is the job title. This will be used as the main text descriptor in the banners for a given product.

  • Character Requirements: The name must start with a letter or number.
  • Limit: 150
  • Type: String
  • Example: Sales Consultant

link

This field is required for all products in the feed, and cannot be empty/blank.

The link is the job offer’s dedicated detail page. The link is usually, although not necessarily, unique to a given job offer. The job information on this URL should match the corresponding information provided in your feed. Please specify the protocol (http:// or https://) for all URLs.

  • Character Requirements: The link must start with the protocol (http:// or https://) followed by the full URL of the product detail page. All symbols must be encoded. Eg. $ must be replaced with %24. Including non-ASCII characters such as non-English letters.
  • Limit: 1024
  • Type: String
  • Example: http://www.jobsite.com/sales/123456.html

categoryid1

The categoryid1 is the first-level category to which the job offer belongs (you may provide up to 3 category levels in your feed but only one can be used for CPC-optimization). For instance, you may fill this field with the job sector.

  • Character Requirements: N/S
  • Limit: N/S
  • Type: String
  • Example: Computing

price

The price is the salary of the job (yearly, monthly, p/h, etc.). Only populate price with the numeric price using a period (.) as the decimal separator and no thousands separator.

  • Character Requirements: The decimal separator must be a period (.) with no thousands separator.
  • Limit: 14
  • Type: String
  • Example: 1199.99

categoryid3

The categoryid3 is the job offer’s location.

  • Character Requirements: N/S
  • Limit: N/S
  • Type: String
  • Example: London

1.2. HIGHLY RECOMMENDED FIELDS

These fields are not required, but highly recommended as they will ease campaign management, help improve performance, and/or improve shopper experience.  

brand

This field is required for Criteo Sponsored Products

The brand indicates the recruiter or company offering the job.

  • Character Requirements: The name must start with either a letter or number, and can only contain ASCII characters. Remove all HTML tags from this field, including style tags.
  • Limit: 70
  • Type: String
  • Example: Criteo

categoryid2

The categoryid2 is the second-level job category or priority.

  • Character Requirements: N/S
  • Limit: N/S
  • Type: String
  • Example: High

image_link

This field is required for all products in the feed, and cannot be empty/blank.

The image_link is a URL that specifies a file path to a given job offer’s image. The bigimage will be used to display the product’s image in the banners. Ideally, images should be at least 800x800 pixels and under 16MB. The image must have a Content-Type header specified, either image/png, image/gif or image/jpeg. If you restrict your images from being accessible via cURL, please whitelist our user-agent so we may display your images in the Criteo banners: curl/7.15+ (x64-criteo) libcurl/7.15+ OpenSSL zlib libidn.

  • Character Requirements: The image_link must start with http:// or https:// followed by the full URL of the product’s image. All symbols must be encoded. Eg. $ must be replaced with %24, including non-ASCII characters such as non-English letters.
  • Limit: 2000
  • Type: String
  • Example: http://www.jobsite.com/sales/123456_s.jpg

1.3. RECOMMENDED FIELDS

description

This field is required for Facebook ads. 

The description is a short piece of text that gives more information about a job offer in addition to its name. Because of the design of the banners, shorter descriptions (under 50 characters) are more likely to fit in Criteo’s formats and layouts, however, not all formats and layouts will have a description.

  • Character Requirements: The description must start with a letter or number. Remove all HTML tags from this field, including style, embed, object, and anchor tags.
  • Limit: 5000
  • Type: String
  • Example: Our client is looking for individuals who are target-driven and looking for a career. You will be expected to sell within the existing database and to identify new business within this sector...
Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk