To view and configure monetization settings for your project, on the Monetization Dashboard, select CURRENT PROJECT > Settings in the secondary navigation menu.
This section lists the following properties for your project:
|Project name||The name of your project. This setting is read-only, but Organization Owners can change project names (refer to creating and editing projects).|
|Project ID||The unique Unity identifier for your project.|
Selecting your mediation partner allows Unity to improve its tools and experiences for you and your project. For more information, refer to Implementing Unity Ads in third-party mediation.
Privacy controls allow you to manage contextual ad settings for your project in a single place. The Children’s Online Privacy Protection Act (COPPA) imposes restrictions on how data can be collected and used from children under the age of 13. Unity Ads provides tools to help publishers provide a safe and positive user experience. Accordingly, each Unity Ads-enabled project must specify whether their project targets users under the age of 13. This article will guide you through configuring the right setting for your project based on your target audience.
To view and edit your project’s privacy settings on the Monetization Dashboard, select CURRENT PROJECT > Settings from the secondary navigation menu, and then go to the Privacy controls section.
Game-level COPPA designation
This setting applies a single project-wide designation for each platform. There are two options:
- This app is directed to children under the age of 13 means the project falls under COPPA restrictions, and can therefore only serve contextual (non-targeted) ads to all users. Note that this designation permits you to enable user-specific COPPA designations solely for applications you also designate as mixed audience applications.
- This app is NOT directed to children under the age of 13 means the project does not fall under COPPA restrictions, and can therefore serve behavioral (targeted) ads to all users.
Mixed audience games
If your app is directed to children under the age of 13, a conditional field displays where you can designate your app as directed to mixed audiences (that is, it is targeted to both children and to adults). Setting Is this app is a Mixed Audience Game to Yes allows you to pass individualized designations for each user to determine whether they fall under COPPA restrictions.
User-level COPPA statuses
A project-level designation should be sufficient for most projects, however, projects with mixed audiences (that is, it is targeted to both children and to adults) have one additional configuration choice.
To enable user-specific COPPA designations:
Present your users with an "age gate" in order to determine whether individual users meet the applicable age threshold.
If needed, enable the user-level COPPA feature inside ironSource mediation or your in-house mediation so that the mediation platform passes the appropriate age gate value along to Unity.
Set the Game-level COPPA designation to This game is directed at children under the age of 13.
Set Is this a Mixed Audience Game? to Yes.
You must pass Unity Ads user-level age designations programmatically by using the
user.nonbehavioral MetaData API. For complete instructions on how to implement this MetaData class in your code, refer to the documentation on COPPA compliance.
The following integrations currently support user-level age designation in Unity Ads:
Refer to the corresponding links for instructions on how to implement user-specific COPPA designations in your app code.
Default behavior for unknown users
Default behavior refers to the baseline behavior of ads served in your project when a user-level COPPA designation is absent. Unity Ads will default to treating users as children and only serve contextual ads when a user-level COPPA designation is absent. The default behavior is relevant only for Mixed Audience applications, and cannot be independently altered.
Refer to the following table to determine the behavior results of your Privacy Settings configuration:
|Game-level age designation||Mixed audience game?||Contextual ads control||End-user behavior|
|Directed to children under the age of 13||No||Not Available||Unity treats all users as under the age of 13 and only serves contextual ads.|
|Directed to children under the age of 13||Yes||Not Available||Unity receives user-level designations. Users designated as 13 and older receive personalized ads, but all other users (including those with unknown designations) are treated as children and only receive contextual ads. Note: Mixed audience games are still eligible for Google’s Designed for Families program or Apple’s Kids Category. For more information, refer to the documentation on app store compliance.|
|NOT directed to children under the age of 13||Not available||Show contextual ads only||Even though the project is not directed at users under the age of 13, all users only receive contextual ads.|
|NOT directed to children under the age of 13||Not available||Allow personalized ads||All users are treated as 13 or older, and might receive personalized ads.|
Missing SKAdNetwork Ids from Info.plist
This field provides a list of recommended ad network IDs that are missing from your iOS project's
Info.plist file. For more information, refer to configuring network IDs for iOS 14.
Optionally link your project to live Store IDs for the project’s Apple App Store or Google Play Store app page.
Extract the Apple App Store ID from your app’s URL, as shown in the highlighted section of the following URL:
Extract the Google Play Store ID from your app’s URL, as shown in the highlighted section of the following URL:
You need the Game ID for each platform to initialize the Unity Ads and Unity IAP SDKs in your code. You cannot edit these IDs.
App store compliance
Both Google and Apple introduced requirements to ensure that apps that are directed at children and serve ads are safe to use. If you serve ads in your app and want to participate in Google’s Designed for Families program or the Apple Kids Category, you must set your age limits filter to Do not show ads rated 13+ or stricter. Selecting one of these programs in your project settings will automatically configure the age designation setting to This app is directed to children under the age of 13, and set your age limits filter to Do not show ads rated 13+ or stricter.
Skipping rewarded ads
Compliance with kid-friendly programs requires that all monetized (rewarded) ads can be dismissed after 5 seconds. Note that Rewarded Ad Units are not skippable by default. For information on changing this setting, refer to Ad Unit settings.
For publishers that also advertise with Unity, allowing Unity to collect revenue-optimizing data can increase Unified Auction campaign performance. Enabling this setting allows Unity to collect session data that enhances your User Acquisition campaigns, to better define the value of new users in your project and similar users from other projects in Unity’s network.
To do so, ensure that your project has the Ads SDK installed, and an active User Acquisition campaign. Select CURRENT PROJECT > Settings from the secondary navigation menu, then go to Acquire Optimization and enable the setting for each platform.
- Sign in to your Apple developer account and select App Store Connect from the left navigation menu.
- Select Go to App Store Connect.
- On the App Store Connect page, select My Apps. If you do not have an app, select + to create a new app.
- Select In-App Purchases > Manage from the left navigation menu.
- Select App-Specific Shared Secret to display the key.
- Copy the key and paste it into your Acquire Optimization setting in the Monetization Dashboard, in the App-Specific Shared Secret field for the Apple App Store.
For more information, reach out to your Unity representative.
Ad delivery status
Use the Enable ad delivery toggle to temporarily stop serving ads to your application.
Use Test mode to test your integration without serving live ads. You can override programmatic settings on a device by toggling Override client test mode, and then enabling Force test mode ON for all devices. It is important to enable test mode before testing integration to avoid getting flagged for fraud.