Custom contact properties store information about a contact that Userorbit can use in audience rules.
Custom contact properties store information about a contact that Userorbit can use in audience rules. Examples include a plan, role, account size, or onboarding state.
Choose the data type
| Type | Example | Use |
|---|---|---|
| String | growth |
A plan name or role. |
| Number | 25 |
Account size or a numeric score. |
| Boolean | true |
Whether a defined milestone is complete. |
| Date | A signup date | Before, since, or date-based comparisons. |
The internal name identifies the property in your integration. The display name makes it readable in Userorbit. Keep the internal name stable, and send values that match its type.
Creating a property defines the field; it does not populate every contact with a value. Check an identified test contact after updating your integration, then test a segment against that contact.
Use Manage contact properties for creation, editing, and deletion steps.
Use properties in targeting
Choose a property in a saved segment or a User attribute targeting condition. Use known contacts to test one matching and one non-matching value. If a contact does not qualify, check the internal property name, value type, and whether the field is populated.