content_ids including SKUs – a problem

  • Resolved jesperh95

    (@jesperh95)


    4 years, 3 months ago

    Hi,

    It seems like the “content_ids” created for the catalog and used by the Pixel is created by a combination of the SKU of the product and the post-id of the product in the form “‘SKU’_’post-id'”. I think this is a problem, since if I want to change the SKU of the product, the Facebook for Woocommerce plugin will recognize this as a new product. Previously the “content_ids” have been created on the form “wc_post_id_xxx” – so I wonder why this has been changed, and whether there is a possibility to change this back or in another way make sure that the content_id stays the same even though the SKU is changed.

    Because of this problem, the catalog I manage have the same products showing several times, because the same product now has 3-4 different content_ids in many cases.

    I hope you can help in solving this issue, so we can make sure that products are not dublicated just because the product gets a new location on the warehouse.

    Best regards,
    Jesper

Viewing 6 replies - 1 through 6 (of 6 total)

  • In have the same problem because I use WPML. I already suggest to add an hook or filter to enable us to customize the identification of the product

    https://github.com/facebookincubator/facebook-for-woocommerce/pull/1197

    Hi @jesperh95 and @miguelfspinto,

    Thanks for reaching out about Facebook for WooCommerce! I’m sorry that the way the IDs are being created is causing this problem for you.

    I can certainly run this issue by our engineering team so that they can look into this further and see what changes may need to be made in order to prevent duplicates from appearing in Facebook. As soon as I hear back, I will be back in touch to let you know what I find out. Thanks so much for reporting this to us!

    Thanks,

    Jennifer

    Hi @jesperh95 and @miguelfspinto,

    I discussed this with one of our developers. The reason this has changed is related to the way that we are (and were previously) syncing products to Facebook. We were originally syncing using the API, but after moving over to syncing via a feed file, the IDs being set this way was no longer an issue, as any products not included in the feed generated at the scheduled time would be deleted from Facebook. However, as we are now back on the API method, the existing products that were changed will no longer be deleted automatically the next time the sync runs.

    We have logged a ticket internally for our developers to look into this further. While I don’t have an estimated time for resolution right now, please know that our team is now aware of the issue and will be investigating making this change.

    Thanks so much for reporting this! Can I help with anything else for now?

    Thanks,

    Jennifer

    Hi @jesperh95 and @miguelfspinto,

    It has been a while since we heard from you, so I’m going to mark this topic as resolved.

    If you’re still experiencing issues please take a look at our documentation for more information and create a new thread if you have further questions.

    Thanks,

    Jennifer

    I already submitted a merge request. I am waiting you deploy the changes.

    Hi @miguelfspinto,

    I checked the GitHub repo and I see the pull request. As we’re partnering with Facebook on this, it’s not quite as simple as merging your changes, I’m afraid. That said, I’ll make sure our development team is aware of this. While I can’t promise its inclusion, I can ensure that our team will give it due consideration.

    Thank you so much for your submission!

    Julie ??
    SkyVerge

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘content_ids including SKUs – a problem’ is closed to new replies.