We have a scenario where a custom event would be triggered. Now I want to fire a tag when the custom event is triggered. What I did is:
Note: if the use page top event then everything works fine but not with custom event. Please let me know If I am doing something wrong.
susheel
susheel
09-01-2019
For now I have done as below. I will keep on adding all events as I find.
$(window).on('event1 event2 event3',function(e) {
document.body.dispatchEvent(new CustomEvent(e.type));
});
StewSchilling
MVP
StewSchilling
MVP
08-01-2019
You could probably create a bit of code that would act as a relay.
I would listen for specific custom events on `window` then re-package and dispatch them on an element of your choice.
StewSchilling
MVP
StewSchilling
MVP
08-01-2019
There are a few things that I'd try.
1) I tend to use vanilla JS. Try one of these (from the JS console) to see if it solves the issue.
Try this if you want to pass a detail payload with the event.
window
.
dispatchEvent
(
new
CustomEvent
(
"email_submit"
,
{
detail:
{
foo:
"1", bar
:
"2"
}
}
)
)
;
Or this if you just want the event triggered.
window.
dispatchEvent
(
new
CustomEvent
(
"email_submit"
)
)
;
Note that if you need to support IE 11, there is a polyfill required for `CustomEvent`. You'll find it here: https://gomakethings.com/custom-events-with-vanilla-javascript/
2) In DTM, you could not catch a custom event on `window`. I'm not sure if that's still the case with Launch.
Try dispatching on `body` or any element of your choice.
body.
dispatchEvent
(
new
CustomEvent
(
"email_submit"
,
{
detail:
{
foo:
"1", bar
:
"2"
}
}
)
)
;
You'll need to update your rule in Launch to trigger on `specific element` and `body` as shown below.
Aaronius9er9er9
Employee
Aaronius9er9er9
Employee
10-01-2019
> window doesn't work
It's not you, it's us. As @stewarts16448458 noted, we need to fix/improve it on our side and I've logged it internally as an issue.
That said, even when the Custom Event event type begins to support detecting custom events dispatched off the window object, it still probably won't detect events triggered using jQuery (e.g., $(window).trigger('email_submit')). This is because jQuery has its own eventing system that's separate from the native eventing system. Launch only detects events created using the native APIs and doesn't cater to any particular library like jQuery.
StewSchilling
MVP
StewSchilling
MVP
09-01-2019
BTW, I spoke with Aaron at Adobe regarding this. He confirmed that it does not presently work on window (document is the top level object at present). He confirmed that listening on window would be desirable and that he would make the case for a fix. At some point in the near future, you should be able to remove that patch and start listening on window.
susheel
susheel
10-01-2019
Thank you so much for your help and registering the case with window object
StewSchilling
MVP
StewSchilling
MVP
08-01-2019
Maybe try `specific elements` and `window`? I haven't gotten around to
trying this in Launch. I'm curious to see if it works for you.
susheel
susheel
11-01-2019
All our custom events are written in jQuery. Migration is getting tough for us.
susheel
susheel
09-01-2019
Yeah I can do that but i am not sure how many custom events we have.
susheel
susheel
08-01-2019
window doesn't work
We are migrating from SIGNAL to LAUNCH. custom window events work fine there but it is not working here.
susheel
susheel
08-01-2019
There is a lot of code written with window trigger in analytics. It would be tough to modify all.
It works fine with body custom events.
Also jquery way of triggering custom event is not working