Child-directed apps—FAQ

1. Follow the Add app wizard.
2. For step 2 of the wizard, see instructions about child-directed apps.
3. After the app is added:
   • Implement the Dev key in the SDK
   • Include appropriate privacy controls

 See more details about implementing compliance tools with ad networks.

Two weeks after adding the app, you'll get a notification asking you to confirm you've implemented privacy controls for your child-directed apps. After confirming, you'll get a confirmation message. You can always access the confirmation message from the Notification center or see the confirmation details in the Audit log.

At this stage, once you select whether an app is directed toward children or not, your selection can't be reversed. This option is only possible while adding the app.

Once confirmed that an app is directed toward children, there are two ways you can see the confirmation:

• Notification center: From the menu bar, click the notification iconand find the confirmation notification.
• Audit log:
  1. From the menu bar, access the user menu (email address drop-down).
  2. Select Security center.
  3. In the Audit log section, click View audit log.
     You can see the confirmation details under the My apps service.

When your app is intended for children or a mixed audience (children and adults), you can use any of the recommended tools from this guide that align with the legal requirements. See more SDK resources at the bottom of this page. 

Examples of compliance tools and their use

The AppsFlyer compliance solution guide offers different tools, each with different levels of control. The impact on attribution varies based on the specific tool you choose to implement.

When using a tool that limits the sending of user data, such as the device ID, other attribution methods are used, such as probabilistic modeling or Install referrer (for Android).

Tools that don’t send user-level data are considered privacy-preserving and enable receiving aggregated campaign data.

It's often unclear whether ad networks you collaborate with are compliant with relevant laws. You can refer this question to the ad network. If they aren't compliant or you're unsure, you can avoid sharing with them your data. You can use the setSharingFilterForPartners function to specify which ad networks to block from receiving your app data. You can also use this function to block all ad networks. See more example compliance tools. 

AppsFlyer compliance tools must always be implemented. Which ones are appropriate for your needs depends on the audience of your app. You may use setSharingFilterForPartners function (“MediaSourceName”) if the ad network you're working with has committed to treat the data you've shared with them solely as a data processor for limited purposes allowed under COPPA, GDPR, applicable laws and rules, or other platform rules that require it and with appropriate consent

This applies to each of the ad networks you're working with.

Ad networks that aren't SRNs receive your data via postbacks. They can define which events to include in the postbacks. Install postbacks are sent by default for attribution, while in-app event postbacks are only sent if you've configured specific events to be sent. As long as postbacks aren't blocked or restricted by the SDK, they may contain user-level data related to app user engagements (installs, in-app events, and re-engagements).

Except for postbacks, ad networks and agencies have limited access to data via the platform.

To find out what data was sent to ad networks via postbacks:

• Download postback reports from the Reports > Raw Data Export menu

To control what data you're sending:

• Use any of the SDK-compliance tools, such as setSharingFilterForPartners to block or restrict certain data from being sent.
• Choose to whom you're sending default postbacks and in-app event postbacks, either to the ad network to which the event is attributed or to all media sources, including organic. 

To control the availability of user-level attribution data for iOS users:

• Use the Aggregated Advanced Privacy framework to enforce Apple ATT privacy levels. This ensures that user-level data, although used for attribution, isn't available in AppsFlyer to advertisers or ad networks. Aggregated data is available without limitation.

The SDK records your app events, such as installs, re-engagements, and in-app events. Without the SDK, there's no attribution. You can preserve user privacy with the SDK and show just aggregate data.