We're doing testing having migrated from DTM to Launch. Most things look right but there's something odd going on with the Facebook pixel.
The tag is added via a rule, and then various events are triggered via additional rules based on either page load, or on button clicks.
In Launch, it looks like the page load events are getting triggered on every page load, even if the rules aren't firing.
These are all the rules:
When the page loads, the debugging output says that the rules aren't firing (except in this instance, when order confirm fires):
But the FB helper chrome extension is showing all the events firing one every page load. Admittedly most of them have the yellow error, and it looks like the right one is showing green on the right page:
... but previously (in DTM) only the relevant page event was showing in this window.
If I disable the rule in Launch then the event disappears from this list. So it does look like the code is getting fired, even though the rule conditions are not being met.
Anyone got any suggestions of what's going on?
Thanks
Ben
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
It looks like this isn't a problem with the tag, but with the Chrome Extension. The events are actually being fired each time. So I think it's not really a problem.
Is the site a single page app?
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
It looks like this isn't a problem with the tag, but with the Chrome Extension. The events are actually being fired each time. So I think it's not really a problem.
Views
Likes
Replies
Views
Likes
Replies