adding to above , be sure to Go to Adobe Experience Platform and check the Dataset Activity to confirm that the data was successfully ingested. Before you look for new profile data ... 

- check for integration / ingestion point  , identity/segment service configuration  or sources that are actively sharing data with AEP - remove/disable them- removal will stop future ingestion but not remove the existing/historical audience - remove segment/audience imported in AEP from Audience Ma...

Looking to use AEM/React combination where react would be an embed component/web component for AEM and will use Apollo graph QL client for API - Any suggestion here 

that is what i mentioned it will capture next page, even if visit/hit happed after sometime or a new tab to any page by any other mean on the same browser - may be i am saying the same thing.@juliusonyancha  can you read our messages and suggest if we are making sense and addressing what you looking...

yes, session persist  that leads to next page in report, you can wait or clear session to validate the issue 

yes, session persist  that leads to next page in report, you can wait or clear session to validate the issue 

the answer is yes, please https://experienceleague.adobe.com/en/docs/target/using/activities/experience-targeting/create-targeting/xt-add-experience 

use case is different for both thus might lead to data mismatch - Eloqua - is marketing/email automation - user interaction is via forms and email.- AA - Web channel and capture user interactionBoth platforms differ in tracking implementation, timing for data refresh, user visit/interaction, metrics...

think of using a custom dimension, such as an eVar, to capture the first-party ID [userid /customer id in case not using server side FPID] and then apply that dimension to your event reporting.- consider eVar as the identified not ECID - eVar would be a dimension on reporting for the unique count 

considering the prior example, understanding is hit would expire right after 1 page view