Hi @canada  fully agree with @Jennifer_Dungan . On top of that, it's also not hard to persist the previous page name, URL, whatever you need and put it in the payload of the next page's page view tracking call. This way, you can always break down your data by the actual previous page's value.

HI @_Paul_S  that is the point about the WebSDK. There is no "s" instance anymore (should be) since the Web SDK is replacing Adobe Analytics, Target, Visitor Service and Audience Manager. Should you still have the legacy libraries in place, they should for sure be phased out.   I think the condition...

Hi @_Paul_S  I think you may just be using the classic AppMeasurement for Adobe Analytics if you are still referring to s.tl() . Web SDK would look a little different.   What would probably make most sense in your case is a condition with a piece of custom code in your rule that checks whether the g...

Agree with @MandyGeorge  what I typically do is merge the UTM params together into the Analytics campaign value, so you can use them as Tracking Code dimension. Key there is to use a unique separator that is not used in any of the UTM param values, such as ":_:" or similar.   Also, when filling the ...

Good one! To be honest, I would assume/hope for build errors, but haven't tried it myself. Maybe give it a try and be our guinea pig?

Hi @srikanthpogula,   upfront: when you are implementing new AEM components, you may want to look into tracking with AEM core components tracking which - partially - provide an out of the box tracking for when core components are shown and interacted with. "Partially" is the key. In my experience, t...

Yes, you are not impacting the source property

Duplicating a property has no effect on the initial published libraries. You will have to do a deployment of all items on the new one (click add all changed resources) and push them to prod (or at least do an initial build with them.

Good one, I'd say give it a try! I wouldn't be surprised if secrets don't get copied. Haven't tried it either 

Ah, I see. So, as explained earlier, the eventInfo is not part of the computed state. This is an issue I previously raised with the developer of the extension that there is no real way to use the extension to access eventInfo data.   instead, use a custom code block and do a (note the ?. construct w...