Tagging Screens

Good screen names turn raw replays into actionable heat‑maps, screen analytics, conversion funnels and journey charts.
This guide walks you through reviewing the automatic tags first, deciding when (and how) to add manual tags, and finally verifying that every screen shows up with a meaningful duration.

Automatic Screen Tagging - The Recommended, Simple Approach

For Android, UXCam's SDK automatically tags screens (i.e., activities), and this is the recommended default behaviour. Automatic tagging means that each activity your user navigates to is recorded automatically, without requiring you to manually intervene. This gives you the advantage of capturing user activity with minimal integration effort.

1. Record one or multiple sessions in your debug build where you are navigating all screens of your app.
2. Open any replay in the UXCam Dashboard and review the screen list on the right.
3. For each entry, ask:

If everything looks good – simply rename screens in Dashboard → Screens (e.g. change MainActivity → Home) and you’re done. No code required.

How to Enable or Disable Automatic Tagging?

It will always be enabled by default, but you can disable this from your SDK configuration options as such:

val config = UXConfig.Builder(BuildConfig.YOUR_UXCAM_KEY)
    .enableAutomaticScreenNameTagging(false) // TRUE BY DEFAULT
    .build()
UXCam.startWithConfiguration(config)

UXConfig config = new UXConfig.Builder(BuildConfig.YOUR_UXCAM_KEY)
    .enableAutomaticScreenNameTagging(false) // TRUE BY DEFAULT
    .build()
UXCam.startWithConfiguration(config)

Manual Tagging - When Do I Need It?

Example: Tagging an Activity Manually

To tag a screen in an activity, use the following code in the onCreate() method of your activity:

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
  
    UXCam.tagScreenName("Main Page"); // Manually tag this activity with a screen name.
}

Example: Tagging a Fragment Manually

Similarly, to tag a fragment, place the code in the onResume() method of the fragment:

@Override
public void onResume() {
    super.onResume();
    UXCam.tagScreenName("Fragment Name"); // Manually tag this fragment with a screen name.
}

How to Tag WebViews

WebViews can be a unique challenge when it comes to screen tagging, as they often contain dynamic content. To properly tag your WebView screens, you can follow our detailed guide that walks you through the best practices and methods for effective WebView tagging.

For more information, click the button below:

Tagging Webview docs link TODO

Verify Your Tags

So you've decided to manually tag some or all your screens, making sure this is properly set up is a fundamental part in ensuring heat-maps, funnels and user journey analytics is giving you full insights, so it is extremely important to verify everything works well before moving on:

1. In your debug environment, run the app and visit all the manually tagged screens, then background the app.

2. Once the session uploads, check:

   • Each screen appears exactly once, according to the user's navigation, with duration > 0 s.
   • No “Unknown” or class‑name (if fully manual) screens remain.
   • Names match your analytics language.

If something is off, look for duplicate tag calls or a missing route handler.

Troubleshooting cheat‑sheet

Edge‑cases to watch for

Next Steps:

You've properly tagged screens and are ready to move on! Let's review some next steps you should take.