• Resolved nilewm

    (@nilewm)


    I setup my product feed attribute for ‘g:id’ as the ‘SKU’ value. That way, when the products go into the catalog, the content id’s are the product skus.

    Since my products all have sku’s, when the viewcontent event is triggered on my FB pixel, the sku should be pulled from the product and match the item in the FB catalog to my understanding.

    However, I’m getting an error where the id’s are not being found in the catalog. I’ve checked the catalog and it appears that the product id’s are all set to the SKUs. The product skus are all properly implemented on my website products.

    I’m not sure why it’s reporting that it is unable to find the items in the catalog.

    Can someone help me with this issue?

    On another note, there is no ‘brand’ option in the value dropdown menu. I’m not sure why that would be?

    The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)
  • Hi,

    Thanks for using our plugin and reaching out to us.

    With regards to your issues at hand:

    • When you add your SKU to the g:id field of your Facebook feed than you also have to make sure that those SKU’s end-up in the content_ids value of your Facebook pixel and CAPI integration. When you are using our Facebook pixel and CAPI feature than that is not going to work properly as our plugin ads the product ID to the pixel and CAPI. In that case you would also have to use the product ID for the g:id field mapping. Please see: https://adtribes.io/align-facebook-catalog-facebook-pixel/
    • With regards to your brand question: WooCommerce out-of-the-box doesn’t come with a brand attribute so you would have to add brands to your products by adding your own attribute or use a plugin for that. Once you did then changes are big you’ll find that attribute in the drop-downs.

    Hope this helps?

    Thread Starter nilewm

    (@nilewm)

    I am struggling to properly link my website products to the catalog using the feed. I set the ‘g:id’ field value back to ‘product ID’ as the article you previously sent me said to do, but it is still not working properly.

    1) The Chrome Pixelhelper is stating a viewcontent event error because the item is ‘missing from my catalog.’ The item id reported by the Chrome Pixel Helper appears to be the SKU I set on my woocommerce website (but does not work when g:id set to SKU OR Content ID).

    The items are, in fact, in my catalog, but are obviously not lining up properly for some reason (content id).

    Can you please help me resolve this catalog issue?

    2) As for the brand, I was able to use the static value and set my brand name since I only have one brand on my entire site.

    Thread Starter nilewm

    (@nilewm)

    I ended up inputting my Facebook Pixel ID in the settings on product feed pro and it appears to connect to my catalogue properly now.

    However, now I’m having another issue.. I use a plugin (pixelyoursite) to implement the FB Pixel along with the FB API, now events are being duplicated probably because the Pixel code is also on Product Feed Pro.

    In my line of thinking, I should try to turn off the Pixelyoursite plugin and manually input the Facebook Conversion API in the header on my website. This way the pixel on product feed pro captures browser events and the API in the header script captures server events. Is this what I should do?

    Yes, you can’t use both the Pixelyoursite plugin and our FB pixel and CAPI plugin as the eventID’s sent (meant to de-duplicate events) are not the same.

    Thread Starter nilewm

    (@nilewm)

    Got it.

    I turned off the PixelYourSite plugin and am using your CAPI plugin for the pixel.

    I then plugged in the FB API script in my header, which looks something like the following:
    <meta name=”facebook-domain-verification” content=”123456789abcdefghij”>

    This is all I need to do for the API to be connected, correct? I’ve double-checked that the browser is working, which it is so I’d just like to confirm the API.

    I turned off the PixelYourSite plugin and am using your CAPI plugin for the pixel.

    –> You need to enable both the Facebook pixel and Facebook CAPI from our plugin. Not sure if you did so? Both the pixel and CAPI send over events. Facebook will then take care of the de-duplication.

    Not sure why you added the FB API script in your header? That is not needed for our plugin.

    Thread Starter nilewm

    (@nilewm)

    I’m a little confused..

    I added the Facebook Pixel ID in the field within the plugin settings.

    Where do I add the CAPI meta tag or token?

    Thread Starter nilewm

    (@nilewm)

    Or is that a paid elite feature only?

    Yes it is, see:
    https://adtribes.io/facebook-conversion-api/

    Unfortunately, per the WordPress forum guidelines, we’re not allowed to discuss our paid Elite plugin here so for any questions about our paid plugins, please contact our support team directly.

    Thread Starter nilewm

    (@nilewm)

    Can I implement the CAPI separately and keep the pixel info in productfeedpro as I mentioned above? I’d rather not pay for the elite just to get the CAPI to work.

    If not, what if I just use productfeedpro for the facebook catalog and then implement the facebook pixel and CAPI separately? Or would this not work because the pixel and CAPI aren’t used in the productfeedpro plugin?

    If not, what if I just use productfeedpro for the facebook catalog and then implement the facebook pixel and CAPI separately

    Yes that could work as long as you make sure that the pixel and CAPI you will be using are sending over the product ID in the content_ids parameter of your pixel so the feed and pixel/capi are aligned.

    Hi,

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

    Please do not hesitate to reach out to our support-team again whenever you need our help.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘ID not linking to product in FB catalog?’ is closed to new replies.