Set up the extension

This page will guide you to set up Mobile Experience Analytics Extension for Contentsquare Product Analytics.

This will supercharge the Product Analytics platform with:

  • Powerful Session Replay
  • Analysis capabilities of Mobile API Errors and Crashes

This guide assumes that you have already implemented the CSQ SDK for Product Analytics.

Enable the extension in the Product Analytics UI

Section titled Enable the extension in the Product Analytics UI
  1. In Product Analytics, navigate to Account > Manage > Replays & Heatmaps.
  1. If this is your first time setting up Session Replay, select the checkbox to accept the terms and conditions.
  2. Click Add web or mobile app to launch the setup wizard. There is one configuration per app.
  3. Select Mobile as platform.
  4. Give your app a name and choose a storage location (US or EU).
  1. Set a sampling rate for how many sessions to record.
  2. Configure replay settings:
    • App ID: enter the bundle ID of your app (for example, com.companyname.appname).
    • Quality Settings: choose the recording fidelity for Wi-Fi and Cellular connections. The default for both is Medium; keep Cellular equal to or lower than Wi-Fi.
    • User Consent: enable this if your app requires explicit opt-in before recording. See Privacy docs for the opt-in API.
  1. Click Save and Continue to finish the wizard.

Enable error and crash collection

Section titled Enable error and crash collection

Error and crash collection is managed separately from the setup wizard. Navigate to Account > Manage > Replays & Heatmaps, click Edit next to your app configuration, then scroll to the relevant section under General Settings:

  • Error Capture: toggles for API Errors and Custom Errors.
  • Crashes Capture: toggle for Crashes.

Click Save when finished.

By default the entire user interface is masked when using Session Replay. Contentsquare offers two approaches to manage masking of the UI:

  • Un-mask the UI on a per-element basis using the data masking APIs
  • Set masking to be turned off by default, then re-mask parts of the UI that might contain Personal Data using the data masking APIs

See Data masking API docs, as well as sample masked and un-masked screenshots.