Help Center

Menu

CDP Advanced Forms destination

The Advanced Forms destination automatically populates form fields with user data from the CDP Single Customer View (SCV). This reduces repetitive data entry for users who have existing SCV profiles.

For information on how to capture form responses into the SCV, see the Advanced Forms Answer Capture documentation.

Why use the Advanced Forms destination

Modern websites often rely on multiple form applications—such as registrations, inquiries, service requests, onboarding, applications, and surveys. Without a connected data approach, users are frequently asked to re-enter the same information.

The CDP Advanced Forms destination pulls consented profile information into supported form applications.

Key benefits

  • Repetitive fields are pre-filled with known user data.

  • Form completion requires fewer manual inputs.

  • Behavior is consistent across different form tools.

  • Data is used in accordance with user consent.

  • A standardized prefill mechanism removes the need for custom development.

  • Field mappings are managed through a self-service schema interface.

Prerequisites

Before creating a destination, you must:

  1. Generate API credentials in your Advanced Forms instance.

    Read the Advanced Forms API credentials documentation for instructions.

  2. Configure the Advanced Forms extension in the Squiz DXP Console.

    The CDP automatically detects the presence of the Advanced Forms extension. If the extension is not configured, you will be prompted to set it up before you can create a destination.

Create a new destination

A Destination in the CDP defines an endpoint where customer data can be sent or synchronized.

  1. From the CDP left-hand navigation, click Destinations.

  2. Click ➕ Create destination.

    The ➕ Create destination dialog presents.

  3. Enter a unique and descriptive name in the Name field.

    For example, Website Contact Form Prefill.

  4. Select Advanced Forms from the Type menu.

  5. Click Create.

    When the destination is created, a success alert presents and the management page for the new destination loads.

Import form attributes

Once the destination is created, import the structure of your Advanced form so the CDP knows which fields are available for mapping.

  1. On the destination page, click Import from Advanced Forms.

  2. A two-step import process begins. You must copy information from the Form Publishing section in your Advanced Forms instance.

  3. In Advanced Forms: Navigate to Form Publishing  Smart JavaScript.

  4. Copy the entire contents of the first text field.

  5. In the CDP: Paste this code into the first field of the import wizard and click Next.

  6. In Advanced Forms: Copy the embed code from the second text field.

  7. In the CDP: Paste the embed code into the second field of the import wizard and click Import.

The CDP processes the codes and fetches the available questions/fields from your form.

Map CDP attributes to form fields

This step links user profile data to your form questions.

  1. Once the import is complete, the mapping interface presents.

  2. On the left, locate the available Single Customer View (SCV) profile attributes (for example, firstName, lastName, email).

  3. On the right, locate the questions imported from your form.

  4. Select the corresponding SCV attribute from the dropdown list for each form question you want to prefill.

  5. If a form question should not be prefilled, leave it unmapped or select the Ignore option.

  6. After mapping all required attributes, click Save.

Grant data access in the SCV schema

For the prefill to function, the system needs explicit permission to read data from a user’s profile and display it on the frontend.

  1. Navigate to the SCV Schema configuration area in your CDP.

  2. For every SCV attribute you mapped in the previous step, ensure that the customer role has been granted read access.

  3. If read access is not granted, the CDP cannot retrieve the value for that attribute, and the corresponding form field will not be pre-populated.

    The SCV schema is a security and governance layer for customer data. Denying read access for sensitive attributes prevents them from being inadvertently exposed.

    Permissions are set using x-scv-permissions in the schema configuration. Read the SCV Schema documentation for more details on schema structure and permissions.