Issue with updating custom fields through Segment.com identify call

Developer Support APIs & Integrations
1

Hey

We are using Segment to sync contacts and user information to Hubspot.

Hypefactors is a SAS software solution for Media monitoring etc. we want to create and update the contacts in Hubspot with information about their use of our platform.

Creating the contacts and updating fields like name and email is working fine but I can’t get it to populate custom fields.

Here is an example of the identify call that we are sending:

{
 "context": {
 "library": {
 "consumer": "LibCurl",
 "name": "analytics-php",
 "version": "1.5.2"
 }
 },
 "integrations": {},
 "messageId": "22c35b72-b72a-45e8-b6db-68aed2f4a905",
 "originalTimestamp": "2019-11-26T10:47:25+00:00",
 "receivedAt": "2019-11-26T10:47:26.441Z",
 "sentAt": "2019-11-26T10:47:25.000Z",
 "timestamp": "2019-11-26T10:47:26.441Z",
 "traits": {
 "activatedAt": "2016-12-02T11:04:14Z",
 "createdAt": "2016-12-02T11:04:14Z",
 "email": "cc@integral.dk",
 "firstName": "Christoffer",
 "fullAccess": true,
 "fullName": "Christoffer Chrintz",
 "id": 380,
 "inDailyEmail": false,
 "jobTitle": null,
 "language": "en",
 "lastLoginAt": "2019-11-26T10:47:24Z",
 "lastName": "Chrintz",
 "phone": null,
 "planAssociation": "Paid",
 "timezone": "Europe/Copenhagen",
 "updatedAt": "2019-11-26T10:47:24Z"
 },
 "type": "identify",
 "userId": "f694fced-4164-4648-86db-0a39a91dc087",
 "writeKey": "m9vIMRe01fRWV9UAq10QInKulLCChM2A"
}

Currently, I have created the custom field planAssociation in Hubspot:

2019-11-26 11_44_26-NVIDIA GeForce Overlay.png
2019-11-26 11_44_26-NVIDIA GeForce Overlay.png583×369 14.5 KB

But I can’t get it to populate the field.

2

Hi @Chrintz,

The internal value for the property planAssociation is planassociation, could you try using planassociation in the identify function and see if that works?

3

Hey Wendy

Thanks for your reply.

I had tried that but Segment automatically converts everything to lower case characters so that wasn’t it.

I did, however, find the issue. It was a bug on segments side where they were formating the request wrong or something (Their explanation).

It seems to be working now.

Thanks

4

Hi @Chrintz,

Thanks for sharing this and I’m glad all is working well now :slightly_smiling_face: