Information about the different methods you can use to get data into Adobe Target.
Available methods include:
(Also called "mbox parameters")
|Page parameters are name/value pairs passed in directly through page code that are not stored in the visitor's profile for future use.|
Page parameters are useful to send page data to Target that does not need to be stored with the visitor's profile for future targeting use. These values are instead used to describe the page or the action the user took on the specific page.
|In-page profile attributes|
(Also called "in-mbox profile attributes)
|In-page profile attributes are name/value pairs passed directly through page code that are stored in the visitor's profile for future use.|
In-page profile attributes allow user-specific data to be stored in Target's profile for later targeting and segmentation.
Users write small code snippets that execute per mbox call, and before a visitor is evaluated for audience and activity membership.
|Data providers||Data providers let you easily pass data from third parties to Target.|
|Bulk profile update API||Via API, send a .csv file to Target with visitor profile updates for many visitors. Each visitor profile can be updated with multiple in-page profile attributes in one call.|
|Single profile update API||Almost identical to the Bulk Profile Update API, but one visitor profile is updated at a time, in line in the API call instead of with a .csv file.|
|Customer attributes||Customer attributes let you upload visitor profile data via FTP to the Experience Cloud. Once uploaded, use the data in Adobe Analytics and Adobe Target.|