Customizing product data feed

Thanks for the help so far @dov.derin . I think the Klaviyo Product feed would be preferable over a web feed so we can show products relevant to the customer.

So the question would be how do we access that feed data in a table. That article you’ve referenced is related to the flow event data, but I’m not sure how to pull a product feed’s data into the table?

Also the feed preview seems to only be available on web feeds. The Klaviyo Product feed only has the option to edit (no preview) so if I was able to use the product feed in the table, I’m still not sure what data objects the feed contains:

Hi @TheSuburbs,

Thank you for your follow-up note.

Apologies if it wasn’t clear in the original post, however, Klaviyo won’t be able to pull in items from a product feed into a table block. The only way to populate data through a table block is to either use a web feed or use event-variables in the flow email. This was the rationale behind my original suggestions. Moreover, displaying a secondary image (your original goal) can only be achieved through one of these two methods (web feed or event-variables). For instructions on displaying a secondary image using event-variables, you’ll want to look at the thread I linked in my previous reply. It contains the code you need to achieve this.

I hope that helps!

Hello Team,

One of our client want to add custom feed from our API to klavio. Can you provide us sample JSON format in which we need to provide required feed. 

Thank You!!

Hi @varstreet.pravin,

Thanks for inquiring about working with custom feeds and API for Klaviyo. 

In order for the mapping step of the catalog setup to work, some required fields must be included for each item in the feed:

● Unique ID ($id): can be text, numeric, or alphanumeric, but must be unique

● Title ($title): the name of the item

● URL ($link): the website at which a person can find this item

● Image URL ($image_link): a URL at which the image for this item is hosted

● Description ($description): a text description of the item. Note: The Unique ID of an item in the feed must match the item ID included in the metric on which you want to base personalized recommendations. 

 In addition to the required fields above, we also recommend passing the following optional mappable fields:

● Price ($price): numeric item price, no currency symbol

● Categories (categories): comma-separated list/array of categories, tags, or collections associated with an item

To view other examples, I’d recommend viewing our Getting Started with API doc as well as the Guide to Adding a Custom Web Feed in an Email article. We also have a good amount of community members writing about different areas they’ve run into regarding custom feeds and API I would look into as you come across other problems!

Hope this helped!
Alex