Facebook Unmatched Products

Hi anstoyanov,

Thanks for using our plugin and reaching out to us.

The tutorial you linked too exactly explains what to do and what attribute to link to.

If you are using our Facebook pixel feature (so no other Facebook pixel plugin) you need to map the g:id field to the product ID. Our Facebook pixel code add’s the product ID to the pixel.

Best,
Eva

Hi Eva,

as I already mentioned, I followed all from the tutorial. I have mapped g:id to Product ID and am using the same plugin for the facebook pixel. The values for content_ids: generated for the pixel is completely different from the g:id in the feed, thus I keep getting the same warning in facebook pixel event tester. What value does the pixel use for content_ids? It’s definitely not Product ID as in the feed…

Could you send me the plugin debug.log? It will help me understand how you have configured your feed and it enables me to check your pixel implementation.

Instructions on how to retrieve the debug.lig can be found here: https://adtribes.io/send-your-debug-log-to-support/

• This reply was modified 5 years, 6 months ago by evavangelooven.

Thanks, I had a look.

You are stating this:
“The values for content_ids: generated for the pixel is completely different from the g:id in the feed”
What makes you think this is the case?

I checked and they seem to align just perfect.

An example. See this variant product on this URL:
https://blubambina.com/shop/baby-boy-clothing/bodysuits-one-pieces/autumn-winter-cashmere-cute-cartoon-bear-jumpsuit/?attribute_pa_color=pink&attribute_pa_size=24m

The Facebook pixel code on it looks like this:
https://www.dropbox.com/s/lahr8syfxnesevi/variant-example.png?dl=0

The content_ids in the pixel is = 2274.

When I check the XML feed I see this (g:id = 2274)
https://www.dropbox.com/s/ny2ceg2p0b05u5b/variant-xml-feed.png?dl=0

So they seem to align just fine to me?

Please provide us with some examples of simple or variant product ID’s and URL’s you believe are wrong. Bear in mind, the parent variable products itself are not in the feed as this is not allowed by Facebook so make sure to get the full variant URL’s including the parameters when you provide those as examples.

All the best,
Eva

Example:
h/shop/baby-boy-clothing/clothing-sets-baby-boy-clothing/newborn-crochet-hand-knit-mickey-costume-photo-props-hat-diaper/ on this product it shows content_ids: [“2994”]
in the feed – /wp-content/uploads/woo-product-feed-pro/xml/ce54a0d3f1239fc526c0467f38a432ed.xml it shows <g:id>13210</g:id>

Also for the example you provided the pixel shows to me content_ids: [“2423”]
and in the feed <g:id>13579</g:id> …which feed are you looking at? Can you send me the url? I have 2 feeds, 1 for Google, and 1 for Facebook. In both the content_ids are different from the pixel… ??

In addition to my prev comment (still held for moderation), now I noticed the pixel started returning content_ids: 0 for all variation products. I haven’t changed anything…

I have also found another issue. For the facebook pixel, when visiting product page but none variation is selected, the content_ids should be the actual group_id not product id(facebook.com/business/help/1549524211985335). I tested this and facebook matches properly the product groupID and no warnings shows up. Still when visit a variation page, the ids don’t match…completely different numbers.

Please can you fix for the case above too? In my case I changed in this file woo-product-feed-pro/woocommerce-sea.php line 342 content_ids: to be the group ID rather than the product id. This fixes the warning when checking the product page when no variation is selected.

I am also waiting for a solution on my main issue…
I don’t know if the google pixel has the same issues too…
please help ??

May I ask on what version of our plugin you are? Please make sure you are on the latest version (6.4.8) as a lot of changes have been made to the Facebook implementation a couple of releases back.

Line 342 of the most recent version of our plugin shows this:

                                                } else {

So most likely you are not on the latest version?

Best,
Eva

• This reply was modified 5 years, 6 months ago by evavangelooven.

I am using the latest version yes. Yes sorry, the row number should be 341:

$viewContent = "fbq(\"track\",\"ViewContent\",{content_category:\"$cats\", content_name:\"$product_name\", content_type:\"product_group\", content_ids:[\"$fb_prodid\"],value:\"$fb_price\",currency:\"$currency\"});";

Instead of $fb_prodid it should be the group id. I hardcoded it with the sku variable, because I am using the sku as product id, but I think there should be a more elegant to do that…

I am going to assume you mean line 340?

For variable “parent” products the product ID is the Group ID so this is actually not going to make a change. Since line 340 is showing on the variable parent pages and not on the variants it should show the Group ID, which it does.

See this variable parent product on one of our test sites. As you can see it has product ID: 20075
https://www.dropbox.com/s/kntiaiioadew2ku/example-2.png?dl=0

When checking the pixel code on the product page:
https://www.dropbox.com/s/3wldg3zcpeitp2y/example-1.png?dl=0
You see, the content_id is 20075 and the type is product_group. Both seem fine to me.

The real problem here I believe, is that you are using the SKU as a product ID. That will cause misalignment. The Facebook pixel placed by our plugin always uses the product ID for the content_ids value. You need to make sure that the g:id field of your Facebook catalog feed also contains the product ID (hence, is mapped to the product ID).

Have a wonderful weekend,
Eva

I am not using SKU for the Product ID, I use sku for g:item_group_id.

I tested now not only in Pixel Helper, but in Facebook pixel diagnosis. Now the pixel matches all ids – product ids, product groups. Also works fine with google pixel. even if I haven’t done anything else, now it’s ok, but before that I was getting Unmatched Products warnings…don’t know why…

Hi,

Assuming the issue at hand has been resolved or our support is no longer required I am going to close this topic for now for housekeeping reasons.

Don’t hesitate to reach out to us again whenever you need our help.

All the best,
Eva