Facebook Conversion API tag send browser events

Stape feature request
1

Hi,

I noticed recently that the Facebook Conversion API tag template for server-side containers didn’t take care of sending back browser pixel events to the client.

This means that Stape customers have to keep a full Meta pixel tracking set up installed on their client-side GTM, effectively overloading the frontend.

Why can’t the server-side CAPI tag have a toggle that would allow the tag to care of browser events as well?
Some competitors already do it (i.e. Addingwell on their Meta tag template GitHub - addingwell/meta-conversion-api-tag)

Best

1 Like
2

The option you are referring to is a custom-made from addingwell. You’ll see that their other tags do not have this feature. However it would be great to have this feature in common CAPI tags as well. But the logic behind is same.

3

I realize it’s custom made. What I’m requesting is for Stape to make it too :blush:

1 Like
4

Hey @Lucas_Adbroad thanks for brining this up.

We will not be adding such functionality, because its a bit pointless from our perspective, which is to say the following:

  • If your concern is page speed and frontend load, you should really just stick to CAPI and forego the Pixel altogether.

  • if, however you are looking to reap the benefits of the client-side hits, you should really be relying on the entirety of fbevents.js (which packs a lot of functionality), and not just the /tr tracking hits via sendPixelFromBrowser()

1 Like