Skip to main content

Hey there, 

I’m wondering if someone had the same issue like me and were able to solve it.

I would like to embed a Klaviyo Sign-up form in Shopware 6 as Landingpage, but if the user doesn’t accept the Klaviyo Cookie before, the form will not be appear. 

In order of GDPR I have to use a Cookie banner, but I would like to use the sign-up form always. 

Does anyone have any ideas on how to implement this?

Hi there @Elke

 

Thanks for sharing your question! 

 

Sign up forms rely on cookies, especially if your forms have a setting/rule to determine who to show the form to, so if someone does not accept cookies, there is no way for the system to identify the visitor and thus the form would not show for them.

 

Unfortunately there is not a way to work around this issue without cookies being accepted. I would recommend testing a form that has no rules or settings in terms of who they appear to, so if you set it to show to everyone, as those may work without cookies, but this also depends if the third party consent integration allows that.

 

I wonder how our friends in EMEA handle these situations, any additional advice or thoughts here @bluesnapper, @Victoria_ap_G, @Casperackermann ? 

 

-Taylor 


Hello @Taylor Tarpley 

thanks a lot for your reply. 

Even if you select the setting in the form that it is always displayed for everyone, the cookies must first be confirmed. 

So if anyone has a customised solution to this, I would be very happy to hear from it :-)


I am having the same issue. Embed form has no restrictions, as it’s just a subscribe block in the footer of our site. It will not appear until the analytical cookies are accepted. It’s quite frustrating!! Were there any other suggestions on how to fix this?


Hi @Nanette 

we solved that Issue as we integrated an HTML code which connecting to the related Klaviyo List in shopware 6. It’s absolutely not sexy, but it was the only way to go. 


Hi @Nanette 

we solved that Issue as we integrated an HTML code which connecting to the related Klaviyo List in shopware 6. It’s absolutely not sexy, but it was the only way to go. 

Hi @Elke 

If I’m understanding you correctly, you used the HTML code to embed the form? That is what I did as well. In trying to troubleshoot this issue, Because our target audience is US and we only sell within the US, I switched our cookie consent from GDRP to US compliance, which involves a different process with handling the cookie acceptance. I think this might have fixed the issue, as it seems the embedded form shows up consistently now.  I’m still testing it, but am hopeful that’s the resolution!!


Hi @Nanette 

we solved that Issue as we integrated an HTML code which connecting to the related Klaviyo List in shopware 6. It’s absolutely not sexy, but it was the only way to go. 

Hi @Elke 

If I’m understanding you correctly, you used the HTML code to embed the form? That is what I did as well. In trying to troubleshoot this issue, Because our target audience is US and we only sell within the US, I switched our cookie consent from GDRP to US compliance, which involves a different process with handling the cookie acceptance. I think this might have fixed the issue, as it seems the embedded form shows up consistently now.  I’m still testing it, but am hopeful that’s the resolution!!

Hi @Nanette 
that sounds great. Crossed fingers, that everything working well for you now. 
 


@Nanette @Elke 

 

Can you share how your experience and testing going? Is it possible to use klaviyo form without cookies? If yes how you manage that exactly?


Hi @Jakub
after my last post, I got feedback that we could also adjust our extension with the following logic: 

page load

cookies accept

cookies denied

  • no change needed

 

It explained in that help article how it works: https://help.klaviyo.com/hc/en-us/articles/4764571493275

 

This splits the tracking, for example, by always displaying the sign-up form without sending any extra data to Klaviyo if the cookie consent has not been confirmed. However, we haven’t used it yet and are still using the solution mentioned above. 


Reply