Conversion API only

No, it’s not.

The reason is simple, we need to control both the browser and the server events so that they have the same event ID, required for deduplication.

But what about the case we just prefer to use CAPI instead of pixel (no need to deduplicate, just use CAPI)? To avoid olverloading site with scripts… and also the CAPI seems more reliable than PIXEL.

At the moment Facebook recommends using both, since CAPI events matching is not as efficient as browser events.

Because of this, we support just CAPI events.

Thanks for your reply.
One more thing: im checking the pixel helper, and i see that your plugin pushes advanced matching events such as email, first name, last name, etc. But why im not seeing FBP and FBC? They are very critical for matching users.
I checked on my browser, and i do see those cookies correctly set. So why we are not sending that info as well? Could you please check? Thanks!

You can’t see them with Pixel Helper.

We do send fbp and fbc whenever possible. Keep in mind that fbp is related to ads.

Thanks for your reply!
I was reading FB′s doc: https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/fbp-and-fbc/
For fbp is always added as a cookie whenever you have pixel installed and first party cookie.
And for fbc, yes, its the one related with ads, as its generated with the click id.
What im not understanding is why is not visible on pixel helper? and how can we verify your plugin is actually sending that info?
Could you please kindly check?
Thanks!

Hello,
Waiting your response on this. Thanks

No need to wait, you already have the answer:

We DO send fbp and fbc when possible.

You CAN’T see them with Pixel Helper.