It sounds like you are tying to set the s.events variable in two different places
- In your core Analytics code library (AppMeasurement)
- In a direct call rule
Whichever portion of code runs last it likely overwriting the previous variable value. I'm not aware of any work around for this or way of setting precedence.
I'd recommend pulling the s.events variable out of your core library if possible and only setting via rules.