> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/customer-data/about-customer-data.md).

# About customer data

Netmera provides **Customer Data** as a module for capturing, unifying, and using information about users.

Customer Data acts as a **data layer** that connects identity, behavior, and consent. This data is used by campaigns, journeys, and automation within Netmera.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Frec8cSdsWMU1AqAdS0xX%2Fimage.png?alt=media&#x26;token=e276143f-729b-498f-95c0-5a2cc0408138" alt="" width="563"><figcaption></figcaption></figure>

### Explore customer data<br>

<table data-view="cards"><thead><tr><th>Title</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td>Profile attributes</td><td><a href="/pages/OSXMrm4Xqj1ojrLAcEVy">/pages/OSXMrm4Xqj1ojrLAcEVy</a></td></tr><tr><td>Device metadata</td><td></td></tr><tr><td>Events</td><td><a href="/pages/kEYahvKEL1aViDqO3fua">/pages/kEYahvKEL1aViDqO3fua</a></td></tr><tr><td>Granular consent management</td><td></td></tr><tr><td>Tagless data capture</td><td></td></tr></tbody></table>

### Profile attributes

Profile Attributes are structured fields that describe each user. You can store anything from basic contact info to custom traits like membership level, favorite category, or device type.

* Create custom attributes tailored to your business
* Auto-update via SDKs, APIs, or contact uploads
* Use in segmentation, personalization, and journey triggers

### Device metadata

Netmera captures device metadata to support engagement. With this data, you can:

* **Deliver tailored content** by adapting messages to device, OS, and location.
* **Segment with precision** using attributes like app version, region, or language.
* **Gain deeper insights** with analytics by platform, version, and manufacturer.
* **Troubleshoot faster** by identifying issues across specific devices or OS versions.

### Events

Events capture user actions like button clicks, logins, purchases, or onboarding steps. These signals are used for behavioral targeting and automation logic across Netmera.

* Built-in and custom event tracking
* Parameter support for richer data
* Visualize user actions in Event Insight

### Tagless data capture

Tagless Data Capture gathers behavioral data from your website or app automatically, reducing the need for manual tagging and code.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FFG59lNm0nHRwWhSUHYkE%2Fimage.png?alt=media&#x26;token=0d01f459-2ce3-4ab9-8ca6-0efab49d50ea" alt="" width="375"><figcaption></figcaption></figure>

### Why customer data powers the whole platform

Customer Data is a shared source of information for Netmera's engagement features.

Every attribute, event, and permission feeds directly into Netmera’s:

* Campaign targeting
* Audience segmentation
* Journey triggers
* Personalization logic
* Message eligibility filters
* and advanced analytics

Customer Data provides the starting point for engagement as well as a source for reporting and analysis.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://user.netmera.com/netmera-user-guide/customer-data/about-customer-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
