Visitor profile attributes not present after updating profile from API

[bruno-bradach]

Hi! I'm working on a cart abandonment example and I'm having an issue with Target.

I created the following audience in Target and I'm using it in an activity to display a message:

Also, I'm updating the profile through the bulk update API sending the pcId that I receive from my Analytics Trigger (through I/O Events) together with some other attributes.

And I can see that the profile is properly updated by hitting the endpoint to get a profile: https://xxx.tt.omtrdc.net/rest/v1/profiles/aab5c29b49764e3a8a861904a47bf291.17_0?client=xxx

This is the response I get:

{
  "client": "xxx",
  "visitorId": "85873594577024071332555981770939565448",
  "modifiedAt": "2020-04-14T08:29:10.992-04:00",
  "profileAttributes":
    {
      "trCoupon": {
        "value": "ADBETGT5OFF",
        "modifiedAt": "2020-04-14T08:29:10.992-04:00"
      },
      "trPrices": {
        "value": "39",
        "modifiedAt": "2020-04-14T08:29:10.992-04:00"
      },
      "mcId": {
        "value": "85873594577024071332555981770939565448",
        "modifiedAt": "2020-04-14T08:29:10.992-04:00"
      },
      "trProducts": {
        "value": "Some shorts",
        "modifiedAt": "2020-04-14T08:29:10.992-04:00"
      },
     "trOffer": {
       "value": "5",
       "modifiedAt": "2020-04-14T08:29:10.992-04:00"
     }
   }
}

However, when I navigate to the page where I created the activity I don't see the message. But if I change the audience to the following then I do get the message displayed in the screen.

Is there something that I might be missing? Is Target somehow not matching the pcId that I update through the API with the one stored in the cookies?

Thank you!

[Tanvi_Agarwal_ · Accepted solution]

Hi @bruno-bradach ,

If the required parameters is available through the API, then the activity should be able to pick it up for content delivery.

Have you tried deleting browser cookies or in a new session? 

[Ruan]

Hi bro

If the required parameters is available through the API, then the activity should be able to pick it up for content delivery.

Trie deleting browser cookies or in a new session?