Not used for targeting and getTreatment
Customer attributes stored using the methods discussed here aren't used for targeting your roll out definitions or as part of the standard usage of getTreatment. In order to target, you must pass the attribute with the
getTreatment call. Learn more about targeting based on custom attributes.
You can use the identities REST API to identify your keys in Split, making them available when writing targeting rules in the user interface and enriching autocomplete functionality throughout the user interface. Identifying your keys is useful if you want to pre-populate the user interface for your team and provide customer data when setting up your rollouts and analyzing impression data.
Split offers both a identities REST API and client-specific API wrappers to use when sending to Split attributes on your keys.
As an administrator in Split, you can see the attributes that your team is sending to Split and the last time an update is received. To manage your organization's attributes, do the following:
From the left navigation, select Admin settings and then Workspaces.
Click View for the workspace you are working in and then the Traffic types tab.
Click View/edit attributes.
Optionally, edit the display name, description, and attribute type.
Click Save. The attributed is updated.
You can view a customer's attribute data on the third tab of the customer dashboard which is populated from the attribute data you send using Split's API. To navigate to this dashboard, click on a unique key when you view impression data or use the search bar on the left navigation panel.
Please sign in to leave a comment.