[Server-side Adobe Analytics to Audience Manager] | Community
Skip to main content
S
SCB21
Level 5
May 9, 2023
Solved

[Server-side Adobe Analytics to Audience Manager]

  • May 9, 2023
  • 5 replies
  • 2327 views

Hi,

If we are doing server-side integration from Adobe Analytics to AAM, how would the ID sync process work?  Also, would adding an integration code affect the ID sync process overall?

 

Any insight would help. 

 

Thanks

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by dhwoolsey

    AAM DataSource Integration codes are solely used for the purpose of ID syncs. Unless you have other sections of the site or other properties (like mobile apps or other websites) using that test123 integration code, there's no harm in changing the integration code for that data source in the AAM UI. 

     

    In terms of why is it still working, it sounds like you're either in the process of migrating or just migrated. However you did the ID sync before (in a pure DIL implementation, you may have been using the data source ID or DPID), must have been going long enough that you have quite a few ID lookups stored in that data source. Those are probably still pretty fresh, so your onboarding is going to continue to work just fine for now. Give it 6-12 months and you'd probably find that your number of "Records with no matching AAM ID" in your onboarding report would increase. in other words, your existing lookup table that you've built up over time is still there, but you're probably not adding any new ID syncs to it. The trait to look at would be your synced audiences trait for the data source in question. I'm going to guess that your daily unique visitor count is trending downward because you're probably not seeing any new ID syncs. You're probably also seeing an error code in the AAM response to your Analytics or ID service calls stating that it doesn't recognize the ID or data source. 

     

    It is hard to really get into details on a community post like this. If you need more help, I'd recommend you open an AAM case and someone from our AAM support team can help answer more questions. If you happen to be an ultimate support customer, then we can probably even help you get in touch with the field services team where they can do a little desk-side coaching with you. 

    5 replies

    D
    Adobe Employee
    dhwoolseyAdobe Employee
    Adobe Employee
    May 9, 2023

    When you use the setCustomerID function as part of ID service, it'll stick the synced ID in the Analytics call so that it gets passed to AAM. You'll see it in the cid. namespace parameter of the Analytics call. And when you use setCustomerID, you use the integration code and it works just like it did before.

    S
    SCB21Author
    Level 5
    May 9, 2023

    Hi,

    In the d_cid_ic we have a value called tempID and on the adobe audience manager data source integration code, we have test123, would that impact ID sync overall? So basically, when I look at the id sync call, it shows up as 'id?visid... d_cid_id=tempID%12345689', however, on the integration code in AAM, it is set as test123. Any info will help.  We are seeing offline to online authentication data, but still a bit lost on this.  

     

    Thanks

      D
      Adobe Employee
      dhwoolseyAdobe Employee
      Adobe Employee
      May 9, 2023

      Yes. The value you see in d_cid_ic needs to match what you see as the AAM integration code in question. So you can change the integration code in the AAM UI to match the code on the page or you can change the code on the page (the setCusomerID function call) to match what you see in the AAM UI for the datasource in question. 

        S
        SCB21Author
        Level 5
        May 9, 2023

        If we change that on the AAM UI, would that break anything in general?  Also, if the integration code is not matching the ID sync code, how are we still seeing data when we onboard CRM into the data source and when we segment using PMR Last Authenticated?  Should it not having any data at all?

          D
          Adobe Employee
          dhwoolseyAdobe EmployeeAccepted solution
          Adobe Employee
          May 9, 2023

          AAM DataSource Integration codes are solely used for the purpose of ID syncs. Unless you have other sections of the site or other properties (like mobile apps or other websites) using that test123 integration code, there's no harm in changing the integration code for that data source in the AAM UI. 

           

          In terms of why is it still working, it sounds like you're either in the process of migrating or just migrated. However you did the ID sync before (in a pure DIL implementation, you may have been using the data source ID or DPID), must have been going long enough that you have quite a few ID lookups stored in that data source. Those are probably still pretty fresh, so your onboarding is going to continue to work just fine for now. Give it 6-12 months and you'd probably find that your number of "Records with no matching AAM ID" in your onboarding report would increase. in other words, your existing lookup table that you've built up over time is still there, but you're probably not adding any new ID syncs to it. The trait to look at would be your synced audiences trait for the data source in question. I'm going to guess that your daily unique visitor count is trending downward because you're probably not seeing any new ID syncs. You're probably also seeing an error code in the AAM response to your Analytics or ID service calls stating that it doesn't recognize the ID or data source. 

           

          It is hard to really get into details on a community post like this. If you need more help, I'd recommend you open an AAM case and someone from our AAM support team can help answer more questions. If you happen to be an ultimate support customer, then we can probably even help you get in touch with the field services team where they can do a little desk-side coaching with you. 

            Terms & ConditionsAccessibility statement

            Loading footer...