-
Notifications
You must be signed in to change notification settings - Fork 34
[Feature Request] Need Customizations Option in Catalog Synchronization #34
Comments
Great feedback, @hiimkhaled, thank you so much for sharing! All very important for good experience. We've been already exploring some of the ideas you proposed: #1 (SKU vs ID) – we introduced SKU / ID toggle for product feed in one of beta versions (not publicly available), but we still need to implement it for Conversions API / Pixel and it can be a bit tricky. This is something definitely on our radar, will comment in this task once we have any updates #2 (GPC mapping) – in our backlog but it's a larger effort so this may take a bit of time to have it shipped #3 (disable catalog sync) – this is implemented in one of beta versions, will soon port to |
Thanks for your quick reply, I am excited to see the new features coming. If you have beta tester program, I would like to join. |
Thanks for your interest! We're currently running Instagram Checkout beta for Magento 2 with a very limited number of sellers in the US. We'll definitely make announcements for any new beta programs. |
Hello,
Thanks for developing the beautiful extension, I've been waiting for this long. I have some feature requests that will be more useful for everyone.
1. OPTION TO MAP CONTENT ID BY SKU
I have previously installed the extension and noticed that it is being mapped Content IDs by Database ID rather by SKUs. We have offline events integration and some other integrations all of them identifying by SKUs. So it was not possible to use the much awaited extension. There's still no option to change the Content_ID field and Pixel sending wrong IDs.
2. GOOGLE AND/OR TAXONOMY MAPPING

I think a dropdown/text option in category edit page to define Google Taxonomy is very important. Single page approach can be also fine as I am currently using Amasty Feed which has an standalone page to map all local categories with Google:
4. OPTION TO MAP ADVANCE ATTRIBUTES

This mapping helps advertisers map their local attributes to the Facebook catalog requirement, here's how my current extension developer did it:
If you have no plans to develop last two features in the near future, at least the first feature is very important, otherwise people like me can't use this extension.
I think you should also give us an option to disable catalog synchronization when we may have more advanced feed extensions so we can only use the Conversion API.
Thanks
The text was updated successfully, but these errors were encountered: