Screen tracking

Path: Settings > App Configuration > Screen Tracking

Screen Tracking automatically collects mobile screen views and user interactions. It supports Tagless Data Capture without separate event instrumentation.

Use it to map technical paths to clear business interactions. Then analyze those views and actions in User Path.

Screen Tracking is available for iOS, Android, and React Native SDKs. Flutter isn't supported.

Why use Screen Tracking

Use Screen Tracking when you want to understand navigation and interface behavior without defining every interaction in app code.

It helps you:

• discover paths users take through the app,

• group equivalent iOS and Android behavior,

• use mapped views and actions in User Path analysis.

Before you start

Make sure that:

• Your app includes the Netmera SDK.

• You can access Settings > App Configuration > Screen Tracking.

• You have a registered test device.

• iOS URL Scheme and Android Package Name are configured in Developers > App Info.

Screen Tracking dashboard

Open Settings > App Configuration > Screen Tracking > Views / Actions.

The dashboard separates published mappings from candidate paths:

• Track Views and Track Actions contain mapped, published interactions.

• Unmapped Views and Unmapped Actions contain test-device paths awaiting a mapping.

Screen Tracking dashboard

Configure Screen Tracking

Step 1: Enable collection

Open Settings > App Configuration > Screen Tracking > Track Views, Track Actions, or Collect Values.

Enable the collection types you need

Enable Track Views, Track Actions, and Collect Values on their respective pages.

Track Views

Enables the collection of full-screen transitions such as Home Page, Product Page, Cart, etc. This helps you understand which pages users are navigating to.

Track Actions

Captures user interactions with the interface, such as taps, clicks, or selections on specific elements. Useful for analyzing feature usage and engagement.

Collect Values

Extends action tracking by capturing the specific value of the item clicked or interacted with.

For example, if a user taps a product titled "Blue Sneakers" at the end of a path like /category/shoes, this toggle ensures that "Blue Sneakers" is included in the data payload.

This allows you to not only track which action was triggered but also what the user selected or interacted with.

---

Step 2: Add test devices

Open Settings > App Configuration > Test Devices > Invite Tester or Add Tester.

To begin collecting screen views and user interaction events, you must first register test devices. These devices are used to simulate app usage in a controlled environment so that Netmera can detect and log potential screen and action events for mapping. Refer to Test devices for further information.

Option 1: Inviting Testers via Email

1. Navigate to the left menu of the panel and select "Settings."

2. Click on "Test Devices" to access the test device management screen.

3. Locate the "Invite Tester" button and click on it.

4. Enter your email address in the provided field to receive the invitation link.

5. Check your email for the received invitation link.

6. On the device you want to add as a test device, click on the invitation link from the email.

7. The link will redirect you to the mobile application and automatically add the device as a test device.

Option 2: Adding Test Devices with their External ID

1. In the "Settings -> Test Devices" screen, find and click on the "Add Tester" button.

2. Enter your external ID in the provided field.

3. The system will list available devices for you to add as test devices.

4. Click on the desired device from the list to add it as a test device with a single click.

Option 3: Adding a Tester with User Details

1. Navigate to the left menu of the panel and select "Targeting."

2. Click on "People" to access the people search screen. Then, click on "Find Person".

3. Write their External ID or email and click "Find".

4. When you see your user's results, click on "User ID" which is shown in color green.

5. You will see a warning about action loggings saying "You are accessing user private data, your action will be logged." click Yes.

6. On top of the page, you will see three options. Click on "Assign as a Tester" > "Get Devices."

7. You are going to see a list of all the platforms you may use this user as a tester. Select your Platform (sms, email, etc.) and choose "Add Tester."

If you haven't set an External ID for your user please follow these steps:

updateUser() methods to set xid:

To set xid, you can use the updateUser() method with the userId. For detailed information, refer to our developer documentation with the following links.

• iOS User Documentation

• Android User Documentation

Precondition: Set your iOS URL Schema and Android Package Name under Developers > App Info.

---

Step 3: Generate candidate paths

Once your test device is registered, interact with your application to simulate user flows. Netmera Tagless Data Capture will automatically generate candidate event paths based on your actions—no manual coding required.

• Views Example: "Home" → "Product List" → "Product Detail" → "Cart" This captures the sequential screen transitions as a user navigates through your app.

• Actions Example: "Tap Search" → "Select Filter" → "Tap Add to Favorites" These represent individual user interactions with buttons or interactive elements.

• Values Example: "Tap Product: Running Shoes" → "Tap Color Option: Red" → "Tap Size: 42" The Collect Values feature appends contextual details—such as the name, label, or value of the item clicked—at the end of the action path.

These automatically generated candidate paths can later be reviewed, named, and published for consistent tracking across your application.

---

Step 4: Create and publish mappings

1. Navigate to unmapped paths

Open Unmapped Views or Unmapped Actions under the Tagless Data Collection section.

2. Create a mapping

Select Create New to open the mapping editor for the selected view or action.

3. Assign a Screen Name

Enter a meaningful and consistent name that reflects the purpose of the screen, such as ProductDetail or OnboardingStep1.

4. Choose Tracking Option

Use the Track toggle/button to decide whether this mapping should be actively tracked. This allows you to save mappings without enabling them immediately if needed.

5. Match Android and iOS paths

Netmera allows you to group equivalent screen views or actions across platforms into a single mapping. Use the Add button in the Mappings table to attach a corresponding path from the other platform. For example, match the Android product/detail screen with the iOS productDetailsView. This ensures consistency in reporting and simplifies cross-platform analytics.

6. Finalize and save

Once both platforms, if applicable, are matched, select the green Add button to save your mapping.

7. Publish the changes

After saving, return to the Views / Actions dashboard and select Publish.

Publishing is required to activate the mappings—otherwise, they remain in draft and will not be applied.

How to Match Corresponding Mappings Between Android and iOS

To unify event tracking across platforms, Netmera allows you to combine Android and iOS paths into a single mapping entry. This helps reduce duplication and makes reports easier to interpret.

Steps to match paths:

1. In the Mappings table of the mapping creation screen, locate the existing path for one platform (e.g., Android).

2. Find the corresponding path from the other platform listed under Unmapped Views/Actions.

3. Click the “Add” button next to the correct platform entry.

4. The selected path will be added under the same mapping, allowing you to track Android and iOS screens/actions as one.

Example: You might have the Android path /product/detail and the iOS path productDetailScreen. Matching both under a single mapping called ProductDetail will allow you to see unified analytics for that screen.

Analyze mapped behavior

Path: Analytics > User & Audience > User Path

User Path helps you inspect flow efficiency, exits, and repeated actions from published views and actions.

Filter Options:

• Segment: Analyze specific user groups (e.g., VIPs, new users)

• Device: Filter by operating system or device version

• Filter: Choose a specific screen or action

• Direction: See what precedes or follows a selected event

• Date Range: Observe behavior trends over time

Analyze published Screen Tracking data in User Path

Tagless Data Capture event types

Event	Description	Notes
Show View Test Event	Fired when a screen is shown on test devices only	Not visible in production
Show View Event	Triggered when a mapped screen is viewed	Live tracking for analytics
View Action Test Event	Triggered when an action is taken on a test device	Used during test flow creation
View Action Event	Triggered when a mapped interaction occurs	Visible in analytics and segmentation

Troubleshoot Screen Tracking

Issue	Solution
Can’t See Track Views/Actions Pages	Ask your Success Manager to enable permissions
No Data Collected from Test Device	Confirm that the device is registered and actively used
Mapping Doesn’t Appear in Dashboard	Ensure you clicked “Add” after matching and then “Publish”
User Path Shows No Events	Check if test events were generated and mapped properly
Session Expiry Issues	Update Session Expiration Interval in Developers > App Info