My name is Ryan and I am part of the Audience Manager Customer Care team at Adobe. Jantzen asked if I could hop in and help further answer the questions you have around the Visitor ID service changes he mentioned.
My understanding is that the calls you see will change depending on whether you are using the stand-alone Visitor ID service code (visitor.js), or if you have it implemented via the AppMeasurement code. If you are seeing the IBS call today, you will continue to see it but the DPID and the DPUUID values will be replaced by the CID and CID_IC values.
Regarding the Integration Code (IC), when added to the data source this functions in place of the DPID value in the http calls (when using the new variables). This will need to be added to the data source in question prior to making the change, and when the http calls are made it will directly point to the desired data source. Because of this, when you upload the data files, you can continue to do so using the same format you have been; continuing to utilize the DPID as the data target.
Hopefully this helps provide more context around the questions you are asking, but let me know if you have any other questions!
That should be the case. If you want to see if the Visitor ID service is working properly, I would start by following the steps in our documentation: https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid-test-verify.html. That should give you insight into whether the Visitor ID service code is working as expected. If you still have concerns after that point, feel free to reach out to our support teams; we would be happy to take a look at the site and see what is happening.
If I understand you correctly, with the Visitor Id service implementation, we should still see the IBS call, but instead of DPID and DPUUID we should see CID and CID_IC values. The offline file naming convention would remain the same.
Is there a way to check if the Visitor ID code is implemented correctly on site? Also, If we are not seeing the IBS call anymore, should this be of concern?
Thank you for your response. Does that mean, even with the visitor id implementation, we would still need to see an "id sync" call such as https://dpm.demdex.net/ibs:dpid=1348&dpuuid=0e7b9b8310ced11a35b82d6d41945a4e?
My understanding is that the dpid determines where AAM stores the ingested data from offline files. i.e the dpid 1348 is the Data source id in AAM. The offline file name is ftp_dpm_1348_TIMESTAMP(.sync|.overwrite)[.SPLIT_NUMBER][(.gz|.tar|.tgz|.zip). Therefore, data in the offline file will be stored in the traits associated with data source id 1348.
Apologies for the questions, but i'm trying to understand what impact the visitor id implementation will have on ingesting offline data into AAM.
I was able to speak with one of my AAM co-workers and he indicated the file uploads will use the same format as they did before. The major change in the first document is that we now use the data source integration code in place of the data source id (DPID). We still use the customer id which was previously referred to as "dpuuid".
Hopefully, this info helps. If not, let me know what other questions you have and I'll try and get some more information.