Embedding a 1 question survey into a flow email

Hi David! Thanks for providing such a thorough response. Makes sense that live content is often blocked via email providers - never thought about it that way.

If I were to use the update property profile method via hyperlinked image, would I be able to view the “results” of the imitated survey on a custom report? For example, how can I see what % of people who responded to the “survey” clicked option A/B/C etc?

Hi - I saw that Typeform provides documentation on how to embed their surveys right into emails. See here: https://www.typeform.com/help/a/launch-your-typeform-from-an-email-360029664091/ Would you still recommend against this given the spam issues you outlined above? Typeform seems to be suggesting this will work just fine with Mailchimp. Does Klaviyo not work the same way as Mailchimp. Thank you! 

Awesome! That’s super helpful. Thank you very much

Hey @alex.hong  cc: @alimac621  -- thanks for looping typeform into this conversation, as I’m working through a similar challenge and thought I’d share my progress with the Klaviyo community in the event that someone goes through the same thing down the road. 

I wanted to ‘have my cake and eat it too,’ combining (1) the update_property_link native to Klaviyo and (2) hidden fields in typeform. My goal was to make sure that I immediately knew someone’s response to a one survey question in Klaviyo (in case that person didn’t click ‘submit’ in typeform) and also capture the response in typeform, where I have a connection with Slack to alert me every time someone submits this particular form. 

I attempted to do this by creating Klaviyo buttons containing the update_property_link with URL = the URL of my typeform survey, passing hidden fields in that URL (i.e., {% update_property_link 'your-property' 'property-value' ‘https://typeformlinkandhash?#firstvariable=yes&email={{ email}}’ %}’

I discovered (or at least think I discovered) two things: 

(A) you can pass static (i.e., same value for all users who click on a particular button) hidden fields using the update_property_link method, but you can’t pass dynamic ones. Said differently, I was able to pass “firstvariable=yes” to the typeform, but Klaviyo passed {{email}} not as the user profile property, but rather literally the text “{{email}}” 

(B) you can pass BOTH dynamic and static fields if you just use a ‘regular’ link outside of the update_property method i.e., https://typeformlinkandhash?#firstvariable=yes&email={{ email}}

@alex.hong  -- is there something I could do differently to make Klaviyo ‘convert’ {{email}} in the link to the email property, similar to what it does in a ‘regular’ link? That would let me have my cake and eat it too. Otherwise, (A) is probably the next best solution, although it’s more of a cookie than a nice piece of cake.