I think there is a Bug in the new Facebook Tag - if you add a Custom Conversion, the guard for standard_events_lookup[event_name] only adds "Custom" to the event_tracking_type but does not protect the following code from accessing the undefined fb_params property of standard_events_lookup[event_name], leading to a JS error and the Custom Event not firing.
Moving the for-loop into an else-block of the guard works at least as a temporary workaround.
Is this a Bug or am I using the Custom Event Mapping wrong?
All the best,
Solved! Go to Solution.
Hi @FelixHartmann ,
Thanks for reporting this issue. Your work-around might fix the problem, but before you edit the tag template I recommend you use the Tag Status Checker to see if there is a newer version of that tag. My team told me that this bug has been fixed, so I suspect that might have an older version of the tag.
Let us know if that works.
Indeed there was a new Tag Version, thank you - it has the same Change I did as my "workaround" but nonetheless good to be back on the official Template.
I had expected the tag to be the newest Version, because it was implemented just 4 days ago, but I think it might have been copied instead of being newly created... :)