hi keerthivasanj96056092​, as I understand it the dips in the Segment Total Population account for unsegmented users.

Hi snehaa30982388​ I believe you can also manually upload ID Sync files (ie: file-based ID synchronization)Note the onboarded data files need to be uploaded again after making ID syncs. We are not backfilling, hence the need to have the ID syncs and then upload these files again.Please see Name and ...

jamest66​ .. it looks for eligible users based on shared characteristics from the 'selected' population..  your  selected segment or trait becomes the baseline that the system algorithms use for modeling.See if Understanding Algorithmic Models helpsThat being said you can exclude certain traits to i...

deepay216044​ here is my take on your scenario:If T1 was realised on Day 1 at 12noon, then I would expect the realisation to be valid for 15 days after that so up until Day 16 at 12noon.In this case your user would be qualified for S1, having not been in T1 population since Day 1.On Day 17, T1 drops...

glennb29356951 ​ .. here is what I get when testing from the UI using the same expression: 'traitRule size must be between 0 and 4095' .. characters I assume.

keerthivasanj96056092​ .. glad I could help The UI will show the population with a bit of a delay but you should be able to see that in the next couple of days.

and you have the same issue in file ftp_dpm_166681_1540220058.sync for all 141 entries

keerthivasanj96056092​ .. I downloaded your file to check (ftp_dpm_166681_1540194656.sync).The one formatting error I can see in there is the missing opening quotes on the PointsEarned key value - see below:Try and correct this and re-upload your file with a new timestamp and let us know how it goes...

jobinj30858442​ .. adding this documentation as well Customer Data Feed Contents Defined & Customer Data Feed File Structure

HughBE​ .. please see this document around real-time unsegment capability, I believe it covers what surbhik48659126​ mentioned