@akwankl- The situation is different for onboarded traits. In that case the "realization" happens when the file containing the key-value pair to qualify for the trait is processed. So with a TTL of 15 days, if the information is not received again within 15 days of the file being sent, the trait would be removed from the user profile. The times that a user comes to site does not affect the onboarded trait being removed from a profile due to TTL - a user could come to site every day, but the onbo...

Hi Srujana It is already possible to overwrite previously onboarded data using ".overwrite" files. This is described in the product documentation here: https://docs.adobe.com/content/help/en/audience-manager/user-guide/implementation-integration-guides/sending-audience-data/batch-data-transfer-process/inbound-s3-filenames.html In particular, this part about .overwrite files:"overwrite : Lets data providers send a list of traits on a per-user basis that should overwrite all of this user's existin...

Yes, this is possible. 3rd party traits can be included in exports run through the REST API, using the BAAAM bulk management tool (https://docs.adobe.com/content/help/en/audience-manager/user-guide/reference/bulk-management-tools/bulk-management-intro.html). The volumes can also be included in General & Trend reports (https://docs.adobe.com/content/help/en/audience-manager/user-guide/reporting/general-reports.html). Either of these methods will allow you to see the full set of 3rd Party traits i...

Hi Yes, as per the documentation, SHA256 email hashing is required, not SHA512. The reason for this is that the hashing method used for the email addresses sent to AAM, must be the same as the method used by the destinations (e.g. Google, Facebook, LinkedIn etc). As Audience Manager is essentially passing through the hashed email addresses (along with segment qualification information) the hashed emails must match the standard required by the destinations themselves, which is SHA256. Hope this h...