Server Sending Invalid Match Key Parameters

Hi @zielakowy,

Thanks for writing in with your question! We’ve had a few merchants mention this so far and had raised a support request with the Facebook team that is still ongoing.

Through all the tests and logs that we looked into for these other merchants, we always saw that the ip address and user agent parameters were sent. So we don’t yet know why this message is appearing. The initial response from the Facebook team has been that this should not occur that often, and that they think it could be related to customers using ad-blockers. They advise to clear the issue by clicking the Resolve button in events manager and see if it continues to appear going forward.

We’ve asked the team if we could see some logging from their side to try and match that with our plugin logs. Unfortunately, due to privacy concerns, it’s not possible for Facebook to share that with us.

In which case, if you’d like to raise this further, I would recommend raising a query with them directly at: https://www.facebook.com/help/contact/552096935652452
Please make sure to include your Pixel ID, a screenshot of the error, and mention that the WooCommerce plugin uses the Server to Server API for recording these events.

I’m sorry we can’t be more help on this occasion. If I hear anything further from their team on being able to narrow down the root cause, I’ll circle around and let you know!

Could you let me know how you get on if you do decide to contact them directly?

Cheers!

Simon.

Hi there,
Just letting you know that I also reached out to Facebook about a few issues I’m seeing. My View Content is now showing the same error message “Server Sending Invalid Match Key Parameters” but when I test the event, it seems to work fine.

The Page View trigger is also saying that it hasn’t received any recent activities for over 12 days, but again, the test event works fine and the Facebook Pixel Helper also shows “green” for both Page View and View Content…so I’m not sure what these weird anomalies are about…

Hopefully Facebook responds quickly!

Well..that was quick! This is what Facebook responded with:

We have received your inquiry about Facebook Pixel showing no activity log for the last 12 days. I understand how this is important to you. Thank you for bringing this concern to our attention to ensure proper resolution is sought and provided accordingly. I am more than happy to assist you.

We looked into the screenshot that you have provided and we see that there is an error message that says “your parameter and referring URL are displayed as removed”. It seems that the Facebook Pixel was implemented through a Partner Integration Woocommerce.

In these cases the Facebook Pixel implementation is handled by the 3rd party’s platform. We do not specialize in these platforms which is why we can not provide support for them. We can only assist with Facebook Pixel implementation when the Facebook Pixels code is directly placed on the website’s code. This gives us the ability to visually find the Facebook Pixel in the website’s code and pinpoint the source of the issue.

We do not have the same debugging flexibility when the Facebook Pixel is implemented via 3rd Party Tag Manager/Integration because the Facebook Pixel code is either hidden or is manipulated to make it compatible with the Tag Manager/Partner Integration Platform.

Hi @fcrowe,

Thanks for passing on the information! While it’s true that we include the tracking in the plugin, and therefore it’s considered a third-party integration, the error messages are occurring in the events manager which we have no control over. I would love to know what event message caused the error to appear so I could help troubleshoot further. The Facebook team have said they can’t provide any further information due to privacy concerns. I would really like to get this problem solved though as quite a few merchants are encountering it!

We log all the outgoing messages for the Server to Server event tracking within the debug log of the plugin. We can also use the Test Event tool, HTML inspection, and Pixel Help Chrome Extension to see the parameters that are being tracked from the front end too. We’ve checked each one of these areas for incorrect or invalid messages and do not see any wrong or missing data.

In my email with the Facebook team, they mentioned that they have been able to see an issue in only a small fraction of logged events for the merchants they looked into. As the plugin tracking code is the same for all events, it seems to suggest there is something causing an error for a particular customer or browser/user configuration that we can’t replicate in testing.

Ideally, we need Facebook to be able to share the message that caused the notice to be shown in their event manager frontend. Or, if they can help provide a unique ID relevant to the specific event that caused the error to appear, we can look that up in the plugin logs too! As I don’t know what validation their system is running, what event caused the notice to appear, or in what conditions the notice should appear, we’re a bit stuck from this side.

That said, they mention that the pixel should be inserted into the page directly. From my previous email with their team, they verified that the error only appears for “Server to Server” events, not front end pixel events. In this case, this is using their server to server API for event tracking.

It would be great if you could ask them to confirm why the server to server API might be causing this notice to appear? And, hopefully, if they can share with you the event message that failed their validation?

Cheers!

Simon.

Hi @fcrowe,

I had another update this morning from the Facebook team. They’ve said 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 workaround 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.

Cheers,

Simon.

Hey @fcrowe,

As we’re waiting for the new release from Facebook to look at this further, let me close this topic for the time being.

If you’re still experiencing other issues please take a look at our documentation for more information and create a new thread for additional support.

Thanks,
Simon.

I am experiencing the same issue.

It seems like it is doubling up the value of conversion on my Facebook ads…