Collecting First Name via Multi-Step Form and use in Welcome Flow does not work

@Dov: Thanks for taking the time to answer. 

I have double-checked the settings and can confirm that the field was set to “required”. One odd thing I have noticed is that the first name does appear in all profiles I have used to test the sign-up process. So there is no problem with getting and saving the information, but with filling the variable.  

Is there maybe a time lag between the sign-up and the data being fully saved in the profile? 

Best

Hi @NextLevel,

Thank you for your follow-up reply.

Nope, the first name should be populating in the email immediately with no time lag/delay. Can you confirm you are using the same tag for first name as I described above? I also suggest trying to use just

{{ first_name }}

and see if anything populates. If not, it may be that the first name is being populated, but as a separate property (not under the default property for first name). If the first name variable is filled in correctly, you should see it at the top of the profile like the following:

If you have first name logged under the Information Section of the Profile, then the first name variable is being passed through as a custom property rather than the default “First Name” field. In this case, you’d have to use a separate tag to successfully pull in First Name into your email. That tag would be the person-lookup tag like this:

{{ person|lookup:'First Name'|default:’’ }}

I would also check your font colors, it could be that the name is coming through correctly but it is simply whited out. If you highlight the text where the first name should be, see if you can see it. You can adjust the colors for specific text using this button:

Let me know if that helps.

Hi @Dov! Thanks again for your detailed instructions. 

I changed the variable to 

{{ first_name }}

Before it was 

{{ first_name|title|default:'' }}

and checked that the text is not in white color. It was not 

After testing, I can confirm that:

1. The first name appears in the email. 
2. The first name is captured as a default property.

Then I changed the variable to 

{{ first_name|default:'' }}

After testing, I can confirm that:

1. The first name appears in the email. 
2. The first name is captured as a default property.

So this is working now 

However, during testing, I realized that the double opt-in email is already triggered when the user adds the email address (first step).

I could then confirm the opt-in and get the welcome message anyway without adding the additional info in steps 2 (name) and 3 (interests).

That’s not good at all, as I have built flows based on step 3 (interest). Is there any way to holding the double opt-in email back until the user fills in all information in the multistep form? 

Thanks & Best

Hendrik

Hi @Dov!

Alright. In my opinion, the order (email, name, interest) would make more sense because I get the “buy-in” from our users and then just collect additional data. To me, it seems more likely that users are open to add more data after submitting their email address. 

But I don’t want them to get the double opt-in email so early in the process, so I changed the order as you proposed. Maybe I will A/B test this in the future. 

Thanks for your help. I really appreciate it. Have a good one!