Tackling an on-going issue where embedded forms do not render. While this is related to ad blocking, we have a specific repeatable use case:
- An Instagram ad appears while browsing through Instagram.
- User taps the CTA, which triggers an in-app webview that contains a page on our site. That page has an embedded Klaviyo form.
- Klaviyo fails to load, leaving a hole in the page.
- Users’ device checked: No ad blocking software installed, default Safari options. So it looks like Safari (15.4) is blocking it out of the box. That’s a LOT of users.
There needs to be a better way of handling blocked content: or at least, Klaviyo needs to be far more transparent about what may and may not work and how to handle cases where embedded forms do not work.
Asking users to disable ad blocking is just not going to wash as more and more browsers do this out of the box.
Sadly, looks like we will now have to remove Klaviyo from many of our landing pages and replace with Shopify forms.
Has anyone come up with an elegant solution?
Best answer by DovView original
Thanks for the response. Interesting resources there.
In the meantime, we’ve switched to using the Klaviyo addon for Shogun (in which our landing pages are constructed). This appears to circumvent the issue as I believe Shogun is talking to the Klaviyo API, rather than loading Klaviyo client-side scripts.
Thanks for sharing this question with us.
that could prevent the form from loading. Resolving this involves having our support team remove the duplicate script(s) from your website. Here’s a thread on that topic:
I also recommend exploring the solutions outlined in the below thread which includes signup form troubleshooting steps:
We do have a call out for internet explorer users which does have a known browser limitation with our forms:
Lastly, I would consider reviewing the code on your site, if you’re running any 3rd-party scripts on your website - that could be interfering with the ability of our forms to load. We’ve certainly come across cases like that before.
I hope you’re able to get this resolved through one of the aforementioned steps. If not, you can also reach out to our support team to have a closer look at your particular website/use case.
Thanks for being a community member.