# Updating user properties via identify api

**URL:** <https://community.hubspot.com/t/updating-user-properties-via-identify-api/11960>\
**Category:** APIs & Integrations\
**Created:** [October 25, 2017, 7:20pm UTC](https://community.hubspot.com/t/updating-user-properties-via-identify-api/11960 "2017-10-25T19:20:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [October 25, 2017, 7:20pm UTC](https://community.hubspot.com/t/updating-user-properties-via-identify-api/11960/1 "2017-10-25T19:20:34Z")

</div>

I’d like to run regular updates of the user’s information using the javascript identify api but the information does not seem to be reflected in hubspot after running `_hsq.push(["identify", identity]);"` where identity is an object filled with `{property: "value"}`

Just to clarify I follow this up with `_hsq.push(['trackPageView']);` so it should definitely send

---

<div class="post-metadata">

**Author:** ![Derek\_Gervais](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/derek_gervais/32/17429_2.png) [@Derek\_Gervais](https://community.hubspot.com/u/Derek_Gervais)\
**Post date:** [October 26, 2017, 5:54pm UTC](https://community.hubspot.com/t/updating-user-properties-via-identify-api/11960/2 "2017-10-26T17:54:54Z")

</div>

Hi @Dylan,

Are you including the contact’s email with every identification call? Also, what’s the use case you’re trying to solve with regular updates via the tracking code API?

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [October 26, 2017, 6:38pm UTC](https://community.hubspot.com/t/updating-user-properties-via-identify-api/11960/3 "2017-10-26T18:38:15Z")

</div>

We’re trying to solve issues with some race conditions for our activation, as well as maintaining membership state. Do we need to always have the email or just on the first identify?

Seems to be working now but not sure what changed. Could be a corrupted record.

---

<div class="post-metadata">

**Author:** ![Derek\_Gervais](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/derek_gervais/32/17429_2.png) [@Derek\_Gervais](https://community.hubspot.com/u/Derek_Gervais)\
**Post date:** [October 26, 2017, 8:42pm UTC](https://community.hubspot.com/t/updating-user-properties-via-identify-api/11960/4 "2017-10-26T20:42:39Z")

</div>

Hi @Dylan,

Technically once a `hubspotutk` cookie is associated with a contact record, subsequent identification calls can be made to update the contact record without including the email address. This isn’t recommended, however, since if the person clears their cookies or something similar, those identification calls (and the property updates) will be lost. In general, it’s best practice to include a contact’s email whenever you have it.

I’m glad to hear that it’s functioning correctly now; if you continue to experience issues with the tracking code API, please don’t hesitate to follow up in this topic.