|
This article covers the following: |
Overview
Info: This feature is applicable for all Wingify products, i.e. Wingify Insights, Wingify Web Experimentation, Wingify Feature Experimentation (FE), and Wingify Personalize.
Attributes are variables that carry information corresponding to visitors. The values of these variables help you identify and segment visitors. Some of the common attributes include the traffic source of the visitor, the browsers used by visitors to land on your webpage, the visitor’s location, etc.
Using attributes, you can track the visitor data that is critical to your business, such as visitor's gender, subscription level, etc. For example, if you are a SaaS company, you may want to categorize users based on their subscription plans, or a travel agency that recently ran promotional offers may want to view conversions by age group.
Types of Attributes
In Wingify, attributes are categorized as follows:
- STANDARD: These are the predefined properties, such as Traffic Source, Operating System, Browser, Location, etc., on the Wingify platform and that Wingify automatically collects.
- MY ATTRIBUTES: These are the ones that you can create and configure based on your specific business needs. For example, you can create an attribute to identify the customers that have been using your website for a very long time and appreciate their association with a special offer. Or, you can identify the customers that have made very few purchases and encourage them with a discount.
-
UNREGISTERED ATTRIBUTES: These are the attributes that are captured by Wingify from your website but not found registered in Wingify. At times, instead of creating an attribute on the Wingify platform, you would use the custom code of an attribute and tweak it to become another to be tracked on your website. Sometimes, such unregistered attributes may come into Wingify from a third-party integration. In such cases, you may not be able to use the data of those attributes for any analysis or segmentation. But Wingify captures such attributes and brings them to you, so you can choose to have them registered in Wingify. If you’re passing an attribute to Wingify that you have not created under MY ATTRIBUTES, Wingify captures it and displays it under UNREGISTERED ATTRIBUTES.
Note: These attributes will continue to stay for 3 days or until registered. -
Clicking on these attributes will reveal the corresponding metadata, which includes the data type, API name of the attribute, and the sample values.
INFO: Sample Values are the values of the unregistered attributes captured from your website/application by Wingify.You can choose to save these attributes to Wingify by clicking on the Register Attribute button at the top-right. This will allow you to configure the attributes and save them under MY ATTRIBUTES.
Note: Upon registering the unregistered attributes, they will be removed from the UNREGISTERED ATTRIBUTES section. - ARCHIVED ATTRIBUTES: If you are no longer using a custom attribute, you can clear up the space by archiving it. Such attributes appear under the ARCHIVED ATTRIBUTES section. The number of archived attributes will also be displayed along with the section name in parentheses.
Any existing campaign that has been using these archived attributes will continue to use them. These archived attributes will appear in the visitor segmentation section of the existing campaigns with an ‘ARCHIVED’ tag. However, these attributes will not be available for a new campaign or any existing campaign that hasn’t yet used them.
Create Attributes
To create an attribute in Wingify, from the main menu panel, access Data360 > Attributes. Click +Create and enter the details in the following fields:
| Field | Input |
|---|---|
| Attribute Name | Enter the name of the Attribute |
| API Name |
Enter the endpoint name for your Attribute
NOTE: By default, the API Name field gets populated based on the value you have entered in the Attribute Name field. However, you can modify it.
|
| Data Type | Select the type (Text, Number, or Boolean) for your Attribute |
| Description | Enter a description that defines your Attribute |
| Data anonymization |
Mask sensitive data to protect user privacy. Choose how to manage sensitive data: Masked List (Anonymized data): A masked list is a collection of masked data rules. Items in this list anonymize specific data based on the regex pattern defined in the rule. This is the default behavior. You can add multiple masked data rules. Unmasked List (Unanonymized data): An unmasked list is a collection of unmasked data rules. Items added to this list remain unanonymized and override the masked list. You can add multiple unmasked data rules.
ATTENTION: When using unmasked lists, proceed with caution to avoid exposing personally identifiable information (PII). Wingify is not liable for handling or potential exposure of sensitive data due to unmasking. Compliance with data protection regulations remains your responsibility.
|
To finalize your changes, click Create. The created Attribute appears in the MY ATTRIBUTES section on the left.
Clicking on a custom Attribute displays the details of the same along with a custom code snippet. Clicking on a custom event displays the details of the same along with a custom code snippet. The code snippet is available for the web version (browser-based) and SDKs (for FullStack). These code snippets contain the placeholders for the Attribute variables, which need to be applied in the respective places. This ensures that each time the event is triggered, it captures the variable data from your website and stores them in Wingify. These variables differ with the type of code; hence you need to apply the variables correspondingly.
To create custom attributes that could be used for feature rollouts, testing, or personalization in FME, refer to the implementation steps for the following supported SDKs. Each link guides you through setting up custom events for the respective platform.For server-side SDKs, by integrating the Wingify server-side SDKs with your application, you can A/B test your applications on the server-side. For integrating an SDK, you just need to install the SDK from the respective package manager and then import it intoin your application. Since backend applications can be written in different programming languages, we offer Wingify SDKs in Node.js, Python, PHP, Java, .NET, Ruby, and Go languages. The custom event code is therefore also made available in all these languages.
Click on the Copy Code icon at the top-right corner of the code snippet box to copy the code. After initializing the Wingify SDK and the corresponding variables into your code repository, use this code in your application to enable this custom event for pre-campaign segmentation.
Manage Attributes
Once an Attribute is created, you can modify or clone the same based on your need. To do so, click on the Attribute that you wish to work on and perform the required action as follows:
Note:
- Users with the Owner or Admin access level can add or edit attributes.
- A custom attribute, once created, cannot be deleted, nor can the corresponding data be flushed.
To Archive - Click on the Archive option, and in the archival confirmation popup that appears, click Archive. Now the archived event will be moved from the MY ATTRIBUTES section to the ARCHIVED EVENTS section. You can always review an archived attribute by clicking on it.
An archived attribute can be edited just like any custom attribute, cloned
into a new custom attribute, or unarchived to be used again in your campaigns.
To unarchive, select the archived attribute, click on the vertical ellipsis
icon that appears at the top-right, and select the
Unarchive option. In the confirmation popup that appears,
click on the Unarchive button. Now, the custom attribute
will be moved from the ARCHIVED ATTRIBUTES section to
MY ATTRIBUTES.
Apply Attributes
You can use attributes to segment visitors during campaign targeting (pre-segmentation) and while filtering reports (post-segmentation). However, in Wingify Feature Experimentation, attributes are only available for post-segmentation.
Pre-Segmentation:
Pre-segmentation is the filter that you can apply while setting up your campaign to target your campaign to those visitors who meet your criteria.
Let’s consider that, if you are running a fashion business., Then you can target your campaign to visitors based on their gender and present your variations featuring changes that are specific to the gender of the visitors.
This can be configured at the time of campaign creation. You can access More Options > Enable campaign for a specific visitor group > Custom Segment in step 1 of campaign creation to configure the pre-segmentation settings for an A/B test.
Click on the first dropdown, and the standard and the custom attributes will appear under the Attributes section. Select an attribute, set the relation in the second dropdown, and enter the corresponding required value in the last field.
You can add more conditions by clicking Add another condition.
Post Segmentation (Report Segmentation):
Post Segmentation is the filter criteria that you set up inat your campaign reports for a targeted study. Once you have your campaign results populated, you can filter the report based on Attributes such as purchase price. For example, you can filter out those visitors that have made a purchase of $70 and above. Or, you can analyze and identify those visitors who have purchased a given product. This way you can identify the problematic or low-performing areas and approach them with appropriate measures.
For applying post segmentation to the results of an A/B test campaign, click on the Wingify campaign you want to look into and go to Report > All Visitors > Custom Segment.
Click on the first dropdown, and all the standard and custom Attributes will appear here. Select an Attribute, set the relation in the second dropdown, and enter the corresponding required value in the last field.
You can add more conditions by clicking Add another condition.
Defining Scope for Custom Attributes
If you’re applying post segmentation in Funnels, Heatmaps, and Session Recordings, you will be able to see a dropdown to define the scope of the custom Attribute. Scope determines what information is collected in the Attributes and is classified as follows:
User Scope - Upon selecting this option, Wingify produces the count of visitors by looking for the latest value of the attributes that match with the one you have specified in the filtering criteria. These attributes can be age, favorite sports, current plan, etc.
For example, you can tag visitors with their plan type and analyze the funnel performance of users who are on Lite plan against the Pro plan. Or, you can track the gender information, and then view heatmaps/session recordings only for female visitors.
Session Scope - Upon selecting this option, Wingify produces the count of visitors by looking for the latest value of the attributes corresponding in each session that matches with the one you have specified in the filtering criteria. These attributes can be signed-in visitors, total purchases made during a session, total time spent on a given page during a session, etc.
For example, you can compare the conversion rate for the Add to Cart button goal for signed-in vs. guest users, or view heatmaps for only signed-in users. You can also view the differences in the behavior of the visitors, who are spending a particular amount of time on a specific page.
Need more help?
For further assistance or more information, contact Wingify Support.