
On this page
- First, confirm it is really broken
- Cause 1: The form is not targeting mobile
- Cause 2: The script is not loading
- Cause 3: A timing race with your theme
- Cause 4: CSS hiding or clipping the form
- Cause 5: Consent banners and other overlays
- Cause 6: Google's mobile interstitial rules
- Cause 7: Ad and content blockers
- A quick test routine after any fix
- What it costs you to leave it
- The short version
Your email list is growing on desktop. On mobile, where most of your traffic probably is, signups are flat. Nobody has complained, because nobody can complain about a popup they never saw.
We ran into exactly this on a client Shopify store with a heavily customised theme: the Klaviyo signup form worked perfectly on desktop and rendered unreliably on phones. The fix took a few lines of code. Finding the cause took longer, so this post lists the seven things we check, in the order we check them.
It applies to Shopify and WordPress alike. Klaviyo's onsite forms work the same way on both.
First, confirm it is really broken
Do this before touching code:
- Open the site on a real phone in a private window, so you are a new visitor.
- Wait for the form's trigger (time delay, scroll depth or exit intent).
- In Klaviyo, open the form's analytics and compare views on mobile versus desktop. A form with healthy desktop views and almost no mobile views has a delivery problem, not a copy problem.
Private window matters. Klaviyo hides forms from people who have already closed or submitted them, which makes your own phone a bad test device.
Cause 1: The form is not targeting mobile
Klaviyo forms have separate device settings. It is easy to design a desktop popup, switch it on and never notice that mobile is set to a different form, a different trigger or nothing at all. Check the form's targeting and behaviour settings first. This one costs nothing to fix.
Cause 2: The script is not loading
On Shopify, Klaviyo onsite forms load through the Klaviyo app embed in the theme editor. If it is switched off in a new or duplicated theme, forms silently stop. On WordPress, it is the Klaviyo plugin or a manually added script. Check that the script is present on the page source of a mobile page, not just the homepage.
Cause 3: A timing race with your theme
This was our case. Klaviyo's script loads asynchronously. The theme's own mobile JavaScript, in this case a custom menu and drawer system, ran first and tried to interact with the form before Klaviyo was ready. On fast desktop connections, Klaviyo usually won the race. On slower mobile connections, it lost.
The reliable fix is to use Klaviyo's command queue rather than calling the form directly. Klaviyo provides a global array, _klOnsite. You push commands into it, and Klaviyo runs them once it has loaded, whenever that is:
window._klOnsite = window._klOnsite || [];
window._klOnsite.push(['openForm', 'YOUR_FORM_ID']);Because the array exists before Klaviyo does, your command waits in line instead of failing. We used this retry pattern for the mobile trigger and the form started rendering consistently.
Cause 4: CSS hiding or clipping the form
Mobile themes often set overflow: hidden on the body when a menu or drawer opens, or give headers and announcement bars very high z-index values. Either can push the form behind other elements or clip it off screen. Inspect the page with your browser's mobile emulator and look for the form's container in the DOM. If it is there but invisible, it is a CSS problem.
Cause 5: Consent banners and other overlays
Cookie banners, age gates, chat widgets and other apps' popups all compete for the same moment. Some cookie tools block Klaviyo's script until consent is given, which is correct for privacy but means the form only appears after the visitor accepts. If the banner is set to wait for consent, the form trigger timing should allow for it.
Cause 6: Google's mobile interstitial rules
This one is a design choice, not a bug. Google has long discouraged full-screen popups that cover content as soon as a mobile visitor lands from search. Many teams respond by switching mobile to a small flyout or a delayed trigger. That is sensible, but make sure the smaller version actually exists and is turned on, or you end up with no mobile form at all.
Cause 7: Ad and content blockers
A share of mobile visitors use browsers or extensions that block marketing scripts. You cannot fix this one, but you can hedge it: add an inline signup form in the footer or on key pages. Embedded forms are less likely to be blocked than popups and they catch people the popup misses.
A quick test routine after any fix
- Real iPhone in Safari, private window
- Real Android in Chrome, private window
- Throttle the connection to slow 4G in your desktop browser's emulator and reload
- Accept and decline the cookie banner, test both paths
- Submit a test email and confirm it lands in the right Klaviyo list
What it costs you to leave it
Work it out with your own numbers. Take your monthly mobile sessions, multiply by the desktop form's signup rate, and that is roughly how many subscribers a working mobile form could add each month. Then multiply by what an average subscriber is worth to you over a year. For most stores it is a number worth an hour of developer time.
On the store behind this post, the mobile signup rate went from 12% before the fix to 43% after.
The short version
When a signup form works on desktop and not on mobile, check device targeting, script loading and timing before anything else. Use Klaviyo's _klOnsite queue so your code never races the script. Then test on real phones, in private windows, on slow connections.
Bit Aura sets up and debugs email capture and tracking on Shopify and WordPress. Ask us to check yours.
Related services
Need help with web development?
Tell us what you are planning and we will point you to the right next step. No pressure.




