Custom Properties are properties on a user which can be used for Targeting Users for Features. These properties are different than the out of the box options within DevCycle (such as app version etc) in that they are defined by user for use within the dashboard.
This article outlines how to define, use, and manage custom properties within DevCycle and its SDKs.
Custom properties can be one of the following types:
These properties can be added to any User object with the Identify method in the DevCycle SDKs, or provided as part of the user object in the .
Creating a new property for use.
To use a custom property in a targeting rule, first initialize the property in a target on the DevCycle dashboard. This can be done from the Target's definition dropdown:
Doing so will open a modal to create your new property.
This modal has two mandatory fields:
The property key should match what is being sent by the SDKs or APIs. This is used to match the data up.
Select the corresponding type of your custom property. This type must match with the type the SDKs are sending.
The types are currently:
There are two additional fields when creating a Custom Property at the bottom of the creation modal
This field is only for changing what the property's name is in the DevCycle UI. This can be useful when handling properties with extremely long or auto-generated names. The property key is what will be used for all matching when bucketing users.
This is an auto generated field based on the property key. This is the key which can be used to reference the property in the DevCycle Management API.
Using an existing Property
Once a property has been created, it will be accessible in the definition dropdown:
First, select your property to use it like any other targeting definition as outlined in Targeting Users
Then, finish your Targeting Rule by filling out the comparator and the value fields.
There are no limits to the number Properties that can be used to define a single Targeting Rule! Use as many custom properties as necessary to accurately target your users for your features.
See the Identify Documentation for usage of properties within each SDK.