<?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: Customer ID Sync on Mobile App - When to Sync (D_CID_IC)? in Adobe Audience Manager Questions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-audience-manager-questions/customer-id-sync-on-mobile-app-when-to-sync-d-cid-ic/m-p/264386#M2049</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you noticed, there are two ID syncs happening, Device ID sync with 20915 and Customer ID sync, which a cross-device data source created in your Audience Manager instance. In your scenario #3, if the CRM id is available, the CRM id sync should also fire, which means, you should see two ID sync calls being fired.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please review your implementation - is your CRM id is either only being exposed when the login happens; or do you not have the CRM id sync code implemented on app launch. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Harish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 27 Nov 2018 11:46:42 GMT</pubDate>
    <dc:creator>harishd90</dc:creator>
    <dc:date>2018-11-27T11:46:42Z</dc:date>
    <item>
      <title>Customer ID Sync on Mobile App - When to Sync (D_CID_IC)?</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-audience-manager-questions/customer-id-sync-on-mobile-app-when-to-sync-d-cid-ic/m-p/264384#M2046</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On mobile app, we are trying to sync the customer ID but not sure when that needs to occur. Here is the current scenario:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;#1 Non-Registered User Launches App&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;On app launch, demdex.net call containing parameter d_cid_ic with value DSID_20915=device advertising ID fires.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;#2 Non-Registered User Signs into App&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;On sign-in event, a new demdex.net call containing parameter d_cid_ic with value XYZ_id=uniqueuserid fires.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;#3 Registered User Launches App&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;On app launch, demdex.net call containing parameter d_cid_ic with value DSID_20915=device advertising ID fires.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The question we have is around situation #3. When a registered user launches the app, should there only be one demdex call that syncs the device advertising ID or should we be expecting two demdex call? One that syncs the advertising ID and one that syncs the unique user ID seen in #2?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Sep 2018 22:35:53 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-audience-manager-questions/customer-id-sync-on-mobile-app-when-to-sync-d-cid-ic/m-p/264384#M2046</guid>
      <dc:creator>johncfl</dc:creator>
      <dc:date>2018-09-25T22:35:53Z</dc:date>
    </item>
    <item>
      <title>Re: Customer ID Sync on Mobile App - When to Sync (D_CID_IC)?</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-audience-manager-questions/customer-id-sync-on-mobile-app-when-to-sync-d-cid-ic/m-p/264385#M2048</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://experienceleaguecommunities.adobe.com/people/johncfl"&gt;johncfl&lt;/A&gt;​ please wait and see if you get additional advice from other forum folks but I came across an internal discussion which I believe might help answer your question:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the call should contain something like:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure if that helps but it might trigger some more reaction to your thread &lt;IMG src="https://experienceleaguecommunities.adobe.com/legacyfs/online/emoticons/wink.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2018 15:51:41 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-audience-manager-questions/customer-id-sync-on-mobile-app-when-to-sync-d-cid-ic/m-p/264385#M2048</guid>
      <dc:creator>Christophe_Joss</dc:creator>
      <dc:date>2018-09-26T15:51:41Z</dc:date>
    </item>
    <item>
      <title>Re: Customer ID Sync on Mobile App - When to Sync (D_CID_IC)?</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-audience-manager-questions/customer-id-sync-on-mobile-app-when-to-sync-d-cid-ic/m-p/264386#M2049</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you noticed, there are two ID syncs happening, Device ID sync with 20915 and Customer ID sync, which a cross-device data source created in your Audience Manager instance. In your scenario #3, if the CRM id is available, the CRM id sync should also fire, which means, you should see two ID sync calls being fired.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please review your implementation - is your CRM id is either only being exposed when the login happens; or do you not have the CRM id sync code implemented on app launch. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Harish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Nov 2018 11:46:42 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-audience-manager-questions/customer-id-sync-on-mobile-app-when-to-sync-d-cid-ic/m-p/264386#M2049</guid>
      <dc:creator>harishd90</dc:creator>
      <dc:date>2018-11-27T11:46:42Z</dc:date>
    </item>
  </channel>
</rss>

