Playable Upload Specifications for Networks
#Subscription # Customization
📒Supported Ad Networks & Test Apps
Currently, Playturbo supports the following channels for apply or download:

💡Usually, you need to unzip the downloaded Zip file once and use the Zip file inside to upload it to the corresponding channel.
If you encounter a prompt like "The main HTML file must be named 'index' and located in the first-level directory" when uploading the file to the channel, it indicates an issue with the Zip file. You can check if the Zip file has been unzipped before.
Google Ads
5 MB
Zipped HTML file
(Tips: unzip the downloaded compressed file once and upload the compressed file inside it.)
-
Liftoff
5MB
Zip file with resources
-
-
Moloco
2MB HTML / 5MB Zip
Single HTML or Zip with resources
-
-
TikTok
5MB
Zip file with resources
(Tips: unzip the downloaded compressed file once and upload the compressed file inside it.)
-
-
Inmobi
5MB
Pls Note: After downloading the InMobi playable material, you need to deploy the offline script content to the CDN and manually modify the paths in the HTML file for the material to function properly.
-
-
Tapjoy
1.9MB
-
-
-
Pangle
5MB
-
-
-
myTarget
2MB
-
-
-
Kwai
5MB
-
-
-
i-mobile
6MB
-
-
-
Snapchat
5MB
-
-
-
Smadex
5MB
-
-
-
Chartboost
3MB
-
-
-
Bigo
5MB
-
-
-
巨量引擎
3MB
-
-
-
快手
3MB
-
-
-
Tencent AMS
3MB
-
-
-
Tencent Ads
3MB
Zip file with resources
-
-
WeChat MiniGame
15MB
Zip with resources
Refer to the official WeChat documentation
-
NOTE:Remember! that specific size, formats and APIS need to be included for desired ads, make sure you have covered all them all when implementing your scene.
📒Special Note: WeChat MiniGame
1.Usage Intro
After completing your project editing, proceed with the download process:
Step 1: Bind "Project Info"
Click the top-right corner [Project Info] >>> Associate with promoted product >>> Add Promoted Product >>> WeChat MiniGame >>> Enter the MiniGame name, MiniGame APP ID, and icon >>> Confirm binding.

Step 2: Select "Playable ad steps" and confirm download
Click the top-right [Download] button >>> Choose the corresponding playable ad steps based on the process >>> Download. 2.Playable ad steps

Step 3: Select channel and complete download
Click [Download] >>> Check the [WeChat MiniGame] channel >>> Confirm package size >>> Complete download.

👉Related content: Feature Changer - Download&Apply Content Editor - Download&Apply
2.Precautions
2.1 Channel Restrictions
⚠️ Except for customized projects, other projects do not support using the "Rigid Body" feature, and the channel cannot be selected if this feature is used.
⚠️ All projects do not support using "Video" type assets, and the channel cannot be selected if this type is used.
⚠️ WeChat MiniGame channel does not support the concept of "redirecting to app store" (it will automatically go to the End Card after the trial ends), so there is no need to add any CTA buttons or redirect steps.

2.2 Some playable templates support the WeChat MiniGame channel
Currently, not all playable templates support exporting to the WeChat MiniGame channel.
You can check whether the template has the WeChat logo in the lower right corner to determine if it is supported.

📒Test playable ads for specific networks
The following content provide some guidelines on how to test your playable ads for specific networks.
1. Applovin
If you wish to use external requests like analytics with your Applovin build, you will need to contact Applovin prior to uploading requesting permission to do so. Otherwise the playable will be rejected.
In order to test your build for Applovin, please follow these steps:
1)Download an Applovin build from you Creative Suite account.
2)Navigate to the Applovin playable preview tool.
3)Drag in your index.html file or find it manually.

4)If the playable is incorrectly formatted or over the file size limit, you will an error such as the following:

5)You may now test the playable in the preview, and change the orientation.
6)The preview tool will show a message when a successful app store click has taken place - please ensure this happens at all expected locations.

2.Facebook
In order to test your build for Facebook, please follow these steps:
1)Download a Facebook build from your Creative Suite account.
2)Navigate to the Facebook playable preview tool.
3)Drag in your file or find it manually.

4)If the playable is incorrectly formatted or over the file size limit, you will an error such as the following:

5)You may now test the playable in the preview, and change the resolution.
6)The preview tool will show a message when a successful app store click has taken place - please ensure this happens at all expected locations.
7)Once all the specification items on the right-hand-side are green, the playable can be uploaded to Ads Manager.

3.ironSource
The ironSource test tool has been deprecated in March 2023.
If you're planning to use ironSource for your playable ads, it's essential to make sure that your build is compatible with the platform. In order to do that, you'll need to submit your build for review in the ironSource dashboard.
Submitting your build for review is a straightforward process, but it's essential to follow the correct steps to ensure that your submission is successful. To help you through this process, ironSource provides a detailed guide that explains how to submit your build for review step-by-step.
By following the instructions provided in the ironSource guide, you can ensure that your build is reviewed efficiently and effectively and that your playable ads are quality assured.

4.Mintegral
In order to test your build for Mintegral, please follow these steps:
1)Download a Mintegral build from your Creative Suite account.
2)Navigate to the Mintegral playable preview tool.

3)Drag in your zip archive file or find it manually.
4)Play the playable in the preview tool. If the playable has any errors such as wrong size, wrong formatting or any missing APIs, it will be highlighted in red.
5)You can then preview the playable and change the orientation.
6)The preview tool will show a message when a successful app store click has taken place - please ensure this happens at all expected locations.
7)Once you are happy, and the test cases are all green, you can send your Playable to Mintegral.

5.TikTok
Currently, there is no testing tool available for playables on TikTok.
Additional Details
The display orientations and languages must be stored in a config.json file, located in the first-level directory.
The orientation must be stored with values of 0,1,2 (responsive, portrait, landscape).
The language code must be stored in the
playable_languages
array.
Example:
"playable_orientation": 0,
"playable_languages":["ja","ko"]
en: English ja: Japanese Ko: Korean Zh-Hant: Traditional Chinese
6.Unity Ads
In order to test your build for Unity Ads, please follow these steps:
1)Copy Unity Ads link from the download menu in your Creative Suite account

2)Download the Android or iOS test app from Unity
3)Open the app and past in the URL of your playable ad
4)Press "Initialize"
5)Once the ad is loads, press "Show"
6)If the ad fails to load, or to check the status of the ad, go back to the main screen and press "Analyse". Any issues will be surfaced in the Creative report
Example:

NOTE:Your playable ad must include the App Store and Google Play app store URLs in order to pass QA. Before carrying out the following steps, please ensure you have set these links in the Playable UI under:
Playable settings > iOS/Android install game link. More details here.
Please make sure that for iOS app store links, you use the apps.apple.com/
domain, and NOT the itunes.apple/com/
domain.
7.Vungle
In order to test your build for Vungle, please follow these steps provided by Vungle here.
8.Google
1)Please check "Select for App Campaigns" first, and then click "UPLOAD" to upload the correct compressed package.

2)The first error message is about the length of the zip file name. You can modify it freely, no need to worry.
3)The second error message has been investigated by our technical team, and there doesn't seem to be any issue with the file. It may be a problem with the detection tool itself and this error can be ignored.

Last updated