# Setting Custom Data
### User Attributes
You can assign custom attributes to your users and they will show up on your Luciq dashboard with each report. These attributes can later be used to filter reports in your dashboard.
To add a new user attribute use the following method.
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.setUserAttribute("Age", "18")
Luciq.setUserAttribute("Logged", "True")
```
{% endcode %}
{% endtab %}
{% endtabs %}
{% hint style="info" %}
Disclaimers:
* Each Bug or Crash Report could have up to 100 user attributes only.
* The character limit for the Keys and Values is 90 characters each.
{% endhint %}
You can also retrieve the current value of a certain user attribute, or retrieve all user attributes.
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
// Getting specific attribute
Luciq.getUserAttribute("Logged in")
// Getting all attributes
Luciq.getAllUserAttributes();
```
{% endcode %}
{% endtab %}
{% endtabs %}
Or remove the current value of a certain user attribute
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.removeUserAttribute("Completed IAP")
```
{% endcode %}
{% endtab %}
{% endtabs %}
### User Events
You can log custom user events throughout your application. Custom events are automatically included with each report.
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.logUserEvent("OnFeedbackButtonClicked")
```
{% endcode %}
{% endtab %}
{% endtabs %}
### Tags
You can add custom tags to your bug and crash reports. These tags can later be used to filter reports or set custom rules from your dashboard.
The example below demonstrates how to add tags to a report.
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.addTags("Tag 1", "Tag 2")
```
{% endcode %}
{% endtab %}
{% endtabs %}
{% hint style="info" %}
#### Adding tags before sending reports
Sometimes it's useful to be able to add a tag to a bug report before it's been sent. In these cases, the perfect solution would be use the event handlers of the bug reporting class.
{% endhint %}
You can also get all the currently set tags as follows.
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.getTags()
```
{% endcode %}
{% endtab %}
{% endtabs %}
Last, you can reset all the tags.
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.resetTags()
```
{% endcode %}
{% endtab %}
{% endtabs %}
#### Managing Tags
If you'd like to remove a particular tag from your dashboard to prevent it from appearing again when entering a new tag manually, you can do so by navigating to the tags page under the settings options and remove the tag. You can also edit and rename the tag.
***
### Feature Flags
In certain scenarios, you might find that you're rolling out different experiments to different users, where your user base would see different features depending on what's enabled for them. In scenarios such as these, you'll want to keep track of the enabled experiments for each user and even filter by them.
**Notes:**
1. **Feature Flag Naming**: Each feature flag name should not exceed 70 characters and each variant name should not exceed 70 characters. Otherwise, they will get ignored by the SDK. Note that feature flag names are case-insensitive.
2. **Feature Flag Persistence**: Feature flag persist beyond individual sessions and are not automatically removed at the end of a session. Additionally, calling the logOut function does not impact the existence of the feature flag. The feature flag is only removed when you call the removing method or the clearing method.
3. The amount of feature flags sent in a session is 200 with maximum of 1 variant per a multivariate feature flag. For example, a feature flag that has 3 variants sent within 1 session will only be sent to our backend as the last variant, and not all 3.
For more information on feature flags, visit Feature Flags.
#### Adding Feature Flags
#### Boolean Feature Flags - Example Usage
Below is an example of where in your code you would use feature flag. In this example, you are experimenting with feature logic that controls whether or not the user has a Dark Mode toggle available.
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.addFeatureFlag(LuciqFeatureFlag("dark_mode"))
```
{% endcode %}
{% endtab %}
{% endtabs %}
#### Multivariant Feature Flags - Example Usage
Below is an example of where in your code you would use feature flag with multiple variants. In this example, you are experimenting with feature logic that controls multiple versions of a specific feature.
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.addFeatureFlag(LuciqFeatureFlag("checkout_v2", "variant_b"))
```
{% endcode %}
{% endtab %}
{% endtabs %}
#### Removing Feature Flags
If your feature flag is concluded or you would like to simply remove it, you can use this method:
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.removeFeatureFLag("dark_mode"); // remove single key
Luciq.removeFeatureFlag(listOf("dark_mode", "checkout_v2")) // remove several at once
```
{% endcode %}
{% endtab %}
{% endtabs %}
#### Clearing Feature Flags
You can use the below method to clear all the Feature Flags from your reports:
{% tabs %}
{% tab title="Kotlin" %}
{% code overflow="wrap" %}
```kotlin
Luciq.removeAllFeatureFlags()
```
{% endcode %}
{% endtab %}
{% endtabs %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.luciq.ai/android/set-up-luciq-for-android/identify-users/setting-custom-data.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.