Q1: When previewing the playable, the bgm or other sound effects don’t play automatically upon entry, or are delayed — what’s going on?
A: This is expected behavior due to browser restrictions — audio cannot autoplay until the user performs an action (like tapping the screen). This issue won’t happen during actual ad delivery, so there’s no need to worry.
During preview, you can try tapping anywhere on the screen or clicking the persistent download button first to trigger the background music, then proceed with the playable — all audio should play normally.
Q2: The playable material looks fine in the platform preview, but when scanned with a mobile phone, it loads extremely slowly or doesn't load at all, making it impossible to play normally.
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.
Q3:After creating a playable ad, the preview link on a mobile phone shows incomplete product information or other visuals. Why?
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.
Q4: After downloading the channel package (e.g., Unity), the playable link can be opened and previewed on the computer. How can I preview it on a mobile device?
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.
Q5: Will the loading screen at the start of the playable appear during actual delivery?
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: Optional field.
If filled: The entered text will be displayed as is and will not adapt to other languages during ad delivery.
If left blank: The default text shown in the blue box in the screenshot will be used, and it will adapt to the preview device language.
Q6:After downloading the channel package and opening the HTML file locally, I can't trigger the redirect to the app store—is this a bug?
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.
Q7: I encountered issues when previewing the playable on mobile via QR code. After fixing the issue, it works on PC but still not on mobile—why??
A: Please note: after any updates or changes to the project, you need to save the project first, then regenerate the preview link or QR codebefore testing on mobile.
If the issue persists, feel free to contact your AM.
Q8: When previewing a playable on mobile, I see a pop-up message saying “Power saving mode may affect ads preview.” Will this impact actual delivery?
A: This message only appears when previewing a playable with power-saving mode enabled on your device. It will not affect the actual ad delivery. As the pop-up indicates, “No impact on actual ad display,” so there is no need to worry.
Q9: The playable works fine in desktop preview, but fails to load when opening it on mobile via QR code or shared link.
A: This issue may occur if the QR code is scanned or the link is opened before the playable has fully finished loading. Please make sure the playable is completely loaded before scanning the QR code or copying the link for mobile preview.
