Title: FAQ
Locale: en
URL: https://sensorswave.com/en/docs/user-operation/faq/
Description: Frequently asked questions about the Users module
This guide covers frequently asked questions and answers for the Users module.

## General Questions

### What features are included in the Users module?

The Users module includes three core features:

1. **User List**: View and filter user lists with multiple access entry points
2. **User Profile**: View an individual user's complete profile and Activity
3. **Cohorts**: Create and manage user groups, supporting Static and Dynamic Cohorts

### What permissions are required to use the Users module?

| Feature | Required Permission |
|---------|-------------------|
| View user list | Users - Consumer |
| View User Profile | Users - Consumer |
| Create cohorts | Users - Analyst |
| Edit/Delete cohorts | Cohort creator or Manager |
| Export user data | Data export permission |

### What is the data latency for the Users module?

- User Property data: 1–5 minutes
- Event behavior data: 1–5 minutes
- Dynamic Cohort computation: Real-time computation, may take a few seconds to tens of seconds
- Data latency is affected by data volume and system load; it may be slightly longer during peak periods

## User List

### How do I quickly find a specific user?

In User List, you can search for users in the following ways:

1. **Search by User ID**: Enter the full or partial user ID in the search box
2. **Filter by User Properties**: Add property filter conditions such as phone number, email, etc.
3. **Drill down from analytics models**: Drill down to the user list from Segmentation and other models

### What information can be displayed in the user list?

Default display: User ID, Last active time, First Seen, Total event count

Customizable display:
- System properties: Registration time, device type, operating system, etc.
- User Properties: Membership level, cumulative spending, region, etc.
- Statistical Metrics: Cumulative order count, active days, etc.

### What is the maximum export limit for user lists?

- Maximum per export: 100,000 records
- When exceeding the limit, narrow the filter scope or export in batches
- Export formats supported: CSV and Excel

### Why can't I see users after drilling down from an analytics model?

Possible reasons:

1. **Unsupported aggregation method**: Only user-related aggregations like "Unique Users" support drill-down
2. **Empty data**: There are genuinely no users matching the conditions for that time period
3. **Insufficient permissions**: Missing access to the Users module
4. **Data latency**: Data has not yet synced — please try again later

## User Profile

### How far back can I view behavior data in User Profile?

The retention period for behavior data depends on the Project configuration. The default is 365 days. Data beyond the retention period cannot be viewed.

### Why are some Event Properties incomplete?

Possible reasons:

1. **Not reported during instrumentation**: The event did not include the corresponding property when triggered
2. **Property deleted**: The property metadata was deleted in Data Center
3. **Property type mismatch**: The property value does not match the defined type
4. **Data masking**: Sensitive properties were masked according to security policies

### How do I view a user's Feature Gate and Experiment status?

On the User Profile page:

1. Switch to the **Associated Information** area
2. View the **Feature Gates** tab to see all Feature Gate states for the user
3. View the **Experiment Participation** tab to see the user's Experiments and group assignments

> Note: Feature Gate and Experiment statuses show results from the most recent check and may be cached.

### Why is there missing data in the user's Activity?

Possible reasons:

1. **Time range limitation**: The event does not exist within the currently filtered time range
2. **Event filter**: An event filter was applied, filtering out certain events
3. **Missing instrumentation**: The operation was not correctly instrumented for reporting
4. **Data latency**: The latest event data has not yet synced
5. **Data retention period**: Data beyond the retention period has been cleaned up

## Cohorts

### What is the difference between Static and Dynamic Cohorts?

| Dimension | Static Cohort | Dynamic Cohort |
|-----------|--------------|----------------|
| **User list** | Fixed | Computed in real-time |
| **Creation method** | Filter and save / Upload | Configure rules |
| **Update mechanism** | No automatic updates | Automatic updates |
| **Use cases** | Snapshot analysis, external imports | Continuous tracking, automated operations |

### Why does the user count of a Dynamic Cohort change?

Dynamic Cohorts are computed in real-time based on rules. Reasons for changes in user count:

1. **New users meet the criteria**: Newly registered users or users with new behaviors satisfy the rules
2. **Users no longer meet the criteria**: Existing users' properties or behaviors have changed
3. **Rules were modified**: The cohort rules were updated

If you need a fixed user list, use a Static Cohort.

### What is the maximum number of conditions for cohort rules?

- A single cohort supports a maximum of 20 rule conditions
- Nesting supports a maximum of 2 levels
- Behavior filter time ranges can be up to 365 days

### Can cohorts reference each other?

Yes. In cohort rules, you can use the "Cohort" rule type to select and reference existing cohorts.

**Supported operations**:
- Belongs to a cohort
- Does not belong to a cohort
- Combine multiple cohorts (intersection, union, difference)

**Limitations**:
- Circular references are not allowed (A references B, and B references A)
- Maximum of 10 levels of nested references

### How do I create a cohort based on user behavior sequence conditions?

Currently, cohort rules support filtering based on user behavioral metrics (e.g., "Purchase count in the past 7 days > 3"), but do not directly support complex behavior sequence conditions (e.g., "Browsed then purchased but did not pay").

**Workaround**:

1. Configure the conversion flow in Funnel Analysis and drill down to dropped-off users
2. Save the dropped-off users as a Static Cohort
3. Periodically update the cohort

### Will deleting a cohort affect analyses that use it?

Before deleting a cohort, the system checks reference relationships:

- If the cohort is referenced elsewhere (analyses, Feature Gates, Experiments, other cohorts), you must remove the references first
- The cohort can only be deleted after references are removed
- After deletion, historical analysis results using the cohort are not affected, but they cannot be recalculated

## Performance and Limitations

### What should I do if User List queries are slow?

Optimization tips:

1. **Reduce filter conditions**: Start with a few conditions to locate, then refine gradually
2. **Narrow the time range**: Use shorter time ranges for behavior filters
3. **Use simple conditions**: Property filters are faster than behavior filters
4. **Query in batches**: Split large-scope queries into multiple smaller queries

### What should I do if Dynamic Cohort computation times out?

Optimization tips:

1. **Simplify rules**: Reduce the number of conditions and avoid complex nesting
2. **Reduce behavior conditions**: Behavior filters have higher computation costs
3. **Shorten time ranges**: Shorter time ranges for behavior filters are faster
4. **Split cohorts**: Split complex cohorts into multiple simpler ones

### What should I do if user list export is slow?

1. **Reduce export volume**: Add filter conditions to narrow the export scope
2. **Reduce export columns**: Only select necessary fields
3. **Export in batches**: Export large datasets in multiple batches
4. **Export during off-peak hours**: Avoid system peak periods

## Troubleshooting

### User List shows "No Data"

Troubleshooting steps:

1. **Check filter conditions**: Are the conditions too restrictive?
2. **Check time range**: Was a time period with no data selected?
3. **Check data ingestion**: Is the SDK correctly reporting data?
4. **Check permissions**: Do you have permission to view data in this Project?

### Cohort save failed

Troubleshooting steps:

1. **Check rule completeness**: Are all conditions fully configured?
2. **Check circular references**: Do the cohort references form a cycle?
3. **Check naming**: Does the Cohort Name contain special characters?
4. **Check permissions**: Do you have permission to create cohorts?

### User Profile fails to load

Troubleshooting steps:

1. **Check if user exists**: Is the user ID correct?
2. **Check data permissions**: Do you have permission to view this user's data?
3. **Check network connection**: Is the network functioning normally?
4. **Refresh and retry**: Clear cache and reload

### Filter conditions are lost after drilling down from analytics to User List

This usually happens because the drill-down conditions are too complex or contain unsupported conditions. Recommendations:

1. **Simplify analysis conditions**: Use simpler filters and Group By dimensions
2. **Configure manually**: Manually configure equivalent conditions in User List
3. **Save as cohort**: Save as a cohort directly in the analytics model, then view users from the cohort

## More Help

If the above content did not resolve your issue, you can:

1. Review the [Users Overview](overview.mdx) for basic concepts
2. Review [Cohort Rules](cohort-rules.mdx) for rule configuration
3. Contact technical support for assistance

---

**Last updated**: January 19, 2026