While Testing the implementation rule order to stack different values before sending the beacon props and eVars seem to work as expected, but the event's string, although it appears stacked on the debugger, doesn't send all the events when the server call is triggered.
Below is the first rule, order 10, which sets a bunch of props and eVar and also event45
Below is the second rule, order 25, which sets some other of props, eVars and also event4,event24 which appear stacked with the previous event45
Below is the beacon that was sent, order 50, with only event4,event24
I'm not sure if that's a bug or there's a reason all the events are not being stacked.
linkTrackEvents only specifies which events should be tracked in an image request. The events variable specifies which events trigger. For example:
s.events = "event1,event2,event3";
s.linkTrackEvents = "event3,event4,event5";
If you sent a link tracking call with these two variables, you would only see event3 since it was the only one included in both s.events and s.linkTrackEvents. This is also the case with your screenshot.
While I would agree that if you have two AA Set Variables Actions in sequence if you set prop1 to "Apples" and then set prop1 to "Oranges" when you send the beacon, you would expect prop1 to be "Oranges" since prop1 can only have one value.
The same, however, is not expected for s.events since it can have multiple values. I feel that s.events should be more of an accumulator and that you should expect to be able to set different events within it in sequenced actions across multiple rules.
I guess the first step is to agree on how it should work. The next step is to make sure that it works that way.