> 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/device-metadata.md).

# Device metadata

The Netmera SDK automatically collects metadata from your users' devices. Use these system attributes for audience targeting, behavior tracking, personalization, and analytics.

### Key advantages

Device metadata supports data-driven customer engagement. Use it to:

* **Deliver relevant content:** Adjust messaging for each user's device, operating system, and location.
* **Improve segmentation accuracy:** Create dynamic audiences using OS version, app version, device region, or language.
* **Add detail to analytics:** Break down dashboards and reports by platform, version, and manufacturer.
* **Debug targeted environments:** Identify devices and OS versions affected by crashes or other issues.

### Collected fields

<table><thead><tr><th width="179.94976806640625">Field</th><th>Description</th></tr></thead><tbody><tr><td><code>appV</code></td><td>App version (e.g., <code>4.3.3.0</code>)</td></tr><tr><td><code>mdl</code></td><td>Device model code (e.g., <code>T782H</code>)</td></tr><tr><td><code>lang</code></td><td>System language setting (<code>tr_TR</code>, <code>en_US</code>, etc.)</td></tr><tr><td><code>mnf</code></td><td>Device manufacturer (<code>TCL</code>, <code>Apple</code>, <code>Samsung</code>, etc.)</td></tr><tr><td><code>oc</code></td><td>Operator code (MCC + MNC as integer, e.g., <code>28502</code> = Operator TR)<br>Note: Deprecated in iOS 15.4+</td></tr><tr><td><code>oper</code></td><td>Mobile operator name (e.g., <code>Operator TR</code>)<br>Note: Deprecated in iOS 15.4+</td></tr><tr><td><code>osV</code></td><td>Operating system version (e.g., Android <code>11</code>, iOS <code>16.5</code>)</td></tr><tr><td><code>psV</code> (Android only)</td><td>Google Play Services version</td></tr><tr><td><code>rgn</code></td><td>Region/country code (<code>TR</code>, <code>US</code>, <code>DE</code>, etc.)</td></tr><tr><td><code>tzid</code></td><td>Time zone identifier (e.g., <code>Europe/Istanbul</code>)</td></tr></tbody></table>

#### About `oc` (operator code) and `oper` (operator name) parameters

* **iOS:** Netmera collects these fields on iOS versions 13 through 15.3. Apple deprecated access in iOS 15.4 because of privacy policy updates.
* **Android:** Netmera continues to collect these fields.

### Common use cases

Use device metadata across marketing, analytics, and development.

#### 1. Version-based targeting

Use **App Version** and **Operating System Version** to:

* Identify users with outdated versions and prompt them to upgrade.
* Run A/B tests based on OS or app-version compatibility.

#### 2. Region and language-specific campaigns

Use **Region Code** and **Device Language** to:

* Localize message content using each user's language settings.
* Exclude users in unsupported countries or regions.

#### 3. Telecom-specific analysis (Android only)

Use **Operator Code** and **Operator Name** to:

* Analyze your audience by mobile carrier.
* Correlate engagement or churn with specific telecom providers.

> **Note:** These two fields are only available on Android and iOS versions 13 through 15.3. They are deprecated on iOS 15.4 and later due to Apple’s privacy restrictions.

#### 4. Device-specific performance analysis

Use **Device Model** and **Device Manufacturer** to:

* Identify performance issues or crashes linked to specific devices.
* Adapt in-app experiences or campaign content to device capabilities.


---

# 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/device-metadata.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.