- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi @rrrrrraul,
#1: It does rely on the same A4T configuration option the typical client-side deployment of Target does (using an SDID parameter). This does assume a Target server-side deployment and a client-side deployment of ECID and Analytics. Then you should be setting a server-state for the ECID (VisitorAPI.js) on the page. You should be able to see this on the Target-Analytics page from the sample app for the Target Java SDK.
#2: The Target Java SDK handles this so that experiences are maintained as you'd expect. The SDK will use and set the AMCV_... and mbox cookies to make sure ensure this works on both the server-side or client-side (in case you have a hybrid deployment of Target).
Hope that helps.