App Store Identifier for Advertisers (IDFA) Explanation
The SDK does not actively obtain IDFA. If you import the AdSupport library, the app needs to check the content in the red box below when submitting for review:
Advertise within the App
If you integrate advertising in the app, you need to check this item.
Attribute App Installation to Previously Delivered Specific Ads
Track installations from ads.
Attribute Actions Occurring in the App to Previously Delivered Ads
Track subsequent actions of users from ads.
"Limit Ad Tracking" Setting in iOS
This item determines whether your app uses IDFA. As long as you choose to collect IDFA, this item needs to be checked.
App Store Privacy Issues
Apple updated the privacy policy in iOS 14.3 and requires app updates or submissions to include a privacy report. If the app integrates the Sensors Analytics SDK, how should it be filled out?
By default, only select "Device ID". If you enable the full-track feature, continue to select "Product Interaction". If you use user association, that is, call the -login: interface, you also need to check "User ID", as shown in Fig 1:
Fig 1
After storage, a series of collection type panels will be generated on the app's privacy page based on our selection. Click the corresponding panel to continue with detailed selection.
User ID
The SDK will collect the user id for the analysis function when calling the -login: interface, so select "Analysis" here, as shown in Figure 2:
Figure 2
After checking, click Next to select whether the collected user id is associated with the user identity, which is checked according to the specific business. For details, you can refer to Apple's definition of whether the collected user ID is associated, as shown in Figure 3:
- Remove direct identifiers (such as email addresses or names) before collecting data
- The data is processed to disconnect from the real identity and prevent re-association
- In addition, in order not to associate the data with a specific user identity, you must avoid certain activities after collecting the data:
- You must not attempt to associate the data again with the user identity
- You must not bind data to other data sets that associate the data with the identity of the user
Please note: "Personal Information" and "personal data" are considered to be associated with the User as defined in the relevant privacy laws.
Figure 3
Click Next, you need to choose whether to use it for tracking purposes. If the call here the activation interface - trackInstallation: or - trackAppInstallWithProperties: need to select is. Here, the purpose of SDK tracking is to analyze and measure the effectiveness of advertising campaigns, as shown in Figure 4:
Figure 4
equipment id
The device id collected by the SDK is used to collect the data before user login, so continue to select "Analysis" here, as shown in Figure 5:
Figure 5
Click Next, because the collected data will be bound to the device id, so continue to select Yes here, as shown in Figure 6:
Figure 6
Continue to the next step, along with the user id, if you call the activation interface and enable IDFA, you need to continue to select Yes, the Analytics SDK will use IDFA to associate with third-party data for targeted advertising or AD evaluation purposes, as shown in Figure 7:
Figure 7
Product interaction
After the SDK is fully embedded, App startup, exit, user click, browsing and other related behaviors will be collected for product analysis, so continue to select "Analysis" here, as shown in Figure 8:
Figure 8
Click Next and continue to select Yes, as shown in Figure 9:
Figure 9