A user profile contains demographic and behavioral information of a web page visitor, such as age, gender, products purchased, last time of visit, and so on. Adobe Target uses this information to personalize the content it serves to each visitor.
The profile information for each visitor is either stored in cookies or in third-party apps.
If your web page implements the Target code (at.js or the Adobe Experience Platform Web SDK), the profile information from the cookies is passed to Target using profile parameters. Target identifies each visitor uniquely through a
pcID that it generates in the visitor’s cookies. However, you can pass profile parameters from an external app through mbox calls using
Use the Adobe Target profile APIs when you have profile data about your visitors to send to Target that you either can’t or don’t want to send as part of your page-based integration with Target. This might be data from a Customer Relationship Management (CRM) or Point of Sale (POS) system that isn’t available on the page. Or this data might be of a more sensitive nature that does not make sense to pass on the page.
There are two ways to update profiles via API: