Export & Deployment Issues
Last updated
Last updated
AοΌWe need to check whether the shop link contains illegal characters (such as mixing with the product's Japanese name), and we need to delete these characters and then delete these characters and download it again.
A: Generally not supported or recommended, as the Playturbo platform currently only supports URLs that follow the standard HTTP or HTTPS web protocol β typically Google Play or App Store links. Here are a few specific cases:s:
For Mintegral channel: The actual redirect URL is determined by the store link set in the Offer on the Mintegral platform, not the one associated in Playturbo (but we still suggest using a matching store link for consistency!).
For certain channels such as Applovin, Unity, iMobile, Adcolony, Chartboost, and Snapchat, these platforms require the associated store link to exactly match the actual store link used in the campaign. Otherwise, the store redirection might fail. For these cases, we highly recommend using a Google Play or App Store link.
If you still want to use other types of URLs (e.g., Amazon), you can choose "Website" as the product type, then manually enter the URL, product name, and icon.
A: 1 time. The number of times is mainly related to the number of download channels and the number of exported versions.
A: It counts as 2 exports. Re-associating product info is treated as a project modification by the platform. It's best to bind both platforms (iOS and Android) before pushing/downloading.
A: It depends on the channel:
Mintegral: iOS and Android are handled separately. After applying the playable to the platform, you need to associate it with different Offers based on the device type. (You can check this in the material name suffix β it will include "ios" or "and").
All other channels: Universal for both iOS and Android.
A: This situation will display the English name correctly during actual deployment and will not have any impact. The reason you see the Chinese name on the platform is that it currently defaults to look up app information based on the package name and the Playturbo language environment. Therefore, if you are using the Chinese version of Playturbo, it may show the Chinese name. However, when packaging the playable material, the app information is generated based on the package name and the material's language. If the store link you provided is correct and the default language of the material is set to English, it will display the English name in the actual deployment.
You can also preview the corresponding playable material on the γExport & Download Historyγ page of the platform to check the actual product information.
A: This issue may arise due to an excessive number of scenes or video resources within the project, which can directly lead to slow loading or stuttering during playback. It is recommended to: reduce the number of scenes to β€4; avoid overly fragmented video clips or excessive interactions.
A: This issue is most likely caused by previewing the playable on a mobile browser. In such cases, the mobile screen is not fully expanded (thereβs a browser navigation bar at the top or bottom), which causes part of the content to be coveredβso you might not see the full screen. This won't happen in actual campaign delivery.
A: The playable links inside the downloaded zip file are generally not supported for direct opening on mobile devices. To view the actual preview for each channel, simply select the channel in the download window and click [Preview]. You can scan the QR code or copy the link to view it. This will show the same effect as the actual deployment.
A: Yes, the loading screen will be shown while the playable is loading. Loading screen language logic:
Product Info: It will first try to pull the app store info based on the projectβs default language. If thatβs not available, itβll use the language from the app store info linked in Playturbo.
Description Text: If you want to show specific text in a specific language, you can fill it in when linking the product. If you leave it blank, the system will default to the language of the userβs device.
A: This is expected. For some channels, HTML files wonβt trigger redirects during local preview. No worriesβthis won't be an issue in actual delivery.
A: Downloading is not supported. Whether the playable is created via Playturbo or any other tool, it cannot be downloaded.
Recommendation: You can apply the playable material to Mintegral platform but avoid adding it to the Creative Set. When needed, you can add it to the set and proceed from there.
A: This may be because you have marked Scene 1 as the "End Scene" when creating your playable project, which means that entering the playable experience reports an end right away. Thus, on the Mintegral platform, clicking leads to a redirect to the store (currently, Vungle and Mintegral channels require setting "Report the end of the playable ads," so if the timing for this is not set correctly, this issue will occur on these two channels, while it won't on others).
Solution: Uncheck Scene 1 as the "End Scene," and add a "Report the end of the playable ads" response event after the redirect to the store event.
πRelated contentοΌ WORK CREATION-IMPORTANT NOTICEβ οΈ
A: β First, ensure that you have uploaded video material to the creative set (as most traffic for interactive campaigns comes from "video + playable," so playable material needs to be paired with video). β‘ If you choose not to upload video, check whether your playable project has only one scene or if it has two scenes with the second marked as the Ending Scene. This is because when there is no video material in the creative set, Playable (pl) type materials can gain traction, but Endcard (iec) type materials cannot. If your project meets either of these two conditions, it will be classified as Endcard type material, which may explain the lack of performance. Most of our templates fall under the pl type.
Solution: Create a new blank scene in your project and place it at the end. No actions are neededβjust ensure the total number of scenes is greater than two.
πRelated contentοΌ Mintegral Creative Operation Guide
A: This situation is normal and can be ignored. The testing tool is primarily used to check if the playable material can redirect properly. The actual page that users see during deployment will depend on the product link bound to the offer on the Mintegral platform.
A: This is because the same version of a playable project cannot be pushed again.
Solution: Make any edits to the playable, generate a new version of the project, and then apply it.
A: This likely means the Mintegral account you're trying to authorize has already been linked to another Playturbo account.
If not, please contact your AM for assistance.
A: Here are the current Google channel guidelines regarding "inducing downloads" for your reference:
βProhibited on End Pages:
The CTA button text on the end page cannot include: Download/Redirect to app store.
Pointer hands are not allowed on the end page.
Permanent download button text cannot include: Download.
β Allowed Scenarios:
End page/permanent download button text: Next/Play now.
Use a zoomed white dot instead of a pointer hand on the end page CTA button.
An end page may consist of a blank button without text.
A: This is because the platform applies base64 encoding for channel downloads (see image below), and video resources become larger after encoding, causing the actual package size to differ from the initial estimate.
πRelated contentοΌPackage Size Estimation Content Editor - Download&Apply
A: Itβs recommended to search using the project ID. If the project is still not found, itβs possible you may have accidentally deleted it (the platform does not delete any projects).
You can also use this tool to convert the link and preview the mobile experience on your computer :
You can also use this tool to convert the link and preview the mobile experience on your computer :
πRelated contentοΌ
If you have access to that other Playturbo account, you can go to "" or remove the authorization.
A: It is recommended to first test the playable material according to theIf the testing shows "CTAClick not yet activated," you need to click the download button in the test play area to resolve the issue.
Suggestions: a. Use the options in the download window to reduce package size with one click. b. Reduce the number of video resources or further compress the video resources externally before uploading.
