This checklist will help with the implementation of the Contentsquare SDK in your mobile app. While a thorough QA will be conducted by Contentsquare’s Implementation team, completing the below checks are crucial to ensuring a faster and successful implementation.
1. In-app features
Verify the CS in-app features are functioning properly by scanning the QR code and confirming its availability.
2. Privacy compliance
Confirm that data collection occurs only when users opt-in (accept necessary cookies) and is blocked when users opt-out (reject all necessary cookies).
Test this by accepting and rejecting cookies: (1) at app startup; and (2) within app settings.
3. Screen tracking
Ensure screens are tracked immediately after opt-in confirmation. You can validate them using a terminal on Mac or Android Studio logs.
Screens should fire when:
- A screen appears.
- A modal/pop-up is opened/closed, returning the user to the screen.
- The app is brought to the foreground after being hidden/minimized.
4. Tracking custom variables (cVars)
Navigate through the app and confirm in the logs that required cVars are being sent correctly.
5. Tracking transactions
Perform a transaction and check console logs for:
- Transaction ID
- Value
- Currency
6. Tracking dynamic variables (dVars)
Verify that all required dynamic variables (dVars) are being sent as users navigate the app by checking the logs.
7. Tracking WebViews
For screens containing WebView elements, use the console logs to confirm that CS screenviews are properly triggered when users reach these screens.
8. Session Replay PII masking
If session replay is enabled, verify that no personal information (PII) is collected. Follow these steps:
- Visit screens displaying sensitive user data, such as:
- Personal account details
- Checkout flows
- Address dropdown suggestions
- Support chat
- Extract your session replay using the in-app feature (long-press the CS button and select 'Get replay link').
- Review the session replay to ensure all sensitive data is masked appropriately.