For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Tagless Data Capturing is available for iOS, Android, and React Native SDKs.

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.

Screen Tracking dashboard with tracked and unmapped views and actions
Screen Tracking separates published mappings from candidate paths

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 and User path 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.

Last updated

Was this helpful?