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:
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, 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.