# Customize & Map Your Microsite Registration Form

When participants register for your program through your microsite, we collect and store their registration data via forms. When you [set up a microsite](https://help.impact.com/brand/advocate-program/manage-advocate-participant-experiences/microsite-experiences/set-up-a-microsite) using auto setup, a form will be created automatically. This help article explains how to set your registration form’s submission rules and map additional form fields.

#### Customize your microsite submission handling rules

You can set submission handling rules for your form so that someone on your team is notified whenever there’s a new submission attempt. This can be useful if you want to track when you receive new participants or get notified when someone attempts to register, but the submission fails. You also have the option to automatically add or remove newly updated participants from a specific user segment.

1. From the left navigation menu, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → Data Sources** → **Forms**.
2. Hover over the registration form you want to customize, then select **Edit**.
3. On the *Update Registration Form page*, scroll down to the *When the form succeeds*.
   * Choose who receives an email when someone signs up successfully.
   * Choose the user segment (if any) that the participant should be added to after registering successfully.
4. Below the *When the form fails* section, choose who receives an email when an attempted submission fails.
5. Select **Update Registration**.

#### Map registration form fields

When your microsite registration form is created, you can configure Advocate participant fields to be set to form values or static data during registration. Your microsite comes with the following default microsite form fields: *First Name*, *Last Name*, *Email*, and *Password*. You can modify the registration form to collect additional information about your microsite users, like *Phone Numbe*r, *Country/Location*, *Business Type*, etc. You can also add a terms and conditions checkbox to prompt users to accept their terms.

**Add additional fields to the registration form**

1. From the left navigation menu, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → Content**.
2. On the *Microsite* card, select **Edit content**.
   * This action opens the Microsite editor and displays the Microsite slideout.
3. Below the *Logged Out Layout* section, select **Register**.
4. In the *Component* menu, select **Add** → **Microsite Components**.
5. Select the component suited for collecting additional data, then select **Add to Additional Fields**.
6. In the *Component* menu, ensure you’ve selected the **Edit** tab, then complete the following information:
   * **Required error message:** The message displayed when a required field is missing information.
   * **Input label:** The name of the additional field that will be displayed on the registration form.
   * **Input name attribute:** The additional field’s key for mapping the additional field to user data.
   * ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-d0b6669ae76a7bef06a8d6940d7ad5c16bb8d018%2F7cb018d4face8d7cceb880eb5086c812e764fbcfe6f2a0377f88bc7576973070.svg?alt=media) **\[Toggle on]** **Optional** if it isn’t a required field.
   * From the *Input* type drop-down menu, select how the field collects information.
7. Select **Save**.

**Map the additional fields**

1. From the left navigation menu, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → Data Sources** → **Forms**.
2. Hover over the registration form you want to customize, then select **Edit**.
3. On the *Update Registration Form page*, select **Advanced Settings**.
4. Below *Advocate Participant Field*, select **Add Mapping**.
5. Select an Advocate value from the drop-down list and enter a mapping value in the *JSONata Expression(s)* text box to be evaluated at registration time.
   * **Add to Segments:** Configure specific rules for adding participants to segments after registration.

     **Example:** `($contains(email, “acme.com”) ? ($append(segments, “Existing”)))`
   * **Custom Field:** Map a custom value you want to capture on the registration form.

     **Example:** cellPhone → `cellPhone`
   * **Country:** Capture the user's country code.

     **Example:** Country → `countryCode`
   * **Locale:** The value of the locale form field named and mapped to the participant’s locale field.

     **Example:** Locale → `locale`
   * **Referred by Codes:** Capture the referrer's unique referral code.

     **Example:** `$exists(referredByCodes) AND referredByCodes != ""`
   * **Referable:** Indicate if a user can be referred or not.

     **Example:** Referable → `false`
6. Select **Update Registration** when you’re done.

   * To view your registration form submissions, refer to [View Your Registration Form Submissions](https://help.impact.com/brand/advocate-program/manage-advocate-participant-experiences/microsite-experiences/view-your-microsite-registration-form-submissions).

   <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-ab2e84593986bd90bf0644920a88b340dfb0cb25%2F43907e51e34ac11866d4f1358b2c90e787e47240246a8d9411445eee331ead4e.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>
