In order for use to create an Enrichment Automation, we often require data about the products in your digital catalog, in the form of a file, or feed.
📖 This article explains:
What type of data format can we use to create your Enrichment Automation?
Good news! We can use almost any data format you can provide us and validate it to create an Enrichment Automation that suits your desired outcome.
💡 As each Enrichment Automation is created specifically for your unique scenario and parameters, our Support team will be able to advise you on optimal data formats for your situation.
Data files, and data feeds: what is the difference?
The essential difference between a data file, and a data feed is that the former is static, whereas the latter is dynamic.
Typically, the source for your data feed, or file, is the same that you use in other areas of your business, such as your CMS, or e-commerce solution.
When to use a feed: | When to use a file: |
When data is dynamic and changes during the Flipbook’s lifetime | When data is static during the Flipbook’s lifetime |
Data fields can include:
Product/stock availability
Product descriptions
Prices and images
What data file and data feed formats can be used?
Appropriate file types for creating data files, or feeds, can be:
.xml
.csv
Google Merchant feed
JSON
All of the above file types, can be used to create dynamic data feeds, or be provided as a static data file, which will be a snapshot of the product selection at the time of creating the file.
Best practices for the data files and feeds
Be consistent with data specifications you include for all products in your feed.
Write unique, helpful, descriptive, and keyword rich content in appropriate fields (such as description fields).
Adhere to data feed specifications, if using, for example, Google Merchant Center.
Update your data feed at a regular cadence, to ensure the most up-to-date information is used.
Static vs. dynamic data requirements
The data requirements for a data file, or feed, are largely dependent on your desired outcome:
Data file requirements
For static, data files, you can download the appropriate template on which to base your product data file, from our separate guide below:
Data feed requirements
Your data feed should include as much data as possible, such as:
Product IDs or SKUs
Product name
Product description
Product variations, such as:
Color
Size
Product price
Product images, including separate images for each product variant.
Requirements for JavaScript integration
A JavaScript integration attempts to validate the SKU or Product ID with that used on your e-commerce website, and draws the relevant product data upon validation.
For a JavaScript integration, we require, as a minimum, the Product ID/SKU for each product. However, if the PDF contains product IDs, we can use regular expressions, or regex, to find those IDs instead of cross-referencing with data.
For example, we can add a regular expression that finds 6 to 10 digits. When we find a match, that will be the ID.
Then the same ID, exposed in the event, can be used to make the connection to your website.