Sometimes, it can make sense to include several registration forms in the flow. This could for example be relevant in cases where you initially want to collect primary contact details like name, e-mail address, or phone number, and later in the flow, you want to collect additional data like age, gender, or preferences.

If you have several registration forms in one campaign and want to transfer the data to an ESP or CRM system, there are some things you need to consider.

If your campaign flow contains more than one registration form, and fields from more than one registration form are mapped in the same ESP/CRM integration, data from the registration forms will only be transferred, if both registration forms are filled out.

This means, that if you have a campaign with two registration forms, and the player decides to only fill out the first form, no data will be transferred.

To avoid losing valuable data, you need to transfer data from each registration via two separate integrations.

The data can be sent to the same list, but you need to separate the transfer of data from the two forms to ensure that data transfer from a primary registration form is not dependent on the other form(s) being filled out.

In the below example, two Mailchimp integrations have been set up on the same campaign. They transfer data to the same list in Mailchimp, however, each integration transfers data from a specific registration form in the flow.

Only data from the 1st registration form in the flow (name + e-mail) is mapped up. This ensures that data from the 1st registration gets transferred even if the 2nd registration form is not filled.

In Integration 2, only data from the 2nd registration form in the flow is mapped up.