---
schema_version: "1"
id: 47b2f38a0dfb9e822e07395b922494aae504d0a9650a0cb8996c8c8936a1948f
title: Add Progressive Profiling and Turn On Pre-Fill for Forms
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mktg_content_forms_add_progressiveprofilingrules.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mktg_content_forms_add_progressiveprofilingrules.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8b32b8423db5beabd3f35d227e11595b9999b4c47b75f78996a4c37012479509
description: Use progressive profiling to dynamically show new fields to returning users based on previously gathered information. Turn on pre-fill to automatically provide known profile values in mapped fields when a form loads, which helps reduce friction for your users. Progressive profiling and pre-fill require that you associate a read data provider with the form.
products:
  - Marketing
release: "264"
---
# Add Progressive Profiling and Turn On Pre-Fill for Forms

Use progressive profiling to dynamically show new fields to returning users based on previously gathered information. Turn on pre-fill to automatically provide known profile values in mapped fields when a form loads, which helps reduce friction for your users. Progressive profiling and pre-fill require that you associate a read data provider with the form.

### Required Editions

[View supported editions](https://help.salesforce.com/s/articleView?id=mktg.mktg_editions.htm&release=264.0.0&type=5 "Marketing Cloud Next is available in Growth and Advanced editions, and requires Salesforce Enterprise or Unlimited editions. Some features are limited by edition or purchased add-on. All functionality is available in Lightning Experience only.").

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d35763e49">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d35763e49 ">To create or edit a form:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d35763e49 ">
              <p>Marketing Cloud Manager permission set</p>
              <p>AND</p>
              <p style="margin-bottom:0;">Any CMS workspace
                contributor role</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d35763e49 ">To publish or unpublish a form:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d35763e49 ">
              <p>Marketing Cloud Manager permission set</p>
              <p>AND</p>
              <p style="margin-bottom:0;">A CMS workspace contributor
                role of content</p>
            </td>

          </tr>
        </tbody>
      </table>

## Add a Data Source to Your Form

Before you can add progressive profiling rules or turn on pre-fill, you must connect your form to a read data provider.

1. Open your form in the editor.
2. On the Data Sources tab, click **Manage Data Sources**.
3. Select the read data provider that you want to use, and choose its data source—a data graph, a marketing object, or a Prospect object.
    
    When you add the form to a landing page, make sure that the landing page uses the same data graph. If a returning visitor can’t be identified—for example, because their identity token expired—the form shows its default fields instead of the progressive profiling variation.

## Add a Progressive Profiling Rule

Create rules to control when a field appears to a user. For example, show a Business Phone field only when the Email field already has a value in the read data provider.

1. In the form editor, select the field that you want to make conditional.
2. In the properties panel, click the **Rules** tab.
3. Under Progressive Profiling Rules, click **New Rule**.
4. In the Add progressive profiling rule window, set the conditions that determine when the field appears.
    
    You can’t add a rule to a hidden field. To unhide a field, on the Setting tab, deselect **Always Hide**. You also can’t hide a field that has a profile rule. You can’t apply a progressive profiling rule to a related object.
5. Save your work.
    
    If you change the read data provider or its data source, all connections for the progressive profiling rules that were associated with the previous data source are removed. Delete the invalid rules and create new ones.

## Pre-Fill Fields with Profile Data

Turn on pre-fill to populate fields with known user data. For example, when a returning user opens a form, their First Name and Last Name are already filled in.

![Warning](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mktg_all-264-0-0-production-enus/e92be4e1-4bef-47a5-a11d-95f4ea1f7d7a/images/icon_warning.png)

Warning Avoid pre-filling fields that contain personally identifiable information, such as Social Security numbers or credit card numbers.

1. In the form editor, select the field for which you want to turn on pre-fill.
2. In the properties panel, under Pre-Fill, click **Select Pre-Fill Attribute**.
3. Select the data source and attribute to map to the field.
    
    For example, to pre-fill a Last Name field, select the Last Name attribute from the Primary Objects list of your recipient data graph. To pre-fill from a marketing object or a Prospect object instead, select that data source, and then select its attribute. Pre-fill attributes are namespaced by data source, such as `dataGraph.LastName`, `myObject__mo.LastName`, or `prospect.LastName`.
4. Review the attribute and resource path, which are populated from your selection.
5. Enter a merge field API name that identifies the attribute for content creators and appears in the API.
6. (Optional) Enter the default text that appears for the merge field when no profile value is found for the user.
    
    If the read data provider’s data source changes or a returning visitor can’t be identified—for example, because their identity token expired—the field shows this default text instead of a pre-filled value.
7. Click **Done**.
8. Save your work.