Using the "Identify" method of our mobile SDKs you can easily add properties to a user that can be used to target surveys to them and associate the information with all of their future responses.

These properties can include things like a unique user id or other properties like email, age, or any custom user data you have. Once the user data has been associated with them it will be used on all future responses to surveys from that user.

Additionally you can associate any response data with a user's response, unlike user data, response data is only associated with the users responses to the current survey they are filling out, not on any future survey responses.

Response properties are commonly used to include information about the page they are on (e.g. url, sku number, order id, product name, etc)


(iOS examples below, but available within all of our mobile SDKs)

Setting user properties

Iterate.shared.identify(userProperties: [
"email": UserPropertyValue("[email protected]"),
"user_id": UserPropertyValue(1001)

Setting user properties only

Iterate('identify', { email: '[email protected]', user_id: 1001, });

Setting response properties only

Iterate.shared.identify(responseProperties: [
"order_id": ResponsePropertyValue(123)

The property values must be a boolean, string, or number.

Important Notes

1. Once created, the type of a property (e.g. 'user_id' is a number) cannot be changed.

If you need to update the property type you can create a new key (e.g. 'user_id_string') or reach out to [email protected] to help.

Special properties

There are a few special user properties which can be used to identify users. If you send these properties you'll see the user's name or email shown on the dashboard next to their responses.

  • email
  • first_name
  • last_name


Once you've called the identify method, you'll find the list of user properties available to target a survey on in the 'Targeting' tab.


In addition to targeting users based on properties, all user properties and response properties will also be available to view on our dashboard and in all available export formats (CSV, Zapier, webhooks).

Did this answer your question?