“Your server is sending an empty fbc parameter…”

Hey there!

I’m getting this message in the Match Quality screen on Facebook:

“Your server is sending an empty fbc parameter through Conversions API, but we observe a valid fbc parameter being received through Meta Pixel.”

And my quality score for PageView is pretty low, so I believe I’m doing something very wrong:

Upon inspecting the network tab and cookie, I see this in the /tr link…

But I’m not entirely sure if that’s correct and if that is being sent out to facebook.

I followed this setup:

stape (dot) io/blog/how-to-set-up-meta-conversions-api-gateway

It’s the META CAPIG Gateway.

Seems to be working… And I’m indeed getting server events on my pixel, but for some reason missing that data tanking my quality score:

Can anyone help?

My website: https://lp.aros.com.br

No idea how to sort this out. If it’s a button I’m missing… a GTM tag on my site I need to install… or what.

Thanks in advance! :folded_hands:

Hello @brunoaros

Remember one thing fbc refers to who clicks on your ad.

If in addition to the adv someone enters organically this parameter is not counted.

So it is normal that unlike the other data you may notice a difference.

Fbp instead refers to the browser identifier.

To make your life easier you should use google tag manager (if you don’t already do it) in order to pass these parameters

Humm I see. It makes sense.

As for fbp, I was assuming that by using the meta CAPI gateway from Stape this would be solved. Is it not?

This one: Effortlessly set up the Meta Conversions API Gateway - Stape

What is the recommended solution and steps to make sure I have the best tracking possible?

I really thought that would sort it out this issues, but maybe not?

HI,

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.

Sorry, I’m not really sure I follow.

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:

As far as I know, using the gateway you can’t do anything else. 9.3 wow

Yeah, so I’m not sure I have the right solution. I’ll try to get in touch with support… but their replies are very superficial ending with:

“Ask the community”
“Hire our agency”

:confounded_face:

I’ll tell you again.

With the gateway, what passes passes, you as a person cannot make changes on what should be received in what way.

Even if you want assistance, what can you do in addition.

Being a closed system they too cannot do more than what you have done.

Let me know if they tell you anything new

Hi @brunoaros

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?

Also how is your pixel is setup client-side?

Could you please verify there are no other sever-side (CAPI) solutions that report to your Meta dataset aside from the CAPI Gateway?

Ah yes, indeed there is. I’ll explain:

  • Pages like this one (subdomain gp) have their own API server. So they might send server events in additiona to Stape’s Gateway;
  • Other pages like this (subdomain lp) have only the classic meta pixel installation directly on the head and body inside Framer as follows:

So when visiting pages with gp., they have their own server setup; whilst lp. pages do not.

So that’s a start.

Have you seen this @Dan ? Thanks!

@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