Hi @AbhilashSh , Good to hear that it worked. I was under the impression that you will have already checked these settings as accepted solution already clarify this.For a beacon to be considered a page view in AA you need either:webPageDetails.name, OrwebPageDetails.URLFor a beacon to be considered ...

Hi @AbhilashSh , It does not seems like Adobe target issue, as Adobe Target captures/increases pageview during proposition fetch event and not on link Click. Check on webSDK extension if pageName value being passed as global value for all beacons.

Hi @AbhilashSh , From the screenshots that you have shared, it seems like beacon call is getting pageName from somewhere in your implementation. For a Adobe Analytics beacon to be identified as pageview, it needs either pageURL or pagename. Re-check your implementation code and you should identify h...

All above solutions did not work for me too. Then we inspected settings in  Adobe Experience Platform Web SDK extension.Check if you have enabled click data collection.if Yes, when sending event data, dont automatically include default context information and rather, select "Specific context informa...

All above solutions did not work for me too. Then we inspected settings in  Adobe Experience Platform Web SDK extension.Check if you have enabled click data collection.if Yes, when sending event data, dont automatically include default context information and rather, select "Specific context informa...

We are trying to use same page/next page personalization in Adobe Target using AEP data. Our site is already tracked using websdk. Created an experience in Adobe Target and here is the scenario: If user clicks on Tab A, show him/her experience AIf user clicks on Tab B, show him/her experience B Othe...