[Bug]: Difference in request payload for setCustomUserAttribute dependent upon value type

[sparsons-gh]

Braze Web SDK Version

4.7.2

Integration Method

CDN

Browser

Chrome

Steps To Reproduce

Invoke the setCustomUserAttribute with a string or an array of strings.

Example 1 (array of strings): .getUser().setCustomUserAttribute('some-attribute', ['first-value', 'second-value']);

• This will eventually results in a request where the attribute values will appear events array

  events: [
  {
      "name": "set",
      "time": 0000000000,
      "data": {
          "key": "some-attribute",
          "value": [
              "first-value",
              "second-value"
          ]
      },
      "session_id": "session-id",
      "user_id": "user-id"
  }
  ]

Example 2 (string: .getUser().setCustomUserAttribute('some-attribute', 'first-value, second-value');

• This will eventually result in a request where the data is sent in the attributes array

  [
  {
      "user_id": "user-id",
      "email": "some@email.com",
      "first_name": "q",
      "last_name": "a",
      "custom": {
          "some-attribute": "first-value, second-value"
      }
  }
  ]

Expected Behavior

We expect the behavior to be similar between the type data types, string and string[] - we expect that the data should be in either events or attributes for both types, preferably the attributes array.

Actual Incorrect Behavior

As explained above, when a string[] is used as the value to setCustomUserAttribute, the data is included in the events array, and conversely, when a string is used as a the value, the data winds up in the attributes array.

Verbose Logs

No response

Additional Information

No response

[wesleyorbin]

Hi @sparsons-gh. This is intended behavior and expected by our backend. I'm going to close out this issue, but feel free to re-open or open a new issue if you notice any problems with the data flowing to the backend correctly.