Hi there, You can choose to keep both or either of them. Since both libraries work differently there's no conflict and generally there's no impact on site performance either.

Hi there, The s_fid cookie is set on the basis of the Tracking Server information. Now, if you have any of the below cookies set then the identification is not done by s_fid cookie and can be ignored:s_viAMCVs_ecid Basically, this s_fid is set in every server call regardless of what user identification cookie is set on the site.

Hi There, Instead of using Data Insertion API, you would rather want to use Data Source API which would correspond to the same functionality using FTP.Please ref: https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/data-sources-api/index.md. The Data Insertion API actually is meant to upload data as a server call just like that on the site and would not help your case here.

Hi There, Instead of using Data Insertion API, you would rather want to use Data Source API which would correspond to the same functionality using FTP.Please ref: https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/data-sources-api/index.md. The Data Insertion API actually is meant to upload data as a server call just like that on the site and would not help your case here.

To add to what @kainth mentioned, if your site does not block third party cookies then the ID Sync call would run through our demdex servers and return the same MCVID on Domain 2. The method suggested would work if there's a journey from Domain 1 to Domain 2.

Hi There, You would have two options to export real time data through API: 1) Real Time API: https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/reporting-api/real_time.md2) Livestream API: https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/live-stream-api/getting_started.md Livestream API gives you all the data set as you'd see in a Server Call on your site but it requires special contract. Real Time API is free to use but is limited in functionality as it only allows...

Hi, this is being worked upon by our Engineering to add S3 as a destination option to for DWH Exports. In the meantime, the only option is go through Client Care and have them engage the Engineering to have the exports moved to S3.