Import the Product Feed

feed overview pentaleap requires an up to date product feed to create campaigns, make ad decisions and run the system the specifications for the file are listed below for more lightweight testing of the pentaleap system, it's possible to work with only an mvp file (minimum required data specifications can be found in the section “ docid\ ep2aiik3d1hhrxi2vjiv4 ”), which contains a limited set of columns however, please note that this approach may result in certain limitations in functionality a sample or dummy version of the product feed can be tested in the pentaleap ui to quickly check that it meets the requirements for a full load and deltas (see below), your team will be provided with an ftp folder for secure and regular transfer of feed files pentaleap also supports file upload via link important gtin must match the product id sent in the ad request for the system to work optimally please ensure that the identifier for each product sent in the ad request matches the identifier set in the gtin field in the product feed feed file specifications best practice with all fields product feeds should be uploaded automatically via ftp we recommend that the feeds are updated at least daily it’s also possible to upload a product feed through the platform’s web interface scope all active retailer products true 110,110,110,110,110,111 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type feed file specifications delta feeds in addition to a total product feed representing the current state of all products, there is the option to provide delta feeds representing only changes compared to the previous state providing delta feeds rather than a full refresh means that the amount of data to be processed can be reduced heavily, allowing the products to be updated more often e g hourly using deltas also removes the sharing of unchanged, redundant data which is more efficient and cost effective for all delta feeds need to be provided in three separate files in separated folders one for new products to be added, one for changed products to be updated and one for products to be deleted the following table shows the differences between the different feeds which can be provided true 220,220,221 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type