Falta información o no es válida

Hey @davidfranom,

I hope you don’t mind if we speak in English, I’m afraid I am not a native Spanish speaker! I’ve used Google Translate to see what I can do to help, and it sounds like you are having an error pop up in your events manager when recording an event on your WooCommerce store.

To start with, would it be possible to send over a screenshot of the error as you see it? This will let me know exactly where about it is, and what event might be triggering it. I can then take a look at your site and see if I can find out anything further with Facebook’s Pixel Helper plugin.

If you need a way to share images, I often recommend https://snipboard.io/ for ease of use.

Could you let me know when you have a moment to pass this on?

Cheers!

Simon.

Hi, thank you for answering. These are the captures.

These errors appear in the catalog manager. (Sorry some are shown in spanish by default).

Here is where the error is shown.
https://snipboard.io/J4OQ0N.jpg

When I click on the first notice.
https://snipboard.io/ygia4A.jpg

And then the second one.
https://snipboard.io/J0KvaM.jpg

I dont know if it has to do with these ones that appear in event manager.
https://snipboard.io/fSRmAh.jpg

I tell you also that I changed the product link of two items directly in the facebook catalog.

Thank’s for the support.

• This reply was modified 4 years, 2 months ago by davidfranom.
• This reply was modified 4 years, 2 months ago by davidfranom.

Hi @davidfranom,

Thanks for sharing those, that’s a great help. It looks as though there are a few different errors on those screenshots, so we might need to tackle them individually.

The first and third notices suggest that the information may be missing or invalid, and therefore also low quality. This can sometimes happen immediately after a first sync if the products have not yet been processed and customers are browsing your WooCommerce store and triggering pixel events.

What I would suggest us to do is monitor this going forward to see if it continues. If it does, perhaps we can gather more information from the Facebook screen about what event or URL was being triggered at the time. I notice from your second screenshot that it appears empty? Was this after clicking the View Details/View Report button?

The last issue is an interesting one, however. It’s one that we’ve seen a few other merchants mention but have not got to the bottom of just yet. We have an open ticket with the Facebook team regarding this notice, and their update so far is that it might be caused by customers with browser add-ons that have blocked the collection of the user agent or ip address parameters. In this case, you can click the resolve button to ignore this alert and keep an eye out for more occurences.

In the meantime, I’ve also added your details to the conversation I have with their team in case they can share any more specific details. Once I hear back from them, I will let you know!

Could you let me know how you get on with the other errors while we wait?

Cheers!

Simon.

Hi, I’ve just checked, and the empty event shown in the second capture has been solved. I think it was just matter of that users interact with the site.
Thanks for the support.

• This reply was modified 4 years, 2 months ago by davidfranom.

Hey @davidfranom,

Great to hear! I think that leaves the last issue regarding the Invalid Match Key without a real answer just yet. Once I hear back from the Facebook team on this, I can circle back around here and let you know.

Thanks again for your patience so far.

Cheers,

Simon.

Hi @davidfranom,

We’ve now heard back from the Facebook team regarding the Invalid Match Key error. They’ve said that they have seen this in their logs, though it should be a rare occurrence.

While they weren’t able to share any logs with me due to privacy concerns, they also mentioned that even with logs, the issue could be a platform issue. Something that we wouldn’t be able to resolve from within the plugin anyway.

They appreciate that it’s difficult to see what is causing the error, and so they’ve added an item to their backlog to improve the user notice, to help add additional information about why the error occurred and which validation failed. They weren’t able to say when this might be released though I’m afraid.

For now, it doesn’t sound like I’m able to do anything further for this issue. I would suggest clearing out the error notice, and if it does continue to crop up, reach out to Facebook directly to see if they have any further news on these improvements.

I’m sorry this isn’t the best of news this time around. I’m going to close this topic now then, but if you have any further questions or issues, please don’t hesitate to contact us again! We’re always happy to help ??

Cheers,

Simon.