Hi @harshapr ,If you want the second event to count as a separate page in Adobe Analytics reports, it needs to be tracked as a full page view. In SPAs, you typically need to manually trigger a page view call for each distinct view you want to appear in the reports.Thanks,Ankit

Hi @SantoshRa5 ,As far as I know, you cannot fetch segmentName directly through attribute mapping. To achieve this, you need to enrich the data (Example: using Query Service) by joining segmentMembership IDs with the segment definition metadata, and then export the enriched dataset.Thanks,Ankit

Hi @SantoshRa5 ,You can export ids and map to names outside AEP or via Query Service you can ingest segment definition metadata into a dataset and export it to SFTP.Thanks,Ankit 

Hi @jayasekar ,Yes, you can see Segment 1 + Destination 4 count, but not directly in the Segment UI.You’ll need to either check the destination activation reporting or run a query to get that breakdown.Thanks,Ankit

I already have a site running on AEM Cloud that was created a couple of years ago using the standard author and publisher flow. The site has multiple pages that are working fine.Now I want to integrate and utilize Edge Delivery Services (EDS) with this existing site and its pages.I have already gone...

Hi @harshapr ,This is expected behavior most of the time.Both values can reach Adobe, you can see the second tag in the browser network request, so the tracker did receive it.But Adobe’s Pages report only counts page view hits. If the second hit was sent as a link/event (or you only changed pageName...

Hi @GabrielaNa1 ,I'd leave 30-60 minutes after a daily audience refresh for journeys to pick up the new data and if the audience is composed/complex, allow up to 24 hours.Reference: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/audiences-profiles-identities/audiences/target-audi...

Hi @NickMannion ,Yes - but only if the field in table B is set up as an identity (profile-enabled). If it’s just a regular attribute, you can’t create a UI relationship from A to B.Reference:https://experienceleague.adobe.com/en/docs/experience-platform/xdm/tutorials/relationship-uiThanks,Ankit

Hi @bjoern__koth ,Reference:https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/methods/edge-segmentationhttps://experienceleague.adobe.com/en/docs/experience-platform/profile/merge-policies/ui-guidehttps://experienceleague.adobe.com/en/docs/experience-platform/segmentation/m...

Hi @AnandhiMa2 ,AEP ingestion does not accept null values for profile attributes via upsert. The practical workaround is to overwrite with "" (empty string) for strings, or use sentinel values and filter downstream. If you must truly remove a field, it requires explicit Profile API calls, not upsert...