Why I am receiving this alert and how I fix it?
Conversion API (FACEBOOK) was implemented through the partner Shopify, not manual.
I am having the same issue. All of a sudden on June 15 Shopify started sending server side events to the Facebook Conversion API, duplicating our FB Pixel data and introducing a bunch of errors. Hoping we get some resolutions ASAP, our conversions took a big hit.
Server External ID Not Matching to Pixel External ID for ViewContent Event
Server Sending Invalid Match Key Parameters for ViewContent Event
Server Sending Invalid Match Key Parameters for AddToCart Event
AddPaymentInfo Event Missing Some Deduplication Parameters
I am experiencing the same and also used the Shopify partner integration.
hi guys, same problem here, do you solved in some way?
Same problem here. Would love to have this fixed asap.
Hi everyone, I found out what’s going on here.
When Facebook updated their API a couple weeks ago, it caused us to start seeing this error. I’ve been told by a Shopify rep that Facebook has pushed out a fix to resolve the error. However, this error is not related to the problems we’re having with missing events and poor conversions.
The same Facebook API update that caused the error also implemented additional filtering that rejects events from iOS 14.5+ users who have not opted-into tracking. This is by design.
Is there any update on this? It’s July 12th and we’re still seeing this error in our FB account regarding shopify
Yes I also have this issue as well, and I need a resolution. Is this a Shopify issue or a Facebook, or both.
When you say “This is by design” do you mean that these errors are expected, and meant to make “the community” try and force apple from removing the opt-in?
No, I mean that the errors are irrelevant, the errors are benign and not related to any of the performance issues we’re seeing. The discarded events that are hurting Facebook’s ability to track conversions and wrecking our ads are being discarded by Facebook on purpose in order to comply with Apple’s policies. Has nothing to do with the External ID errors.
These errors are annoying and supposedly shouldn’t be showing up anymore, but they aren’t actually harmful.
Thanks for the quick response to this. I was brought in by a client to try and help resolve errors he was seeing on behalf of his client. So I am coming to this looking for a solution, but unfortunately I don’t have a ton of ground-level knowledge of the platform.
What you’re saying, if I understand is that these errors can be disregarded and are unavoidable due to the new iOS opt-out mechanisms?
No, the errors have nothing to do with iOS 14.5 except that they happened to start appearing at the same time as an update to the API. If they are ALSO having problems with tracking conversions, then yes, that’s from iOS 14.5 opt-outs, but not related to these errors. A lot of people in this thread are conflating the two because of the timing.
Here is what Shopify support had to say:
Our developers and the team at Facebook have definitely noticed a large increase in these errors, and it appears to be due to an updated implementation in Facebook’s CAPI version 2.
We have heard back from Facebook, and they have noted that these errors will not be impacting Pixel performance on your store. As well - they have notified us that Facebook has removed the new instances of this error related to External ID not matching. Can you please review your Facebook Pixel, and let us know if you’re seeing any new instances of this error? The error may still exist historically in the data of your Pixel, but going forward Facebook has mitigated this issue.
did you ever find a solution? i really need help.
Did you ever find a solution? i really need help.
Did anyone find a Soluton yet?
I just started having this issue this week 
I have no issue. Contact Facebook ad manager and shopify they will get it fix for you . But the sales has declined tremendously since a few days ago I don’t know if it is related to this.
Yeah my sales seemed to be low all week too until I finally saw these errors today and it said it first noticed the error 6 days ago.