Adobe  I/O Adobe Target

Profile Fetch

Adobe Target creates and maintains a profile for every individual user. This profile is stored on the Target edge cluster and is updated in real time after every visit.

Structure of a Target Profile

A Target Profile consists of these following objects

clientcode The Target client code to which the profile is associated
visitorId The identifier for the profile. This can be a tntid or thirdpartyid or marketingcloudvisitorid
modifiedAt The timestamp of when the profile was last updated.
profileAttributes List of all the profile attributes stored as key-value pairs on that the individual profile

Fetching a profile

A Target Profile can be fetched in two ways

1. Using a tnt id

Target automatically assigns a tntid for every request. The request format to fetch a profile using a tntid is

https://yourclientcode.tt.omtrdrc.com/rest/v1/profiles/your-tnt-id?client=yourclientcode

Replace "yourclientcode" and "your-tnt-id" and fire a GET request. Here is an example profile fetch call using a tntid

http://adobetargetmobile.tt.omtrdc.net/rest/v1/profiles/111492025094307-353046?client=adobetargetmobile

2. Using a thirdPartyId

Target profiles can be augmented with your own identifier (eg: CRM id, uuid, membership number etc). See the profile update section to learn how you can attach a thirdPartyId to your profile. 

The request format to fetch a profile using a thirdPartyId is

https://yourclientcode.tt.omtrdrc.com/rest/v1/profiles/thirdPartyId/your-thirdpartyid?client=yourclientcode

Replace "yourclientcode" and "your-thirdpartyid" and fire a GET request. Here is an example profile fetch call using a thirdpartyid 

http://adobetargetmobile.tt.omtrdc.net/rest/v1/profiles/thirdPartyId/a1-mbox3rdPartyId?client=adobetargetmobile

When this call is made, Target attempts to locate the profile first in the cluster noted in the edge request, or wherever the profile is located and return the content. The profile contents are returned in JSON format. 

Authentication

This API is currently not authenticated.

Metering

These calls do not count towards your mbox calls.

Error Handling

In the case of a call to /thirdPartyId with an invalid or an expired thirdPartyId specified:

{"status" : 404, "message" : "No profile found for client <client_code> with third party id=<third_party_id>"}

If the profile can not be located or has expired:

{"status" : 404, "message" : "No profile found for client <client_code> with mboxPC=<mbox_pc>"}