> 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/tagless-data-capturing.md).

# Tagless data capturing

Tagless Data Capturing automatically collects **mobile screen views and user interactions** without requiring separate event instrumentation for every interaction. It turns technical interaction paths into **clear, business-friendly mappings** that can be used for reporting and user behavior analysis.

Use Tagless Data Capturing to understand how people move through your application, which interactions they perform, and where they continue or drop off. Development teams enable the feature and prepare the mappings, while product and marketing teams can use the resulting data to investigate user behavior.

{% hint style="info" %}
Tagless Data Capturing is available for iOS, Android, and React Native SDKs.
{% endhint %}

{% embed url="<https://youtu.be/piUgfFaMHo8?si=XXKZ3aZTYHemozUn>" %}

### What it captures

Tagless Data Capturing supports three types of captured behavior:

* **Views** show the screens people visit, such as `Login > Home > Profile`.
* **Actions** show interactions people perform, such as `Home > Search > Select Result`.
* **Values** add context to captured interactions, such as a selected option or input value.

Your team can map important technical paths to business-friendly names. For example, a path such as:

`Home > Profile > Settings` can be mapped to: **Profile Settings**

These mappings make user flows easier to understand and provide consistent terminology for product, marketing, analytics, and development teams.

<figure><img src="/spaces/X6uilbEAw42gqsudlclY/files/aVL1r4Lgw3lr1qwKfeJE" alt="Screen Tracking dashboard with tracked and unmapped views and actions"><figcaption><p>Screen Tracking separates published mappings from candidate paths</p></figcaption></figure>

### How it works

1. Developers enable collection in Screen Tracking.
2. Test-device activity produces candidate view and action paths.
3. Your team maps important paths and publishes them.
4. User Path shows how people move through published interactions.

The [**Screen tracking**](/netmera-user-guide/panel-settings/settings/app-configuration/screen-tracking.md) and [**User path**](/netmera-user-guide/reports-and-analytics/analytics/user-and-audience/user-path.md) subpages contain each workflow.

### Business use cases

Use Tagless Data Capturing to answer questions such as:

* Which screens do people visit before checkout?
* Which interactions commonly lead to a purchase or exit?
* Does behavior differ by audience, platform, or app version?

For example, compare the shopping journey for new and returning customers. You can identify where people leave the flow, then investigate the experience or target a relevant campaign.

### When to use manual events

Use Tagless Data Capturing for navigation and common interface interactions. Use manual events when you need business-specific actions, custom attributes, or data outside captured paths.

For example, use a manual event to record membership status or a transaction amount. Use Tagless Data Capturing to understand the route that led to that action.


---

# 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/tagless-data-capturing.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.