Help Center

Menu

Testing and verification

This guide explains how to test and troubleshoot the CDP and Advanced Forms integration.

Testing the integration

To verify the integration is working correctly:

  1. Open a new browser window.

  2. Sign in to your website’s portal as a user who is using Portal Auth and has a complete SCV profile (that is, they have values for the attributes you mapped, such as first name, email, and address).

  3. Navigate to the content page where you embedded the form.

  4. Verify the prefill

    The following form fields should be automatically populated with the data from the logged-in user’s profile:

    • First name.

    • Last name.

    • Email.

    • Any other mapped attributes.

Troubleshooting and edge cases

The form prefill is designed to fail silently to avoid disrupting the user experience. Prefill cannot occur in the following situations:

  • Anonymous users: The user is neither logged into the portal nor has a matched marketing profile in CDP SCV.

  • Portal Auth not used: The user is not using Portal Auth for authentication.

  • No SCV profile: The logged-in user does not yet have an SCV profile in the CDP.

  • Empty attribute value: The user has a profile, but the specific attribute being mapped (for example, phoneNumber) is empty for that user.

  • Form structure changes: If a form question configured for prefill is later deleted from the form in Advanced Forms, or new questions are added to the form after the initial setup.

    In the case of form structure changes, CDP administrators who return to the destination’s mapping interface will see the latest version of the form’s questions.

  • Any mappings connected to deleted questions will be automatically removed, and new questions will appear as unmapped.

    You will need to re-save the mapping configuration to apply any changes.

Common configuration errors

The following configuration errors can cause prefill to fail:

  • Mismatched attribute names: The attribute name in the SCV response does not match the attribute name used in the form mapping.

    For example, the SCV response may use email while the form mapping expects emailAddress.

    Ensure attribute names match exactly between the SCV schema and the form mapping configuration.

  • Invalid JSON schema deployment: Permissions are not correctly set within the schema using x-scv-permissions.

    If permissions are not correctly configured using x-scv-permissions, the JSON schema deployment may be invalid and prefill will not function.

    Review the SCV schema configuration to ensure all mapped attributes have proper x-scv-permissions settings for the customer role.