yes, this completely makes sense. And no change is observed, even by applying a separate rule which says if “Page Name” is set then over write the “Page Name” with the contextdata(pagename) , which is expected.Thanks for the response @Sumit-Kumar , it helps.

Thanks @SamuelPaulPeter  and @Sumit-Kumar for the inputs above. However, I was simply trying just to research on it more if mapping the by- default page name variable irrespective of trackAction or trackState call, that means creating a separate processing rule altogether mapping a page name like be...

Hi Team, We had a use case where pageView(custom event) and pageViews(by default metrics) numbers were not matching, because one of the probable reasons was, for few of the link click calls are going as trackState calls in apps therefore changed them to trackAction calls. Now, wanted to set the mapp...

Hi @Jennifer_Dungan ,Since I have also come across the same set of requirement if we can pass on the tracking code along with lifecycle metrices so that we don't loose the attribution. Is this only possible from the app developers?Do we have any such approach from Launch side where we can set the us...

Field Description: What product are you using? What area of the product are you using? What are you trying to achieve? What’s the problem or error? What have you tried so far? Environment / VersionScreenshots / Videos / Logs / CodeAdobe AnalyticsAEP AssuranceTo view listVars in AEP Assurance Debugge...

Hi @Jennifer_Dungan, Regarding the above scenario, as I have used it as : 1. Check if the User is LoggedIn(eventkey = userUpdate)2. Max Frequency "Return true no more than once every 1 sessions". So now while looking at the reports, it seems "Max frequency for a session" is creating multiple events....

Thank you @Jennifer_Dungan for your response. It really helped a lot to get along with multiple complex scenarios like above.

Thank you @Jennifer_Dungan for explaining it clearly. I am trying the above solution of : Using Max Frequency, if you create a trigger for "userUpdate", you can add two conditions to the rule:1. Check if the User is Logged In2. Max Frequency "Return true no more than once every 1 sessions". It seems...

Thank you @bjoern__koth for the reply. Yes, it seems quite undoable to exactly understand when this session would end, and we can not do it manually either. And another question is related to the above scenario, what would be the impact of expiring data elements on a session?Provided, these data ele...

Hi Team, There is a requirement regarding Launch implementation, It is to fire an 'eventx' after every session is complete for a visitor. The above eventx should only fire when :a) event : userUpdateand b) user is logged inAnd we need to fire this event consistently after every session provided the ...