Introduction
Template preview, deployment, and update issues in the Piano dashboard can stem from a variety of causes, ranging from unsupported template types and browser quirks to caching layers and corporate network restrictions. This checklist walks you through each potential cause in a logical order, starting with the quickest checks and progressing to deeper diagnostics. By following these steps, you can resolve most issues independently or collect the right information for Piano Support to help you efficiently.
Confirm Preview Is Supported for Your Template
Before troubleshooting, verify that your template type actually supports dashboard previews. Skipping this step can lead to wasted effort investigating a "problem" that is actually expected behavior.
Templates Without UI Preview
The following template categories do not generate previews in the Piano UI:
-
My Account templates
For these template types, test directly on your website or integration environment instead of relying on the dashboard preview.
Offer Template Requirements
Offer templates require an associated offer with at least one term in order to render a preview. If no term exists:
-
The preview may appear blank.
-
Offer-related elements may be missing from the preview.
Action: Ensure your offer template has at least one term configured before attempting to preview.
Preview vs. Live Behavior Differences
Be aware that preview behavior may differ from your live site:
-
The preview uses a default "registered user" context.
-
If your template logic changes for new/anonymous users vs. registered users, the preview may not reflect the "new user" experience.
Common Symptoms and What They Usually Mean
Use the table below to quickly identify the likely cause based on the symptom you are experiencing.
Blank Preview (Empty Iframe / White Screen)
Most often caused by:
-
Missing offer term(s) for an offer template
-
Browser extensions (ad blockers, privacy tools) interfering
-
Network/security tools blocking preview domains
-
Browser protocol issues (HTTP/3 / QUIC)
Preview Shows Old Code (Changes Don't Appear)
Most often caused by:
-
Caching (browser cache/cookies and/or edge/CDN caching)
-
Preview/thumbnail generation lag (queued rendering)
-
You edited a template but didn't publish the version you're testing
Step-by-Step Troubleshooting (Recommended Order)
Follow these steps in order. Each step builds on the previous one, starting with the fastest checks first.
Rule Out Browser/Session Issues
These are the fastest checks and resolve the majority of preview problems.
-
Try Incognito/Private mode.
-
Disable extensions, especially ad blockers and privacy/security extensions.
-
Try a different browser (latest versions recommended):
-
Chrome
-
Edge
-
Firefox
-
Safari
-
-
Ensure your browser and OS are up to date.
Edge-Specific Cleanup
-
Go to:
edge://settings/content/cookies/siteData?searchSubpage=piano -
Click Remove all shown.
-
Log back in and retry the preview.
Chrome-Specific Cleanup
-
Go to:
chrome://settings/content/all?searchSubpage=piano -
Click Delete displayed data.
-
Log back in and retry the preview.
Force the Preview to Regenerate
If the preview thumbnail or iframe appears "stuck":
-
Make a tiny HTML change (for example, add a space).
-
Click Save.
-
Remove the change and click Save again.
-
Reload the preview.
If your preview UI includes device controls:
-
Change the device preview model, then use the reload/spinning arrows control to refresh.
Account for Caching/Propagation Delays
Template changes may take time to appear in preview and on-site due to caching and propagation.
|
Scenario |
Expected Timeframe |
Action |
|---|---|---|
|
Typical propagation |
~15 minutes |
Wait and retry |
|
Changes still not visible live |
30+ minutes |
Investigate further and/or contact support |
Disable HTTP/3 / QUIC
In some environments, HTTP/3 (QUIC) can prevent preview content from loading. Disable it in your browser and retry.
|
Browser |
Steps to Disable HTTP/3 / QUIC |
|---|---|
|
Chrome |
Navigate to |
|
Edge |
Navigate to |
|
Firefox |
Navigate to |
|
Safari |
Enable Develop menu → Develop > Experimental Features → disable HTTP/3 |
Retry the preview after disabling.
Check Network/Security Tooling (Corporate Networks)
If you are on a corporate network, using tools like Zscaler, or connected to a VPN, the preview can fail due to blocked or rewritten requests.
-
Try disconnecting from VPN and retesting.
-
Ask your IT/security team to allowlist Piano dashboard and preview domains for your region.
Domains to allowlist (examples):
-
https://dashboard-eu.piano.io/ -
https://checkout-preview-eu.pianousercontent.io/ -
Equivalent US, AP, AU domains if you are in another environment
Make sure you're using the correct environment (EU vs. US) and that your Application ID (AID) matches that environment.
Use Developer Tools to Identify Errors
When the issue persists after all previous steps, use browser Developer Tools to dig deeper.
Open Developer Tools (typically F12 or Ctrl+Shift+I) and check:
-
Console: JavaScript errors, blocked requests, CSP errors
-
Network: Failed requests (e.g.,
404,403,5xx), stuck requests, redirects
If possible, capture the following diagnostics:
|
Diagnostic |
Description |
How to Capture |
|---|---|---|
|
HAR file |
Full network trace while reproducing the issue |
Network tab → Export HAR |
|
Screenshots |
Visual evidence of the issue with Console/Network visible |
Screen capture tool |
|
Screen recording |
Short video showing reproduction steps and Developer Tools output |
Screen recording tool |
These diagnostics are often required to pinpoint whether the cause is template code, caching, network blocking, or a service issue.
When to Contact Support
Contact Piano Support if:
-
Preview remains blank after completing browser, network, and HTTP/3 checks
-
Updates are not visible after expected propagation time (e.g., 30+ minutes live)
-
You see repeatable errors in Developer Tools (Console/Network)
Include the following information in your support request:
|
Information |
Details |
|---|---|
|
Environment |
EU or US or AP or AU |
|
Application ID (AID) |
Your application identifier |
|
Template details |
Name, type, and whether it is a variant |
|
Steps to reproduce |
Detailed reproduction steps |
|
Console logs + HAR file |
Captured from Developer Tools during reproduction |
|
Screenshots / screen recording |
Visual evidence of the issue |
|
Network environment |
Whether you are behind VPN/Zscaler/corporate network and any allowlisting attempted |