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 approach

The UXCam iOS SDK automatically tags most screens (i.e., UIViewControllers or top‑level SwiftUI scenes). You can override or extend this behaviour where needed.

For iOS, UXCam automatically tags view controllers the moment they appear. This is the default and recommended workflow because it captures user journeys with zero extra code.

Review the default names

1. Record one or more sessions in your Debug build while you navigate every main screen.
2. Open any replay in the Dashboard → Session view and focus on the screen list at the right‑hand side.
3. For each entry, ask:

If everything looks good – simply rename screens in Dashboard → Screens (e.g. change SettingsViewController → Settings) and you’re done. No code required.
Names changed in the dashboard auto‑apply to future sessions as well.

Enable or disable automatic tagging

Only turn it off if you see duplicate / meaningless names in your timeline and you are ready to maintain manual tags.

var config = UXCamConfiguration(appKey: "YOUR-APP-KEY")
config.enableAutomaticScreenNameTagging = false // TRUE by default
UXCam.start(with: config)

Manual Tagging — when you need it

Automatic and manual tagging can co‑exist. Leave auto‑tagging ON and call tagScreenName() only for the edge‑cases listed below.

Example A · Tagging a View Controller

Tag once per navigation event to avoid 0 s duplicates.

class CheckoutVC: UIViewController {
    override func viewWillAppear(_ animated: Bool) {
        super.viewWillAppear(animated)
        UXCam.tagScreenName("Checkout Screen")
    }
}

Example B · Tagging a SwiftUI View

struct OrderSummaryView: View {
    var body: some View {
        VStack {
            // …
        }
        .onAppear {
            UXCamCore.tagScreenName("Order Summary")
        }
    }
}

(Prefer .onAppear over onChange(of:navigationPath) so the tag matches the moment the view becomes visible.)

 Tagging WebViews

WebViews contain dynamic content that rarely maps 1‑to‑1 to native screens. Use the JS ↔ native bridge to tag logical pages whenever the URL (or in‑page route) changes.

//  Inject into your WebView JS
window.webkit.messageHandlers.uxcam.postMessage({
  type: 'tagScreen',
  name: 'Pricing Page'
});

//  In your WKScriptMessageHandler delegate
if message.name == "uxcam", let dict = message.body as? [String: String],
   dict["type"] == "tagScreen" {
    UXCam.tagScreenName(dict["name"] ?? "WebView")
}

For a full walk‑through—including regex URL matching—see WebView Tagging →.

Verify your tags

1. In Debug, navigate through every manually tagged screen; then background the app.
2. Once the session uploads, confirm:
   • Each screen appears exactly once with duration > 0 s.
   • No “Unknown” or class‑name entries remain.
   • Names match analytics terminology.
3. Fix any issues by removing duplicate calls or adding a missing tag handler.

A solid screen‑naming strategy makes PII masking and heat‑map analysis far easier later on.

Troubleshooting cheat‑sheet

6 · Edge‑cases to watch for

Next Steps ➡️

You're on a roll! You've now set up some of the most important features from UXCam to get full insights already, but let's dive next into protecting sensitive information.