Boomerang sends beacons on page load to HTTP(s) endpoints with the pattern of
To validate whether everything is working correctly:
Validate whether the standard mPulse Loader Snippet is on the page.
If the loader snippet is not there, you will need to add it.
boomerang.jsis loading via the browser developer tools.
In the Networking tab, you should see a request to [c|s].go-mpulse.net/boomerang/[API-KEY].
In the Source tab, you should see the minified
If you do not see boomerang.js in the Networking tab, check that the loader snippet is on the page.
config.js[on]is loading via the browser developer tools.
config.js[on]contains app configuration and security tokens that are required for sending beacons.
In the Networking tab, you should see a request to
If you do not see
config.js[on]in the Networking tab, check that
Validate whether beacons are being sent via the browser developer tools.
In the Networking tab, you should see beacons being sent to a URL matching
If you do not see beacons being sent, please review the following troubleshooting steps:
- Validate whether the Boomerang
After the loader snippet executes, it will create an
<HEAD>of the HTML document. This
<IFRAME>is used to load
<IFRAME>must remain in the page for Boomerang to work. It will have a
width: 0px; height: 0px; border: 0px; display: none.
<IFRAME>, it will have a
Here is an example of a correct
<IFRAME> is later removed, it will stop working, and it will not send beacons.
Here is an example of what a removed
<IFRAME> tag might look like. Note that the
<body> was removed, even though the
<IFRAME> is still there.
If this has happened, there may be code on the website that is removing the
<IFRAME> or modifying its contents.
Updated over 1 year ago