the gateway replaces all the tracking you do on GTM. By doing everything himself, the only thing you have to do is open the gateway, connect it to the pixel and purchase a subdomain, he automatically passes the information on.
The argument is always the same. If the user does not click on your fbc advertisements it will always be empty
Using the gateway or not is your choice. It depends on how much you want to keep up with it.
I’m already a paying customer. I’m more than glad to pay to get this sorted out. I’ve already set it all up, connected to my pixel and subdomain. I thought this would have sorted things out. But my quality score for pageview is still super low.
That’s what I’m trying to fix.
I understand fbc only shows up when someone comes from an ad — that makes sense.
But shouldn’t fbp be sent out every time, no matter where they came from?
What else should I do to ensure the best tracking possible?
BTW, my purchase event (which is actually more important) is just fine:
The screenshot you showed originally shows massively bigger amount of server events compared to browser ones, it is very atypical to have an x3 discrepancy, so before diving into hypotheticals around fbc error (which I understand is your main issue) we need to figure out where that is coming from. If it is effectively over-reporting then the error could be related.
Could you please verify there are no other sever-side (CAPI) solutions that report to your Meta dataset aside from the CAPI Gateway?
@brunoaros well I would check what that API server is sending. It is very more likely that is sending no cookie data, rather than native Gateway dropping the ball.
I also suggest diving deeper into why is it there in the first place, you are effectively over-reporting
