+1Hello we recently set up our Adobe Commerce/Magento 2 store in Klaviyo and there are many issues with the feed.
It seems like these would be common issues and I can’t find any documentation on how the catalog feed actually works or what data they are pulling exactly but from what I can see this information is include in what they are pulling. Any advice.
Best answer by whereisjad
| Product Price | {% catalog event.VariantId integration='magento_two' %} {% currency_format catalog_item.metadata.price %} {% endcatalog %} |
| Variant Image | {% catalog event.VariantId integration='magento_two' %} {{ catalog_item.variant.featured_image.full.src }} {% endcatalog %} |
+16
Look it up under this doc https://help.klaviyo.com/hc/en-us/articles/115005254348
I think the problem your facing is similar to what is covered in this thread:
+1
Look it up under this doc https://help.klaviyo.com/hc/en-us/articles/115005254348
I think the problem your facing is similar to what is covered in this thread:
My media root is correct, the image shows, but I have items like blue shirt, red shirt, orange shirt. But the image shows the blue image for all of them, even though the JSON has the correct image path needed to display the right image for that variant.
+1
Look it up under this doc https://help.klaviyo.com/hc/en-us/articles/115005254348
I think the problem your facing is similar to what is covered in this thread:
Also that post is from three years ago, and it seems that configurable products ARE pulled in from Magento 2 into the klaviyo catalog now.
+16
inability to fully handle configurable products. Klaviyo only syncs and stores the parent product in the catalog; paired with the fact that Magento 2 does not utilize price for the parent configurable product by design leads to this behavior.
A common workaround to this, as you’ve astutely highlighted, is the use of a custom feed where each variant of the configurable product can be assigned its own sku and ID. You can find our guide on how to set up a custom catalog feed from our Sync a custom catalog feed to Klaviyo Developer Guide.
+1Well this part is completely wrong “ Klaviyo only syncs and stores the parent product in the catalog” because it does now pull in variants into the catalog. I can see them in the product catalog under the parent, and it shows their price, Klaviyo has the data to show the correct image and to potentially roll up a price to the base product, but not sure why they aren’t. I will see what support says.
+16
| Product Price | {% catalog event.VariantId integration='magento_two' %} {% currency_format catalog_item.metadata.price %} {% endcatalog %} |
| Variant Image | {% catalog event.VariantId integration='magento_two' %} {{ catalog_item.variant.featured_image.full.src }} {% endcatalog %} |
+1
| Product Price | {% catalog event.VariantId integration='magento_two' %} {% currency_format catalog_item.metadata.price %} {% endcatalog %} |
| Variant Image | {% catalog event.VariantId integration='magento_two' %} {{ catalog_item.variant.featured_image.full.src }} {% endcatalog %} |
Thanks for the info this is useful, I am a Magento developer not a Klaviyo developer so was not aware of these. I did discover that Klaviyo should have the ability to display the proper images for the variants because it is working fine in the test account I am using but for some reason not working in our “real” account.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
