Facebook Product Attributes - Introduce Attribute Mapping

[lytesaber]

What happened?

This is not so much a bug report but an architecture / data issue with the module. On installation of the Facebook for Magento 2 module it creates 43 different product attributes with a prefix of "facebook_" which cover a large amount of the category-specific fields as outlined in the commerce platform documentation: https://developers.facebook.com/docs/commerce-platform/catalog/categories/#cat-spec-fields.

While this may be done with good intentions dumping 43 new product attributes into an existing product catalog that already has attribute data configured just creates duplicate and needless attributes in the catalog. This bloats out Magento's data set which Magento recommend in their best practice to "Remove non-used product properties". The majority of the attributes are either duplicates of default Magento attributes such as color or manufacturer / brand, where other's will be completely irrelevant to 99% of retailers product catalogs such as "facebook_digital_zoom" or "facebook_health_concern" which are very specific to the type of product being sold.

Instead of dumping 43 new attributes into Magento's dataset, introducing attribute mapping to these Facebook product attributes would be a way more efficient way of going about pushing a product catalog's data to Facebook. This would also have the added benefit of allowing store owners that already use Magento's default attributes such as Manufacturer / Color or custom attributes that they already setup in their catalog to be mapped to Facebook. This would also avoid the need of populating out the equivalent Facebook attributes that already exist as custom attributes in their catalog.

Quite a few other Magento integrations include such attribute mapping functionality avoiding the need for excessive attribute creation for data that's already present.

Magento Version

2.3.7-p2 / 2.4.3-p1

Plugin Version

1.4.4

Relevant log output

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct