Additionally, consider:

• Fully imported programs, such as Digital and Conversations.

• Combining separate surveys (for example, Personalized and Anonymous surveys) into the same program.

• Installed Apps.

Map out the Condition strings that define each of the programs. To do so, consider the answers for these questions:

• What combination of field values are unique to records within this program?

• What combination of field values would not be possible for records within this program?

• Do these combinations of field values correspond to Condition strings on my Email inviters, Email templates, Design rules, and Surveys?

Check the inferred Condition string relationships against the draft on the Identify the program step. These relationships are derived from field values in Auto Importers, Anonymous surveys, and from real field values on records in Experience Cloud. If the Experience program migration tool has inferred incorrect relationships or missed some, manually edit them on the text box. Note that each condition string implies that all the parent condition string are always true. For example:

e_record_type = 'B2B'
    e_survey_program = 'B2B Relationship'
    e_survey_program = 'B2B Onboarding'

When the Condition string relationships are accurate, click Save. The Condition string relationships can be only be saved once, but you may need to make small edits to it if you see more or less items for a given asset (for example, extra survey email). Click View changelog to see the lists of changes for that field dependency. See Change Log for more information.

Enter the Condition string. You can select the Feedback fields (E-fields) the Experience program migration tool has detected. Click the condition value (of Enum Content Kind) to write the condition. Note that the options available come from Survey conditions tab in the Condition String Relationship screen.

Unselect any Auto Importers and surveys you do not need. For example, in the image above you might unselect the Test Auto Importer.

Click Load Fields. Experience Cloud generates a list of the fields available to be used in contacts, events, and feedback schemas. All fields are listed in one of the following tables:

• Event and Feedback fields — The E-fields and Q-fields from the Auto Importers, Surveys, and Case Form you selected. These fields contain data and, when mapped to Contact fields, provide the information displayed in profiles.

• Contact fields — The fields available to be used in Customer Profiles. This table always includes the following five fields, which begin unmapped: External Customer ID, Email, First Name, Last Name, and Phone.

The Event and Feedback fields table does not include K-fields. To add one or more K-fields to the list:

1. Click Add K-fields.

2. Select the K-fields you want to add.

3. Click Add/Remove selected.

For Contact fields to display data in profiles, they must be mapped to fields in the Event and Feedback fields table:

1. In the Event and Feedback fields table, locate the field you want to map to a contact field. Click Search to make location easier by adding search fields to the top of each column.

2. In the Type column, click the small arrow to open the Map to Contacts dialog. For example:

   

3. Either select an Existing Field in the Contact fields table for the mapping, or select New Field to create a new row in the Contact fields table, mapped to this Event or Feedback field. For example, the following image shows the Map to Contacts dialog, with the e_email Event field mapped to the Email contact field:

   

4. Click Map. Repeat these steps until your Contact Fields table has all of the mappings needed by your profiles.

5. Optionally for any Contact field, change the values for IsPii (which marks the field as personally-identifying information), IsIdentity (which marks the field as identifying information), and IsIndexed (to mark the field for indexing).

   Restriction: Mark no more than five fields as IsIndexed.

   Warning: After you create a schema with a field marked as identifying information, you cannot remove that field.

   Important: As of iOS15, Apple devices obfuscate the user’s IP address when using the Mail app. If the only customer identifier (IsIdentity) configured in the schema is for the customer email address, multiple profiles might be created for the same user. To avoid this, always configure at least one other identifier besides email address.

Before proceeding, verify that you have completed all of the following tasks:

• Map all contact fields (unmapped fields are grayed out), and verify the isPii, isIdentity, and isIndexed settings for all Contact fields.

• Categorize all event and feedback fields correctly.
• Mark as Ignore any event and feedback fields that should be unavailable in customer profiles.
• Add all necessary K-fields.
• Configure the Event area, especially the Event Name and Event Timestamp.
• Configure the Feedback area.
• Configure a Backfill Rule.

On the production instance, grant the appropriate permissions to the roles that will use Customer profiles:

1. On the Company > Users > Roles > Roles screen, for any role that will view customer profiles, move the View Invitation Management capability to the right-side box of the MemberCaps property. This is required for users to see non-responded records in the Contact Timeline.

2. For roles that will create Customer profiles in Admin Suite, assign the Manage Reports and Controls administrative permission, as described in Reports and Preferences. This permission works only for users' primary role.