> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adrop.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Properties

> Properties are user attribute information such as age, gender, interests, and membership tier. Learn how to register and manage properties for audience targeting.

***

## What are Properties?

**Properties** are user attribute information. Any data that can distinguish users—such as age, gender, interests, or membership tier—can be a property.

Properties are collected via SDK, and targeting options are created by combining collected properties.

***

## Default Properties

Properties provided by default in Ad Control.

| Property     | Description                | Collection Method          | Data Format                              |
| ------------ | -------------------------- | -------------------------- | ---------------------------------------- |
| **Country**  | User's country information | Auto-collected             | ISO country code 2 digits (KR, US, JP)   |
| **Language** | User's language setting    | Auto-collected             | ISO language code (ko, en, ja)           |
| **Age**      | User's age                 | Requires birthday from SDK | YYYY, YYYYMM, YYYYMMDD format            |
| **Gender**   | User's gender              | Requires SDK pass          | M(Male), F(Female), O(Other), U(Unknown) |

<Note>
  Country and Language are auto-collected from device locale settings. Age and Gender must be passed directly from the SDK.
</Note>

***

## Custom Properties

<video autoPlay muted loop playsInline src="https://mintcdn.com/openrhapsody/smENmiWX3Jge7uck/videos/targeting-properties.mp4?fit=max&auto=format&n=smENmiWX3Jge7uck&q=85&s=94cb87ef138ba4f989aebfc994623ee1" data-path="videos/targeting-properties.mp4" />

You can add custom properties beyond defaults to fit your service.

### Example: Local Activity App

Assuming a local activity app collects user activity region and booking count.

| Property            | Type   | Description              | Example Values     |
| ------------------- | ------ | ------------------------ | ------------------ |
| **`region`**        | String | User's activity region   | Seoul, Busan, Jeju |
| **`booking_count`** | Number | Cumulative booking count | 0, 5, 20           |

<Warning>
  String values are case-sensitive. Enter exactly as passed from the SDK.
</Warning>

Combining these two properties allows creating various targeting options.

### Adding Custom Properties

1. Click **Targeting → Audience** in the left menu.
2. Click the **Properties** tab at the top.
3. Click the **Property Details** button.
4. Enter property name and data type.
5. Click the **Save** button.

### Property Naming Rules

* 3-64 characters using only lowercase English letters, numbers, and underscores (\_)
* Examples: `membership_level`, `asset_size`, `baby_months`

### Data Types

| Type              | Description                | Examples                       |
| ----------------- | -------------------------- | ------------------------------ |
| **String**        | Text value                 | "premium", "gold", "drama"     |
| **Number**        | Integer or decimal         | 25, 100000000, 3.5             |
| **Boolean**       | True/false                 | true, false                    |
| **Date**          | Date value                 | 2024-01-15                     |
| **String Array**  | Multiple text values       | \["drama", "action", "comedy"] |
| **Number Array**  | Multiple number values     | \[1, 2, 3]                     |
| **Boolean Array** | Multiple true/false values | \[true, false, true]           |

<Warning>
  Data type cannot be changed if a property is in use by targeting.
</Warning>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Events" icon="bolt" href="/targeting/event">
    Learn about behavior-based targeting using events
  </Card>

  <Card title="Creating Audience Targeting" icon="users" href="/targeting/audience">
    Create targeting by combining properties and events
  </Card>
</CardGroup>

***

## FAQ

<AccordionGroup>
  <Accordion title="Can I start targeting with just default properties?">
    Yes, you can start right away with default properties like Country, Language, Age, and Gender. Adding custom properties unique to your service (membership tier, purchase history, interests, etc.) later enables differentiated premium targeting versus competitors.
  </Accordion>

  <Accordion title="What is the difference between properties and events?">
    Properties are user attribute information (age, gender, membership tier, etc.), while events are user behavioral data (purchases, add to cart, etc.). Properties indicate "who the user is," and events indicate "what they did." Both can be used as conditions in audience targeting.
  </Accordion>
</AccordionGroup>