I would like to understand on what way this .sync or .overwrite file works while doing the below case
Here I have a small scenario for your understand.
Step 1 - We have created the XYZ onboarded trait name with expire set to "0" conditions along with rules update (i.e.) "usera==1".
Step 2 - Instantly we upload the offline .sync file to that location, after 48 hours user "A" has realized under that XYZ onboarded trait.
Step 3 - Since, the user "A" is no more in our system after several days. we would like to remove that user "A" from the existing XYZ onboarded trait and the conditions from the file are set to be "usera==0"
My Query is?
On what way we can remove that user "A" who already realized on the existing XYZ onboarded trait long back and please note that conditions still on 0 expire.
Is it possible, If we use .sync file to upload with the "usera==0" or If we use .overwrite file to upload with the "usera==0"
.overwrite file: It overwrites all of your existing visitor profiles and replaces them with the data in your file. You can use a .overwrite file to reset visitor traits or remove stale, obsolete traits.
.sync file: It appends new data to your existing visitor profiles. Sending in a .sync file does not erase or overwrite existing profiles
1234 "gender"="m","age"="30","campaign"="upgrade eligible" User will be qualified for all the three traits
User will be removed from trait "campaign"="upgrade eligible" but he will still be qualified for other two traits
1234 "campaign"="upgrade eligible"
User will be only qualified for above trait and will be removed from"gender"="m","age"="30"
1234 "campaign"="upgrade eligible",state="Kerala"
User 1234 will be qualified for both the traits.
Let me know if any other additional information is required on .sync and .overwrite file.
Awesome its really help us and appreciated your response as well.
One last question may be silly? Suppose If I have not loaded the file using .sync method shally I use directly the .overwrite file mean what happens and what will be the draw back.
Example, suppose if we have send 1st file with 100 id later again i need to modify or remove some user from the same first file feels like rework kind off, is that works if i can directly use the overwrite method for both newly added user and remove the users instantly.
Sorry if my understand is correct as per your comment!
I would like to add that user "A" into different onboarded traits (i.e.) ABC Trait ID on the same .sync file upload actions it means I want to remove from XYZ Trait ID and added to ABC Trait ID (rule for this abc trait id is "usera==0") on a single upload.
Please suggest me, do I need to add that user "A" into separate column something likes this on the same .sync file.
454545 <TAB> d_unsid=2222222
454545 <TAB> usera==0
I need to add the syntax mentioned in the previous examples and upload
454545 <TAB> d_unsid=2222222, usera==0
I need to add two .sync file for the same user "A". First is for remove that user "A" from the Trait ID then upload. Again the second steps is to add the user "A" along with this syntax "usera==0" to upload with different .sync file.
If you would like to remove a single onboarded trait from User A, I would recommend one of the following:
.Overwrite: Provide a .overwrite file with a row for User A. This row MUST contain all the signals / key-values of trait expressions that you would like the user to keep. Otherwise user A will lose more than just a single trait. Essentially whatever is uploaded is what their profile will now contain trait-wise.
.Sync: If you know the trait ID that you would like removed, you can simply pass in the prefix "d_unsid" with the .sync file. Using d_unsid=<trait ID> will remove the onboarded trait from this users profile.