Bug in typeform-triggered campaign: campaign doesn't deliver the correct email following the T/F branch condition

Hey Giulia,

I haven’t had any issues with Typeform so far, but I hope I can help you anyway. I think I would need some more information, though:

• Can you provide some screenshots?
• Is the boolean information (true/false) strored first as attribute in the profile? If so, is stored as JSON or simple a value?
• Have you connected typeform via a manual webhook or using the forms feature?

Thank you very much for your help!
There you go: 

• typeform: is connected via forms feature (see screenshot below). The attribute I want to monitor is the one circled

  

   

• the info is stored as a simple value in the profile attributes (see drop down menu in the screenshot)

• 

   

• Here below I share with you the overall workflow and the T/F branch details

• 

  

  Thank you again for your help, let me know if you need further info!

Hey Giulia,

thanks for the screenshots. That helps a lot. The form feature is a bit limited. Are you actually sure the the attribute that is created has a value that contains “isioterap”?

In my experience the typeform webhook has a lot of data that also stores other information like ids. Could be the value is actually not the name but an id of the typeform answer field or something similar. Can you check the person profile, just to make sure? 

hi! it looks like it does but please tell me if I am misreading something

Alright. That seems to be correct.

Next try: I remember we had issues with the processing. We can try that next.

So the person submitts the form and the campaign is triggered immediatley. It seems that sometimes the if branch is triggered before the attributes are saved to the profile. That way, the attribute does not exist yet or is not filled with a value and therefore the person is always sent to the false branch.

Can you try adding a time delay of one minute or so before the if-branch?

that works! Thank you very much for your help

You’re welcome 😉

As a note:

If you do not want to work with delays, you can simply not work with the “form feature” of Customer.io and Typeform. Use the trigger “webhook” instead of “form submission” and set up the webhook between Typeform and Customer.io yourself. This way you can work with the data inside the webhook directly instead of waiting for the attribute to update. 

You will have to save the information you want to store in the profile with a “create or update a person” manually, though.