Looking at the (RUM) beacon packet, I see that it includes a
$A part containing the action type, and third party urls
$url part I hope this is used to link the action to a web requests?
They both include time-stamps some sequence number and a little secret sauce (-;
Does anybody have more specifics on the contents of the packet? And what happens if you send this packet again, because than there is no matching web request it gets discarded?
Solved! Go to Solution.
The correlation of user actions to server side pure paths happens after the beacon is has arrived at the dynatrace server and the correlation is done by looking at timestamps, url's and our cookies which must also be available at purepath level.
But as not every user action can be correlated to a purepath the "linkaged" of user action to purepath is not a criteria to discard the beacon. So if you send a beacon twice it might still be recognized as valid beacon. Of course there are some checks, like don't accept beacon which are outdated etc. but it's not so trivial.