Yo, buds! Warm greeting from Minsk.
We run CC sweeps for a wide range of GEOs from FB with pixel implementation.
Click - Prelander - Lander - Billing page (FB pixel fires on this stage).
I know that some advertiser do not manage pixel on their landers and some do.
For those who work with pixel, their is a permanent discrepancy between tracker and FB stat. which is not higher than
10% average and it depends on the volume.
But we have faced the difference more than 75% on big volume. In FB we have almost twice more than in the tracker.
Every FB lead has its unique FB click id, so it makes us think, that all the leads are real users. But unfortunately the quantity of extra leads in FB does not equal to the number of billed users (due to the advertisers feedback).
So we have reasonable questions: what is the nature of this difference between FB and the tracker?
Appreciate every opinion and answer, thank u in advance, fellow experts 
Привет из Москвы)
Check if the pixel is anywhere else on the site. As an example, forgotten on another landing page your pixel or costs 2 events on the page
Are you using other traffic sources along with FB? I've seen this happen a few times when people promoted something on multiple sources... so let's say they click an AD on google, but later on they also click an AD on FB and the conversion get's attributed to both sources, so it's like a duplicate.
But yes, it could be also a tech problem or a failed setup with multiple postbacks/pixels being present on the offer pages, as dontfarm suggested.
Thank u, guys for sharing your thoughts. Will keep u posted once find the solution
Отправлено с моего iPhone используя STM Forums
I had a similar issue when promoted an offer where the thank youpage had all of the affiliates pixel (about 15 different ones).
FB conversion campaign let you choose the time for the conversion (1 day click/7days view).
What means if a user seen my ad but later clicked on other affiliate ad and converted, Facebook pixel fires for my ad and the other affiliate ad aswel.
Don't think that's your issue, might be something similar
Sent from my Redmi Note 6 Pro using STM Forums mobile app