Hi ​@juliane 

I did this for a client a while ago. From memory, I created hidden fields for firstname and email in their Typeform survey. Then my email button url was of the form:

pyour_typeform_domain_url]/uyour_typeform_survey_name]#first_name={{first_name}}&email={{email}}

Which transparently passed the email recipient’s firstname and email to Typeform so they didn’t need to enter their email during the survey. I used firstname just for survey personalisation. The recipient’s survey results are captured against their profile in Klaviyo.

You obviously need to have the Typeform/Klaviyo integration set up first.

Please test and hopefully that works for you OK.

Regards

Andy

Hi ​@juliane 

Backing up what ​@bluesnapper said above, you’ll need to edit your Typeform survey to enable the passing of hidden fields.

Click on the Workflow tab and then the “Pull data in” section. That will open the URL parameter section where you can enable and add those fields you want to collect from the URL you link to within the Klaviyo email:

Thanks,

Ross

Hey guys!! You made my days, it seems it is working. Thanks a lot

​@bluesnapper  and ​@ross_hopkins one more question if I May.

Now I want to create a tagg in Klavyio with all people that answer to the first question of my typeform “How likely would you recommand … from 0 to 5?” - with a score of 4 or 5. → Tag: Happy Customer.

So that then I can create a flow with a condition did a second purchase AND belong to the tag Happy Customer or did a second purchas AND did not belong to ..

Do you know if I can do that?

Pleased to help @juliane 

The example flow below would work for tagging. If a user completes the survey and rates 4 or 5 (out of your 5 max), you add “Happy Customer” to a custom profile property in the first flow step eg “customer_satisfaction”

Notes:

• A user will enter this flow each time they submit the survey with a 4 or 5 rating and trigger the type form event. So, you should consider the profile filters for your specific use case.
• The  trigger filter condition “how likely...” will appear in the dropdown only if you have at least one profile with that custom property already.
• You don’t have to have this flow for your use case: Your Typeform form will create a custom property “how likely...” with the values captured. You can use that property/values directly in your 2nd purchase flow without the need for a tagging flow. However, I appreciate the tagging approach might be a less error prone when creating flows and segments. 

Hope that helps

Andy

​@bluesnapper It worked out! thanks a lot

Good to hear ​@juliane 

Have a great weekend when you get to it1

Andy