Customer properties

Use customer data to personalize targeting.

Customer properties let you tailor an Experience to the person using your app. Store details such as language, onboarding progress, or the number of projects they’ve created, then use those values to choose who receives an Experience.

For example, you can show a localized introduction to English-speaking customers or leave completed users out of an onboarding reminder. Properties can be used directly in conditions or combined in a reusable Segment.

Set properties

Identify the customer through your SDK, then send the properties your app uses. A property has a name and a value: language: "en", onboarding_complete: true, or projects_created: 3.

Use the same names and value types across your integrations. A number such as 3 can be compared with a usage threshold, while the text "3" is a string.

Properties describe the customer’s current state. Events record something that happened. You might send an onboarding_completed event when setup finishes and set onboarding_complete to true at the same time. You can use the event to measure completion and the property to decide whether to show onboarding again.

Manage properties in a profile

Open Customers, choose the customer, and select Properties. You’ll see each key, its value, and its type. You can filter by key or type and sort by either of those fields.

Add a property

Click Add property, enter a unique key and value, then save it. The value field accepts JSON, so true is saved as a Boolean, 42 as a number, and an object or array as structured data. Other input is saved as text.

If you want a JSON-looking value to remain text, put it in quotes. For example, "42" saves a string rather than a number.

Delete a property

Use Delete on the property’s row to remove it. This leaves the property absent. Setting it to false, an empty string, or null stores a value instead, which can produce different results in your conditions.

Segment conditions

Choose a property in the Segment builder, then pick an operator and value. You can compare exact values, match text, compare numbers or dates, or check whether a value belongs to a list.

is set and is not set let you include customers based on whether a property exists. This is useful when some customers haven’t supplied a value yet. For a localized Experience, you could match language equal to en and add an alternative group for customers whose language isn’t set.

Update properties

Send a new value when the corresponding state changes in your app. Nuxie uses the last value it received; changing a setting only in your app doesn’t update the property in Nuxie.

Answers collected in an Experience are stored as Responses. If an answer should also affect future targeting, have the Experience or your integration update a Customer property. You can keep the original onboarding answers in the response collection while using onboarding_complete for the customer’s current status.