• Resolved lawandmoore

    (@lawandmoore)


    I am getting the following error using this plugin

    Server Sending Invalid Match Key Parameters for ViewCategory Event

    Martin

Viewing 15 replies - 16 through 30 (of 39 total)
  • Simon

    (@simonskyverge)

    Hi @fcrowe,

    Thanks for letting me know! We’ve been made aware of the issue you’ve mentioned, and we’re currently awaiting feedback from the Facebook team on how to get this resolved.

    You can read more about this on our forum sticky post: https://www.ads-software.com/support/topic/missing-required-information-from-developer-error/

    Cheers,

    Simon.

    Simon

    (@simonskyverge)

    Hi @mortenz and @fcrowe,

    I’m afraid we haven’t got too far with the Invalid Match Key error. Facebook have noted that there is an issue with this error, though they suggest it should only happen in rare cases.

    I have asked for further details around the actual message which triggered the error, though due to privacy concerns, I’m not able to be given that data.

    My team had another look into this problem, and they confirm they cannot share the logs with you as it is considered sensitive and our policies prevent us from doing so.

    I totally understand the response doesn’t resolve the problem for you an your partners, however the team highlighted that the issue seems to affect a sample incredibly small (only 2 instances) out of over a thousand ViewContent events that have been sent via server in the past week.

    Apologies for the inconvenience this may be causing. As we are restricted in what we can share, I’m unable to further assist with this issue.

    If you’d like to provide any feedback regarding our platform or processes, you are more than welcome to fill out our feedback form that goes directly to our teams who make changes to the platform: https://www.facebook.com/help/contact/2682288832563

    My suggestion, if you’re still seeing this issues occur, would be to open a conversation with their team directly at: https://www.facebook.com/help/contact/552096935652452 and mention that the Facebook for WooCommerce uses Server to Server API to record events. Within these logs we see that all parameters are included that Facebook requires. Yet in the Facebook front end an error is appearing that suggests the ip_address and user_agent is missing or invalid. Could they please share steps to diagnose why the error is occurring if the information is already being sent?

    If I hear anything further, I’ll also circle around and let you know!

    Cheers,

    Simon.

    Hi all,

    I fixed this by abandoning that old pixel and generating a total new one. I also deleted the plugin. Then I copied the new Pixel Code directly onto the <head> before reinstalling the app. That fixed the issue…but unfortunately I now have data from two different pixels – which isn’t ideal, but I’m hoping this new one doesn’t crash one me again.

    Hi all,

    Is there any news?
    I’ve been following this topic since I had this problem.
    How can we fix it? Website performance is worse than ever…

    Simon

    (@simonskyverge)

    Hi @begumyildirim ,

    The latest we’ve had from the Facebook team is that they’re looking into providing more information for this error in a future release, such as showing the affected URL and the parameter/what is wrong with it. Though they did also mention that even with some additional details, we would not be able to solve the problem, as it can be at the platform level. I hope the additional information would let us try and work around it though!

    They weren’t able to pass along an expected date for release, though did mention that they usually see some features/improvements added after the holidays.

    It seems that at this moment, we’ll need to wait for this release before looking at the Invalid Match Content parameter further as all logging and examples that we were able to find so far showed that we already include the required parameters.

    Cheers,

    Simon.

    I guess I need to find alternative plugins because I cannot afford my advertising and traffic budget to sales.thanks for answering

    Simon

    (@simonskyverge)

    Hey @begumyildirim,

    Sure thing! I’m sorry that the plugin didn’t meet your needs on this occasion. If you’d like to keep the plugin for the product syncing side of things, that should still be possible. You can then use a snippet to disable the pixel integration.

    Of course, I completely understand if you’d like to use one plugin for both and can find a suitable alternative.

    Can you please let me know if there is anything else I can help with?

    Cheers,

    Simon.

    Thank you I’ll keep it in my mind

    amandaenchanted

    (@amandaenchanted)

    Hi,

    Is there any news on this? I still seem to be having the same issue

    Thanks

    cekaraz

    (@cekaraz)

    Hi,
    same issue here for viewcategory and viewcontent on IP and Useragent.
    I tried to mark it as resolved, but the issue came back again. Any hint on how to solve this ?

    Any updates, we are facing the same issue.

    If this issue happens with the official plugin and is Facebook side is a problem…

    I have the same issue… Please let me know if it’s better to change the plug in in this case.

    • This reply was modified 3 years, 10 months ago by apeterikmj.
    mohsin

    (@mohsinjaved0703)

    Hi,
    i am saving same issues please give me alternate solution to this problem. I have been wasting my time and money because my ads are not performing due to these issues. Please let me know about any permanent solution

    I am having the same issue.
    Just wondering, why the status of this topic is ‘resolved’ while I am not able to find the solution. Do you have any more specific guidance on what we have to do to solve the issue with Facebook, and what appears to be this “Facebook for WooCommerce” Plugin?

    I am having the same issue.

Viewing 15 replies - 16 through 30 (of 39 total)
  • The topic ‘Server Sending Invalid Match Key Parameters for ViewCategory Event’ is closed to new replies.