<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Data Collection and Experience Persistence for Server Side (Java SDK) in Adobe Target Questions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/data-collection-and-experience-persistence-for-server-side-java/m-p/430299#M7145</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="15067214"&gt;&lt;/LI-USER&gt;,&lt;/P&gt;&lt;P&gt;#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 &lt;A href="https://github.com/adobe/target-java-sdk-samples" target="_self"&gt;sample app for the Target Java SDK&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;#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).&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
    <pubDate>Thu, 04 Nov 2021 00:40:56 GMT</pubDate>
    <dc:creator>Ryan_Roberts_</dc:creator>
    <dc:date>2021-11-04T00:40:56Z</dc:date>
    <item>
      <title>Data Collection and Experience Persistence for Server Side (Java SDK)</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/data-collection-and-experience-persistence-for-server-side-java/m-p/430258#M7142</link>
      <description>&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a couple of questions regarding server side (Java SDK).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question number one:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For server side tests (form based), does setting the reporting source to Adobe Analytics send activity data over the same way as client side does (activity / experience name)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question number two:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How is persistent experience achieved with server side?&amp;nbsp; I know for client side the Visitor API (AMC...) cookie is used for experience consistency.&amp;nbsp; Does server side have a similar mechanism?&amp;nbsp; If so does it "autmagically" work out of the box?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 16:32:55 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/data-collection-and-experience-persistence-for-server-side-java/m-p/430258#M7142</guid>
      <dc:creator>rrrrrraul</dc:creator>
      <dc:date>2021-11-03T16:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: Data Collection and Experience Persistence for Server Side (Java SDK)</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/data-collection-and-experience-persistence-for-server-side-java/m-p/430299#M7145</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="15067214"&gt;&lt;/LI-USER&gt;,&lt;/P&gt;&lt;P&gt;#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 &lt;A href="https://github.com/adobe/target-java-sdk-samples" target="_self"&gt;sample app for the Target Java SDK&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;#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).&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 00:40:56 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-target-questions/data-collection-and-experience-persistence-for-server-side-java/m-p/430299#M7145</guid>
      <dc:creator>Ryan_Roberts_</dc:creator>
      <dc:date>2021-11-04T00:40:56Z</dc:date>
    </item>
  </channel>
</rss>

