I'm not exactly sure how this should affect this Segment FB Pixel implementation, but I've noticed some duplicate PageView calls on our app and after digging around, found that fbevents.js is overwriting pushState events and calling their PageView event automatically:
(function ca() {
if (j.disablePushState === true)
return;
if (!d.pushState || !d.replaceState)
return;
var da = function() {
s = m;
m = c.href;
if (m === s)
return;
var ea = new v({
allowDuplicatePageViews: true
});
j.trackWithoutValidation.call(ea, 'PageView');
}
;
h.injectMethod(d, 'pushState', da);
h.injectMethod(d, 'replaceState', da);
a.addEventListener('popstate', da, false);
})();
Just wanted to bring that to your attention so your team can dig in further and see what is going on under the hood with FB and see if there is a better solution to getting the two to play nice together.