Has anyone successfully done file based offline ID sync (not for PBD) recently?
If yes, could you share the exact steps and settings for both the data sources?
We have an ID (say hashed email) that's available on website front end for ID sync (data source 1). But, the offline data file will be uploaded using a different customer ID (data source 2). We'd like to send an offline ID sync file or match table later on to AAM to tell that both IDs belong to the same person.
We uploaded file like this: adobe_id_datasource1_datasource2_<timestamp>.sync
So far, we have configured both the data sources as cross device and uploaded the file to the s3.
But, while looking up the trait and segment qualifications using the d_cts=2 flag, we do not see that the hashed email ID (data source 1) qualifies for the traits and segments.
Hello @Varun_Kalra ,
Hope you are keeping well! 🙂
Offline ID sync enables us to sync the cross-device Ids and make the offline IDs to be available for targeting. It doesn't map data of the existing cross-device Ids to the new cross-device IDs. At the end of ID sync file processing, we get only devices linked to new cross-device Ids.
This is because the Trait/Segment qualification is done on Data source 2 not on Data source 1, by offline ID sync we can only create a link between two customer Ids but the actual Trait/Segment qualification stays on the one for which customer has been qualified. Therefore if you use d_cts=2 flag you will find no data against customer Id of data source 1 but will get data against customer id of data source 2.