1. Overview

In real business scenarios, you might need to identify users who meet specific criteria for targeted analysis. For this purpose, user segments can be used to as the filtering or group display conditions in other SolarEngine analysis models.

Through user segments, the following questions can be answered:

• How many users haven't logged in since 8 days ago?
• How many users made their first payment yesterday?
• How to create a user segment for analytics by importing account IDs?

2. Usage Guide

SolarEngine provides product-level user segments for usage within the same product, and also offers global user segments that can be applied across multiple products.

Clicking on "Analysis-User Segments" in the product navigation: you can enter product-level user segments.

Clicking on "Asset Management-User Segments" in the top menu on the homepage: you can enter tenant-level user segments.

SolarEngine supports the following user segment types.

• Conditional Tag (Product-level/Tenant-level): Users who meet the defined conditions will be grouped into the segment. You can choose to update these tags either on a scheduled basis or manually.
• ID Tag (Product-level/Tenant-level): Create a user segment by uploading a file with associated IDs, and the system will find corresponding users. Once uploaded, these tags cannot be updated.
• Result Tag (Product-level): These tags are directly saved based on the calculated results from an analysis model. Result tags cannot be updated once they are generated.
• Preset Tag (Tenant-level): These tags are created based on preset conditions.
• API Tag (Product-level/Tenant-level): These tags are created and updated through API integration.

2.1 Product-Level Tags

2.1.1 Conditional Tags

Conditional tags are generated by setting a series of calculation conditions. These conditions support event-related conditions and property conditions related to users, devices, and events.

• By default, product-level conditional tags are limited to the current product and cannot be modified.
• When creating tags, you can either select the preset entity, or your custom entity for calculation.
• When creating conditional tags, you are required to select a time zone. The selected time zone will be used as the reference for tag calculations and result display, ensuring consistency and accuracy in analyzing user data.
• The tag name should not exceed 30 characters, and the tag description or remark should not exceed 80 characters.  

1) Update Method

Manual Update

Automatically filter out the target users once the user tag is created. No more updates without manual operation.

Auto Update

Automatically filter out the target users once the user tag is created. Update the target users at 00:30 AM every day.

2) Add Tag Conditions and Tag Values

Under a single tag, you can create multiple tag values. Each tag value can correspond to a set of conditions. Users who meet the conditions for a specific tag value will be assigned that value. If a user satisfies multiple conditions, they will be assigned multiple tag values.

       The tag value should be string type. When applied in analysis models for filtering and grouping, string-based grouping and filtering methods are applicable.

3) Add Event Condition

      You can select "Done", "Not Done", or "Done Sequentially".

▪ Done: Users who meet the condition will be targeted.

▪ Not Done: Users who don't meet the condition will be targeted.

▪ Done Sequentially: Users who trigger multiple events sequentially will be targeted.

For "Done" or "Not Done", the event condition is composed of "Event + Event Property/Metric + Statistical Method + Threshold + Time Window".

▪ Event: Select from all events within the current app.

▪ Property/Metric: Properties available vary from the event selected. Preset metrics are event totals and day totals.

▪ Statistical Method: If a metric selected, you can select "more than", "less than", "equal", "not equal", or "in range of". If a property selected, the statistical methods available depend on the selected property.

▪ Threshold: A specific value or criterion used to determine whether the condition is met or not.

▪ Time Window: During which the selected event occurs. You can choose dynamic time or static time.

For "Done Sequentially", the event condition will be a series of orderly events.

▪ At least two events shall be defined.

▪ You can add a condition (Not done event X) between two events.

▪ You can add filters for one single event, or add global filters for all events in the sequential.

▪ You can set the largest time interval between two events, or the maximum time range within which all events shall be completed.

▪ If an associated property is set, then all events in the sequential should have this property before users can be targeted.

4) Add Property Condition

     The structure of a property condition is "Property + Statistical Method + Threshold".

Depending on the selected analysis entity, you can choose to add event properties, device properties, or user properties.

▪ Event properties are available for all entities.

▪ Device properties are available if the entity is defined by device ID, such as _distinct_id, _oaid and _gaid.

▪ User properties are available only when "_user_id" or "_account_id" is set as the entity.

The processing logic of "AND" and "OR" can be set between event conditions and property conditions, or set between two event/property conditions.

2.1.2 ID Tags

       Create tags for users by uploading user IDs. User tags created in this way cannot be updated.

1. Supports UTF-8 encoded CSV file uploaded, and the file cannot exceed 100M.

2. The first column of the uploaded file is used to search for users, and the header must be an existing user property ID.

3. By comparing user properties with the first column values, all matched users will be saved to the corresponding tag values.

4. The second column is the Tag Value, and any row with no value in the two columns will be discarded.

2.1.3 Feature Tags

Feature tags are based on the property value of a user's first or last event that occurred within a specified time range.

It can be used to analyze the distribution of certain property values in a user's first or last event, such as the city distribution of first payment, the role for first battle, or the ad type of the first ad impression.

The data type of a tag value applies with the selected event property, and the data type decides available calculation methods when it's used for filtering and grouping in analysis models. Please refer to the instructions in event analysis for more details.

One predefined statistical method for feature tags is "Days since Calculation Date," which has a numeric data type and should be used with numeric methods when applying it.

2.1.4 Indicator Tag

Indicator tags are based on the event metrics that occur within a specified time range.

It can be used for analyzing the amount of key metrics during a specified activity or period, such as the total payment amount during an active period, or the number of ad impressions on a specific ad placement within a specified time.

The data type of indicator tag values is numeric. It is suitable for grouping and filtering using numerical methods in analysis models.

2.1.5 Result Tags

Create tags by calculating "Unique Visitors" in other analysis models. In this case, hovering over the result value will display a small icon "+" next to it. Clicking on the "+" opens a pop-up window to create a result tag.

In the result tag window, both the tag name and tag value are required. The tag value will be automatically populated with the analysis name but can be modified. Clicking on "Confirm" will save the user group as a result tag.

2.2 Tenant-Level Tags

A tenant-level tag can be generated and used across multiple products. You can find tenant-level tag through Homepage -> Asset Management -> User Tag

Tenant-level tags is an advanced feature so not available by default. If you need this feature, please contact your customer manager to unlock the function for you.

2.2.1 Conditional Tags

Tenant-level conditional tags allow you to select multiple products within the same data storage area (China Mainland or Non-China-Mainland).

For calculation rules, you can choose either "All products meet the conditions" or "Any product meets the conditions".

• All products meet the conditions: Only when a user satisfies the set conditions across all products will they be tagged.
• Any product meets the conditions: If a user meets the conditions in any one product, they will be tagged.

With cross-product tags, you can quickly identify users who have performed the same actions in each product or users who have performed specified actions in any product. This provides new methods for precise user identification and enables personalized marketing.

2.2.2 ID Tags

When uploading tenant-level tags, you need to specify the Product Range. You can simultaneously select multiple products within the same data storage area for this purpose.

2.2.3 Preset Tags

Preset tags include the most commonly used tag conditions in real business operations.

When using preset tags, you only need to adjust the parameters according to your requirements to enable tag calculations. This reduces the complexity of configuring tag conditions and improves the work efficiency.

2.3 API Tags

If you have already created tags in other CDP or DMP systems, we provide the option to import user tags via API. By integrating with our system, you can automate the process of importing external tags or periodically updating imported tags.

For the API tag importing documentation, please reach out to our support team or contact your customer manager for assistance.

2.4 User Tag List

       All the created user tags will be displayed in the user tag list. Here you can take a quick look at the tag ID, tag name, tag remarks, entity, user quantity, tag type, update time, creator, creation time, and status.

2.4.1 Product-Level Tag List

• Clicking on the tag ID or user quantity will open the "Tag Details" page.

• For tags with the status of "Completed", click on "Update" will manually update the selected user tag.

• Only conditional tags are editable. Click "Edit" to make modifications.

• Click on "Delete" to remove the selected user tag.

2.4.2 Tenant-Level Tag List

Different from product-level tags, above the tenant-level tag list is an industry tag, which displays the industry preferences of users based on big data analysis.

• By weight

       If a user is more interested in a particular industry, this industry will be assigned a larger weight value.

• By quantity

       In this case, the weight is not considered, and each user within the same industry is counted as 1.

       Industry tag is helpful for understanding the user composition and interest preferences of existing products before launching a new product. They can assist in developing advertising strategies and more. To utilize this feature, please contact our business personnel.

2.5 The Application of User Tags

User tags can be applied in conditional filtering and result grouping within analysis models, as well as in audience segmentation for A/B testing and online parameter selection.

When applied to analysis models, the filtering and grouping methods are similar to those used for properties. Different filtering and grouping methods are provided based on the data type of the tag values.

Introducing user tags into analysis models allows for comparing user behavior performance among different tag values. This is one of the most commonly used applications of user tags.

3. Permission Explanation

Product-Level Tags:

Operation Permissions : Super Admin, Group Admin, Analyst, Regular Sub-account with assigned permissions.

Entry: SolarEngine - Product - Analysis - User Tag

Tenant-Level Tags:

Operation Permissions : Super Admin, Regular Sub-account with assigned permissions.

Entry: SolarEngine - Top Manu in Home Page- Asset Management - User Tag