We have migrated our properties from DTM to Launch using "Upgrade to Launch" feature in DTM. All our properties are loading fine in the pages from Launch. One odd thing we noticed in the rules, every time Event based rule fires when the event is triggered, the corresponding Page load rule Props also being set along with corresponding Event based rule props. Also in the AEC Debugger I noticed all the previous events are combined together. Event based rule clearly selected with s.tl(), not s.t() in the config. Anyone else see this issue in the launch? In DTM, we see the event rule run separately and the page loads props are not set for the events. But its happening in Launch.
in the below Pic, Prop 11 supposed to be added only to Page load, it loads for Event also in launch.
Events property also prepending previous events like event12, event34. In DTM we used to see only event34 just for event. Any tips are appreciated to fix this.
In the event rule, have you tried adding the "Clear Variables" action (using the Adobe Analytics extension) before populating the desired props/eVars/events and sending the call? This would give you 3 actions in the rule: Clear Variables + Set Variables + Send Beacon
Have you checked the configuration in the "global variables" section of the Adobe Analytics extension?
Also in the extension, do you have any logic in the custom code section that might be inadvertently adding properties to the s.linkTrackVars/s.linkTrackEvents properties?
What about the config of the EBR, can you confirm that it doesn't have the offending variables defined either in the GUI or in custom code?
If you run _satellite.setDebug(true) in the console, you should get some additional details about what's going on during the load process. Maybe you can find something in there.
As per my understanding, it seems that the event value is persisting from s.tl () i.e. link call to s.t() i.e. page load call. So, I will suggest you to review the launch rule that is setting that event. Check whether you are using Clear Variable after sending the beacon. This will help in preventing the data to persist from the previous server call to the next call. Also, you can check the load order by going to the browser console & using _satellite.setDebug(true). After enabling the debug logs, you will need to reload the page & filter the results in the browser console using the keyword "fired". That will show you what all rules are getting fired & in which order.