I am facing an issue with Facebook conversion pixel.
I have first implemented FB conversion tag for pageviews and even trcking for Search and email subscription events. It was working fine untill i implemented another FB conversion pixel with a different pixel id but with the same requirement of tracking.
After that i am facing this issue - both the pixels fire on pageviews but then they are not firing on Search or email subscription events.
I did not change any pattern while implementing the second tag. I just copied the first tag as the requirement is similar and just changed its pixel id. But niether of the tags are working for events.
If i disable the second tag then the first tag fires correctly as before but again if i switch it on then both the tags only fire on the page views and not on the events.
Any help on where i am going wrong?
When there are two Facebook tags loading on the same page there is an issue with a collision of the same objects being utilized by the Facebook library. This leads to an overwrite of some of the necessary parameters that one of the two tags may be leveraging at that time and, especially on events, will cause issues and often stops the events from even happening.
To fire multiple Custom Audience ID's, you can pass through the ID's as a comma separated list in the custom audience pixel ID mapping on a per-event basis or in the standard configuration if you want them both to fire across all instances. The following article from the learning community discusses these mappings, as well as other configurations, that you can leverage to make your tag more robust and dynamic: