On this page
Configure collection around the journeys you need to understand. Separate the settings in your app from the settings in your CUX project so you know where to make a change.
Set up collection in your app
Your app controls SDK initialization, consent handling, navigation integration and the sensitive content you mask. Use the API for your platform:
| Platform | Configuration guide |
|---|---|
| Android 1.2.0 | Initialize the SDK and control collection |
| iOS 1.1.11 | Initialize the SDK and control collection |
| React Native 1.0.22 | Initialize the SDK and control collection |
| Flutter 0.0.27 | Initialize the SDK and control collection |
Do not copy initialization options between platforms. An option with a similar purpose may have a different name or may not exist in your integration.
Check screenshot configuration
Screenshot capture also depends on the configuration your SDK receives from CUX. Capture frequency and image settings affect how much visual context is available and how much data your app sends.
If you need to change screenshot frequency, image scale or compression, ask CUX which controls are available for your project and SDK version. Do not add an undocumented initialization parameter or assume that a setting is available in the panel.
Test any change on representative screens and network conditions. Compare image readability, missing visual context and the app's behavior during navigation and scrolling.
Keep screenshots and collection separate
Masking a field changes what is visible in screenshots. It does not stop custom events or remove values your code sends as user properties.
On iOS and React Native, screenshot pause/resume controls are separate from stopping collection. Use the platform guide to choose the right control. Do not assume those methods exist on native Android 1.2.0 or Flutter 0.0.27.
Enable optional Android features deliberately
Preview stitching is off by default and requires compatible CUX processing. WebView integration requires a compatible web collector and a configured pair of projects.
Neither feature is enabled just by installing Android 1.2.0.
Verify a configuration change
- Test the same journey before and after the change.
- Check screens, interactions and screenshots in CUX.
- Confirm that consent choices still control collection as intended.
- Inspect sensitive screens and fields in the resulting data.
- Check the app on a slower device and connection before releasing it.
If the result differs from your expectation, record the SDK version, device, app build and reproduction steps. For native Android, use Troubleshoot your integration.