Expand my Community achievements bar.

Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!
SOLVED

How will the calls affect by the checkbox , Document will unload ?

Avatar

Level 4

Hello, 
I have a question, 
How will the data collection/calls affect the checkbox, "document will unload". 

gmadala_0-1729191186949.png

What I have observed is if I uncheck this, it will give the request type is "interact" or if I check the box the request type is "collect" ?
Please let me know if this could affect the calls, performance etc. 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Added some more context to my initial reply. 

No:

  • don't tick it on page views since the user will likely stay long enough to make the request go through 
  • tick it in cases where you experience aborted tracking calls
  • as mentioned, none of your extensions, even the Experience Platform Debugger will be able to show you the request payload which is quite annoying 
  • personal opinion: with nowadays browsers caring more and more about performance and user experience, I wouldn't be surprised if the beacon API will soon also be ignored
Cheers from Switzerland!


View solution in original post

4 Replies

Avatar

Community Advisor

Hi @gmadala 

ticking the checkbox will turn the request into a beacon/ping that is choosing a different request type. You regular requests are GET or POST requests, whereas a beacon is designed/intended to be sent in the browser background which will likely improve tracking accuracy.

This can be crucial if you put a click tracking on e.g., a button or link that causes a browser navigation and might be canceled from the browser for performance reasons. This is a classic issue with click tracking.


Downside of this request type is that the payload is not as easy to analyze by for instance automated tests and/or browser extensions.

 

What's also not ideal is that the UI only shows a checkbox and does not let you evaluate whether it should be sent as beacon on the fly, for a generic click tracking that only uses the beacon when needed.

in AppMeasurement, this could be set onthe fly on request base with a.useBeacon = true and automatically get reset after the request.

 

https://developer.mozilla.org/en-US/docs/Web/API/Beacon_API

 

Cheers from Switzerland!


Avatar

Level 4

So you would recommend, unchecking the box for link calls and keep it checked for regular pageview calls ? 
I would like to know whats the standard across.

Avatar

Correct answer by
Community Advisor

Added some more context to my initial reply. 

No:

  • don't tick it on page views since the user will likely stay long enough to make the request go through 
  • tick it in cases where you experience aborted tracking calls
  • as mentioned, none of your extensions, even the Experience Platform Debugger will be able to show you the request payload which is quite annoying 
  • personal opinion: with nowadays browsers caring more and more about performance and user experience, I wouldn't be surprised if the beacon API will soon also be ignored
Cheers from Switzerland!


Avatar

Administrator

Hi @gmadala  Did you find the suggestions helpful? Let us know if you need any further information! If the solution works for you, please mark the answer as correct to help others. And if you’ve found your own solution, we’d love for you to share it with the community. Thank you!