Our organization uses the DCS API for on-boarding of CRM data (for various reasons, we're not permitted to use the AAM file transfer mechanism). DCS is fine for qualifying a user for rule-based traits, but how can we disqualify a user? For example, suppose we have a trait User Gives Consent for which a given user is qualified and later that user withdraws their consent. To comply with GDPR rules we should disqualify that user within 72 hours. But how?
If we limit our User Gives Consenttrait to a lifetime of 72 hours then okay it'll expire, but then we need to keep refreshing the trait needlessly for all those (possibly millions) of users whose consent doesn't change. This seems like a brute force solution. Has anyone else got a better idea? I did hear rumours of a DCS API upgrade coming in 2019 that would include a trait disqualification feature. Here's hoping!
My name is Ankita Sodhi and I am from AAM Tech Support Team.
I understand that you are looking for a solution on real-time trait disqualification so that opt-in and opt-out can be tracked in AAM.
I would like to highlight that currently we can't remove users from trait in real-time but the same is possible via offline data onboarding method. The feature of removing user from trait in real-time via DCS API calls is a work-in-progress task and we have this on our pipeline.
I do not have any ETA yet which I can confirm on but I can see that our engineering team is engaged into this task and working towards a release.
For now, I suggest that you create a segment using AND NOT logic as mentioned in your scenario, so that it will give you all the users
who are in opt-out list. (Segment rule (opt-out AND NOT opt-in))
I will check on further options and will come back on this thread.
Hi ASodhi-AAM ShwetaSingh, following on from my queries in another AAM forum thread, in October 2018 you mentioned that the feature of removing users from traits in real-time via DCS API calls is a work-in-progress task and it is on your engineering pipeline. Can you please advise any reference numbers and the status of this request - we are very excited about this prospect as other options promoted are not useful to our use cases? Many thanks, David.
In this case it can get tricky. If you know that your user opts in and opts out that frequently, then probably the best way to go about it would be to upload a batch file of updated list of users. Frequency of the batch file upload can be set to daily.