While creating a custom attribute, you are asked to define an identifier for it. The identifier of a custom attribute becomes the key field in your event layer.
And, custom attributes are segmentation properties that you create within UserGuiding's Dashboard to define specific user segments for your guides, hotspots, and etc.
An identifier is also used as the custom attribute's name since it defines the user property that you want o make trackable. You can create various custom attributes based on properties that you want to segment your users. For instance;
Let's assume, in your web platform, your customers differ from each other based on product plan they use as users having freemium plan and premium plan.
And you've just released two different new features each for a different plan, and you want to promote these features with UserGuiding guides.
That's why, you designed two custom guides and now, you need to direct each of them, separately, to the correct user segment having the following custom attribute.
Creating a Custom Attribute
In the above image, ‘customer_type’ is the key field in your event layer. It is the identifier of the custom attribute.
Text is our Data Format. Since the value of your user segment is in text form.
Data source is UserGuiding. So, the code snippet (container JS code) will check the data you've set through 'userGuiding.track’ method.
If you click on SAVE, you will see the following code snippet.
Copy the code below and insert it into your application (A developer can decide on the snippet's location).
The value in your event layer should change with respect to the customer type as free or premium.
Expected code tracking snippet if the customer's plan type is freemium:
And, if the customer's plan type is premium: