Unable to utilize bulk update api in Adobe Target to add custom profile attributes. Attributes not recognized.
Hi all,
I'm new to Target. My goal is to ensure that we can provide personalization for users when they log on to one of our pages.
In order to do that, we're adding profile attributes using the pcId (tntId) via the Target Bulk Update API in the link below by adding them into a file and then using curl to push it to the Target endpoint for our client code.
We are not able to pull the values for each parameter specified in the file for use in a defined Target Audience.
For example, in my case, the contents of my file is very simple.
batch=pcId,primaryRole,personna,hasAuth
c0be691c46574646946c0972ddbb3f36,Senior Engineer,Architect,Yes
45f0b9533b474ee68e5256010db0b5e8,Senior Engineer,Architect,Yes
There are two pcIds and 3 profile attributes; primaryRole, personna and hasAuth.
When I run the curl command, I get the output indicating a successful export into Target.
<response><success>true</success><batchStatus>http://mboxedge44.tt.omtrdc.net/m2/xxxxprofile/batchStatus?batchId=xxxx-1702421749846-98858546</batchStatus><message>Batchsubmitted for processing</message></response>
In the Target UI, we set up an activity and an experience for a specific web page.
We then create profile attributes for the primaryRole, personna and hasAuth profile parameters.
In the profile Scripts, we can set up each of these parameters as follows in 3 different scripts; one for each parameter.
return user.get('primaryRole');
return user.get('personna');
return user.get('hasAuth');
All 3 parameters are found by the suggestions provided when setting up the scripts.
After activating the scripts, we then create an audience (or use an existing one) and try to see if we can use them in the Audience by using a Visitor Profile container and choose user.<script> for one of the attributes say 'primaryRole'. We use an action of 'Parameter is present' and click on Done to register and save the Audience.
However we do not get the desired experience (here we are simply highlighting some text on the web page) for the page configured in the activity. This is true for *any* of the profile parameters that we specify in the bulk update file that we used above. We can see them in the Visitor Profile drop down in the specified Audience as if they are recognized by Adobe Target but we cannot validate them if they are present in the Audience nor can we get the values that we set in the file used in the bulk update export for the profiles in question,
Our pcId's are recognized and we can get the experience if we simply match the Visitor Profile on the pcId attribute solely by itself, but we cannot match any profile attributes that were specified using the bulk update nor can we validate that any of these attributes are present. Note that we *do* get the experience on the web page if we configure the Audience for any of the parameters to 'Parameter is not present'.
If I query the Target Profile API using the tntId for the pcId's used in the file for the Bulk export, I can get all the profile attributes returned for that profile but I do not get the profile parameters I specified in the bulk update file ('primaryRole', 'personna' etc).
I'm thinking that I did not configure something properly here or am missing something that is very simple but I've put in a lot of time debugging this and haven't gotten anywhere.