Hey ​@bertoalvaro,

Welcome to the community! That’s a good question, and I’m actually consulting my team on this now, to see if we can provide you with a concrete answer. Since you’re editing a form with custom CSS outside of Klaviyo, I can’t reliably say how that will impact how the form behaves, but my hunch is that it will still count as a form view, even when CSS is set to display:none. That being said, it might be worthwhile to test this. I’d recommend adding a form to a rarely-visited page on your site, and hiding the form with CSS, then viewing the page once. Wait a few minutes, and see if a form view is logged in Klaviyo.

Does this make sense? If you have any other questions about this process, don’t hesitate to let me know!

Hi ​@Byrne C:

We have two ways that we implement this. 

Scenario: We want to display an embedded form on the homepage to only New Site Visitors targeted by Dynamic Yield, our personalization platform. To show an email sign up promo for new customers only.

Option 1: The Klaviyo form is inserted in our CMS but set to display:none in the CSS. When Dynamic Yield identifies a New Visitor, it displays the form by setting the CSS to display: block. This means the code is always present whether it is visible or not.

Option 2: When a new visitor visits the homepage, Dynamic Yield inserts the Klaviyo form in that moment and it is displayed. It is not living in the CMS, meaning return users’ visits will never load the form snippet.

We have done Option 1 in the past and we are running Option 2 currently. Hypothetically, if impressions are only based on the snippet loading, I think I would see a higher CTR on Option 2 because it would only count real impressions.

From the scenario described, option 1 will result in more “form views” in Klaviyo (because Klaviyo isn’t registering that you had CSS set to hide the form), and a lower submit rate, so scenario 2 would result in a higher CTR, that’s correct!