Here's a snapshot which explains the latency by source type.  You can read more here for AJO     

@Olivier_Blonste You cannot delete/change once it's created/has data associated with it already, if you want to assign a new namespace for the same data  You will need to remove the profiles from profile store which are affectedDelete these data/purge the dataset create new namespace and update the ...

@SCB21  Assuming you are taking about IP from Analytics to AEP, It should not pose any issues in the set up of AEP.  If you have any use case for segmentation/reporting ( highly unlikely) use case based on IP address, these may be impacted.  The only place i could see it impacting is if you use IP a...

Hey @SCB21  Assuming you referring to OOTB analytics source connector, the "ipv6 will be mapped to environment.ipV6" field in the schema.    Here's the full list of analytics mapping   Hope that helps  Anil

@deepika988 Could you expand more on the usecase, i.e what are you trying to achieve using the query service?    Assuming you are trying to download the data, this may not be the optimal way.  The "result" of the Query created via this API ends up as a new dataset, you will then be able to use it fo...

@Shruthi_Vanguard Could you expand on the "for the events"? may be with an example use case to help you with the same. 

Thank you @Tof_Jossic 

@Vin_Adobe Yes that should be doable, to begin with  use the Adobe AEP connector in commerce To enhance your AJO, add any custom events/data to schema Finally listen to these events in AJO to configure action Hope that helps  Anil

@FelixAgung1 did you map the xdm variables to Adobe analytics in processing rules? did you test this in staging env before moving to production and did that work ok?