@Jennifer_Dungan  @Andrey_Osadchuk @Ishan_Sinha_ @akt0m3r @HemanginiS @amgup  Do anyone of you have answer to this? I am using web SDK from 1 year and haven't faced this issue before.

Looks like it's common issue and no resolution.@yuhuisg  @Jennifer_Dungan  @Andrey_Osadchuk @Ishan_Sinha_ @akt0m3r @HemanginiS @amgup @RudraChaudhari 

It's not the same thing, Anyway I have figured it out. we can look for sendEvent. [alloy] Executing sendEvent command. Options: {xdm: {…}, type: 'formview|Campaign|Subscription'}

with web SDK it's hard to find out which rule is firing, as setDebug() is does not work, adobe debugger give some data in console but it's not clear as setDebug(). Is there way to know which rules are firing for web SDK debugging? @Jennifer_Dungan  @Andrey_Osadchuk @Ishan_Sinha_ @akt0m3r @HemanginiS...

its not giving exact rule name and that's what I am looking for, just like it works in App measurement.

Is it possible to see same in web SDK? some how _satellite.setDebug(true) is not working.and gives below  

yep, and just FYI this behavior is only for product string, rest events and their eVars are working as it was with app measurement.

Thanks a lot for explanation, this is probably the reason, in reports it's showing proper eVars and events.

eVars and events in product variable are proceeded by 1&2 respectively.we are passing eVar17,19.but in product string in debugger it's capturing as eVar117,119. similarly for events, we are passing as event52but in product string in debugger it's capturing as event252  @Jennifer_Dungan @yuhuisg @And...