In our company, we need to on-board CRM data in real-time, hence our use of DCS API requests. But it's unclear from the product documentation which trait type will be affected when our server delivers DCS /event calls. See https://marketing.adobe.com/resources/help/en_US/aam/trait-qualification-reference.html We might have expected on-boarded traits to be affected but the explanation only refers to the arrival of inbound files. Can you please clarify? - Thanks, Hugh
DCS API calls can let a device ID or CRM ID qualify for a rule based traits. For inbound data ingestion using onboarding files you can create onboarded traits.
But for the purpose of getting data via DCS API calls, you need to create rule based traits.
HughBE, just wanted to say thanks for the very thorough feedback I got from you, I sincerely appreciate the time you took for the write-up. My team and I will look at turning the points you made into actionable items.
Victor here, from the AAM documentation team. Thanks for your suggestion.
If you don't mind, I'd like to know more about the help articles you guys used to set up onboarding of CRM data via the DCS APIs and the difficulties you faced. That will help us create an end-to-end document
At your convenience, please send me a mail at firstname.lastname@example.org.
Thank you for your clear answer. It explains why I was getting odd results. Maybe someone could update the Audience Manager Help page (see the link in the original question) to make it clear for other customer in future. Thanks again and best wishes from Belgium!
As you requested, I have sent a detailed description of our experience that will hopefully lead to improved DCS API documentation. Thanks for your willingness to improve - that's nice to see.
That would be excellent Varun. For those clients who must use the DCS API for on-boarding of CRM data, it can be difficult to figure things out by searching across lots of help pages. Any new insights/procedures document would help a lot. Enjoy the rest of your day. - Sincerely, Hugh
Thanks for the feedback. We have noted this and I will pass on this to our doc team to make AAM DCS APIs insights/procedures available in a step by step doc.