Note: Currently, Diagnose for mobile apps is only available for iOS devices.
Diagnose for mobile apps extends the product's scanning capabilities to your mobile devices to help your organization identify vendors, ensure compliance, and assist in updating your documentation and data maps.
Pre-requisites
The following information must be retrieved from the Sourcepoint system and team in order to successfully install and utilize the Diagnose SDK:
| Pre-requisite | Description |
| Property Name | Name of the app property added or imported into your Diagnose account. Value can be retrieved by visiting the App > Properties page. |
| Property ID | ID assigned to the app property added or imported into your Diagnose account. Value can be retrieved by visiting the App > Properties page. |
| Account ID | Associates the property with your organization's Sourcepoint account. Value can be retrieved by contacting your Sourcepoint Account Manager or via the My Account page. |
| API Key | Contact your Account Manager to retrieve the API key for your organization. |
Install Diagnose iOS SDK
In order to implement Diagnose for mobile apps on your property, your organization will need to integrate the Diagnose SDK into you property. In order to successfully integrate the SDK you will need to have the pre-requisite information from the section above. Click below for more information:
Test app or environment
The Diagnose SDK does not need to be pushed to a production app environment in order to capture network calls. If your organization has access to a debug or pre-production app environment and this contains all of your organization's production SDKs, you can implement the Diagnose SDK there to avoid going through the App Store review process during testing.
If your organization implements the Diagnose SDK in a test environment, you will need to mimic an end-user journey to send data to our system. Depending on where you are testing from, you may need to VPN to a region where you would like to collect data before running through the app.
The end-user journey should include accepting any CMPs or consent messages and navigating through a wide range of areas within the app itself in order to trigger as many third party SDKs or technologies as possible. We also recommend doing this every day for a week in order to capture technology which might not trigger on other days.
Note: Implementing the Diagnose SDK in a test environment which is not as active as a production app will mean proactively pushing data to Sourcepoint by mimicking an end-users journey as often as possible from multiple regions. Please reach out to your Account Manager if you have any questions.
App metrics
Once the Diagnose iOS SDK is successfully installed on your app property, Sourcepoint will sample a portion of real end-user traffic and track network calls (accept and reject button events) to produce the following metrics in the Diagnose portal.
| App metric | Description |
| Vendors triggered prior to consent | Designed for EEA scans and is the number of vendors that were observed on the properties before an end-user made a consent choice via your CMP in a given periodization. |
| Vendors after opt out | Designed for U.S. Privacy scans and is the number of vendors firing after an opt out from the sharing and/or selling of their personal information on the selected properties for the selected date and U.S. States. |
| Vendors after reject all | Designed for EEA scans are is the number of vendors that were observed firing after a Reject All action was taken by the end-user. |
| All vendors found | Designed for scans in all regions and reveals all the vendors observed on the properties. |
Comments
0 comments