Hello @Chiranjeet , Please find the inline inputs below:DP ID - I think this will be your Partner ID in AAM. If you do not have this information then please let me know and I will DM It to you.Data source ID - This is AAM datasource ID, you need to create a new datasource via AAM UI and share its ID...

Hello @snehaparmar , If the purpose of login step is just to perform ID sync then no need to add AAM DIL library.However, if you are planning to send data along with this ID sync to AAM then you would need DIL code on the login page as well. I hope this helps, please let me know if you have any addi...

Hello @JL143 , A few points:To analyze this raw data in order to optimize the digital marketing efforts.It contains the Marketing Cloud ID (MCID) which can be used to analyze the behavior of anonymous site visitors, plus it includes the timestamps.Use this information to understand the marketing tou...

If you are targeting authenticated users then yes the count will become 2 on the second visit from incognito window. Just ensure that Profile Merge rule validates using authenticated profile option with Profile Link Device Graph.

Hello @michaela7702973 , Analytics can share data with AAM in real-time via SSF only and that too with limited variables only. [Complete List] Above mentioned variables won't populate in AAM due to the product design. You need to pass these variables as one of evar/prop/listvar to have them populate...

Hello @Roxie423 , If you have Analytics and forwarding data to AAM via Server-Side Forwarding then you can ignore the first concern mentioned below:"Delay between when a visitor qualifies for the experience and when they are included in the AAM segment to be used for XT"However, above will need a sl...

Hello There, You need to create the onboarded traits prior to sending data files into AAM otherwise all of the new signals will be lost. As you correctly said, to perform backfilling of those new signals there will be an additional cost.

Hello There,

Hello @sheetalkamble , Could you please elaborate a bit more on the use-case? It helps me in providing a better answer/approach to your question.

Hello @MA1985CG, The mentioned use case is achievable if you are targeting authenticated profiles i.e. customerIDs. Device based qualification + recency/frequency won't work. Also, please note that recency/frequency works only on rule-based traits which means  you need onboarded + rule-based traits ...