# Create contact attributes

**Contact attributes** let you store information about individual people in your database — such as their name, email, preferences, or behavioral data.\
You can use these attributes to segment contacts, personalize campaigns and trigger automations.

### **Go to the Contact Attributes Section**

* From the main navigation, go to Marketing → **Audience** → **Contacts**
* Under 3 Dots menu, click **Contact attributes**.

<figure><img src="/files/OvEGu5Rr2eku6rNBig4f" alt=""><figcaption></figcaption></figure>

* On the Attributes tab, click on **+New Attribute**

<figure><img src="/files/ZmAwRGy4EyG8dpDwJ33J" alt=""><figcaption></figcaption></figure>

* Search for existing attributes before you create a new one to avoid duplicates. Bird creates many standard attributes already for you&#x20;
  * Display Name
  * First Name
  * Last Name
  * Gender
  * Language
  * Country Code
  * Country Name
  * City
  * Province
  * Province Name
  * Address 1
  * Address 2
  * Postal Code
  * Birthday
  * Subscription Attributes:&#x20;
    * Email Subscription
    * SMS Subscription
    * WhatsApp Subscription
    * RCS Subscription
    * Push Subscription

### Create Attribute

If you want to create your own custom attribute, click on +New Attribute and provide following details:

<figure><img src="/files/kfCQJW2OtPNllqW0rqFL" alt=""><figcaption></figcaption></figure>

* **Display Name:** This is the name which is shown in the Bird UI for users. It can be edited later
* **Description:** Add optional description which will show as a help text. It can be edited later
* **Internal Name:** This is a unique internal name for this attribute which will be auto-filled based on display name. It can only have small letters and no spaces. Once created, it cannot be edited.
* **Type:** Select the data type such as Text, Date, Number, Select options etc. Once created, type cannot be edited.
* **Editable:** Select if the attribute values can be edited manually in the UI by the users.

<figure><img src="/files/RFgYBpVu9RUtvHx4Gubn" alt=""><figcaption></figcaption></figure>

There are following data types available:

#### **Text**

In addition to the common fields, you can define if the text field has

* Can have multiple lines of text

<figure><img src="/files/OBqwNDUBKh5YSuWDCjM4" alt="" width="375"><figcaption></figcaption></figure>

For multiple lines of text, here is an example of what the input would look like if you used it for address:&#x20;

<figure><img src="/files/mRfeAUCjzdOabqaU8IF2" alt=""><figcaption></figcaption></figure>

#### **Select**

In addition to the common fields, you can define if the attribute has

* Options: UI Labels and internal names (Value)
* Has multiple values

<figure><img src="/files/qNosTjU1r6CJnQ7IJcMC" alt="" width="375"><figcaption></figcaption></figure>

#### **Number**

In addition to the common fields, you can define if text field has

* Has decimal places and how many

<figure><img src="/files/YDqTCJcED8kkR5jF6zRi" alt="" width="375"><figcaption></figcaption></figure>

#### **Date and Date & Time**

You can select based on whether your attribute will accept only date (day, month, year) or timestamp as well

<div><figure><img src="/files/ylK2pNb6LBG9OeepBZ3d" alt=""><figcaption></figcaption></figure> <figure><img src="/files/Cu8ohr7c3xA8KUsDpOXF" alt=""><figcaption></figcaption></figure></div>

#### **Toggle**

You can select whether your data type is boolean and will accept only True/False values

* You can define the default value - empty, true (on), false (off)

<figure><img src="/files/7srMD9OqC4CrznDCcnP0" alt="" width="375"><figcaption></figcaption></figure>

#### **URL**

This is generally used to capture any web links and you can select if it

* Has multiple values

<figure><img src="/files/utVkg8Xsx8rMUoEcuMXP" alt="" width="375"><figcaption></figcaption></figure>

#### **Email Address or Phone Number**

This is generally used to capture email address and phone numbers. You can define if this attribute

* Has multiple values

<figure><img src="/files/c8jDPLZd57cIIgm0jPt6" alt="" width="375"><figcaption></figcaption></figure>

#### **Tags**

This is used when there could be one or more free form text values for an attribute

<figure><img src="/files/0Jb1ap2514v67H2UxIHw" alt="" width="563"><figcaption></figcaption></figure>

### Importing attributes for bulk creation

You can also create attributes in bulk using Import option.

<figure><img src="/files/S4mJ5GZchFsbQ8RtWxQM" alt=""><figcaption></figcaption></figure>

### Add values to contact attributes

Once the attribute is created, you can add their values using following methods:

* **Manual update:** Edit a contact record directly from the UI.
* **CSV import:** Upload a file with a column that matches the attribute internal name.
* **API:** Include the attribute in the contact create/update API call.
* **Integrations:** Sync data automatically from external sources (e.g., CRM, Ads, forms).
* **Flows/Journeys:** Use rules to auto-set values based on events or other data in a flow or journey

### Managing contact attributes

* You can edit **display name** and **description** anytime. You can edit if it is editable or not.
* You can **archive** unused attributes. You cannot delete an attribute
* You cannot edit the internal name
* You can add new options to Select type attribute


---

# 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.bird.com/applications/audience/contacts/how-to/create-contact-attributes.md?ask=<question>
```

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.
