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: Temporarily does not support , because the platform currently only supports HTTP or HTTPS protocol address in the Web standard.
(But in general, the ad platform puts the redirect address has nothing to do with the product information entered here in Playturbo. However, after entering the product information, the information will be recorded in the Library, if the next time to do material based on this product, and then placed to external channels (such as imobile, Adcolony, Chartboost, Snapchat, applovin and unity), these channel specifications require packaged shop links will have an impact. (So it is recommended to follow the real shop links, otherwise it will always be a hidden danger.)
A: 1 time. The number of times is mainly related to the number of download channels and the number of exported versions.
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: No. Whether the playable is created via Playturbo or any other tool, the Mintegral platform does not support downloading it.
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 can be found in 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 can be found in： 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: It is recommended to first test the playable material according to the Playable Upload Specifications for Networks. If the testing shows "CTAClick not yet activated," you need to click the download button in the test play area to resolve the issue.
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 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.
