---
schema_version: "1"
id: 98f39628747914e8ade3b76b92142f4f7bf06826becd278992b7f1447c817f1b
title: Validate Your Identity System Configuration
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_pers_identity_troubleshooting_validate_config.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_pers_identity_troubleshooting_validate_config.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bb10aae3446a31660d72223773204141bfe21e0a971462583a79644ebe862727
description: Confirm and debug your identity system configuration.
products:
  - Marketing
  - Salesforce Personalization
release: "264"
---
# Validate Your Identity System Configuration

Confirm and debug your identity system configuration.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </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="d76914e38">Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d76914e38 ">To configure the identity system:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d76914e38 ">A role with Administrator permissions</td>

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

1. To confirm that the correct namespace is set, from the main navigation, select **Settings** | **Identity Types**. The **Identity Namespace** field at the top right of the page shows your dataset ID.
2. If the **Identity Namespace** field is blank, contact Salesforce Customer support to help you add it.
3. To verify that attributes match the correct Identity Types, select **Settings** | **Attributes**.
4. In the Attributes table, review each attribute’s Identity Type setting.
5. To confirm events, select **Reports** | **Event Stream**.
6. In the Event Stream Report, make sure that events are sent in the proper format and that identity values are passed to the correct attributes. For more information, see the Developer Documentation [User Identity Mapping](https://developer.salesforce.com/docs/marketing/personalization/guide/user-identity-mapping.html?q=identity) and [Serverside Event API Requests](https://developer.salesforce.com/docs/marketing/personalization/guide/event-api-requests.html).
7. Verify that ETL formatting is correct. For more information, see [User ETL Data Feed](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_etl_user_data_feed.htm&release=264.0.0&type=5 "Use the User ETL data feed to update Unified Custom Profiles, and Unified Account Profiles if you have B2B Detect. Personalization stores user profiles for each anonymous and known user in the system.").
    1. Confirm that your ETLs are sent in the correct format to the correct attribute and that ETL formatting overall is correct.
    2. Make sure that column headers are formatted correctly for your identity attributes and they’re in line with the expected column of data.
8. If configured for your system, confirm that the Channel Identity Type is being used correctly. To check the identity type for each channel, see these setup help topics for the channels used in your system: [Mobile](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_identity_mobile_apps.htm&release=264.0.0&type=5 "Use the Personalization identity system to identify and merge user profiles in your mobile app."), [Serverside](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_identity_event_api.htm&release=264.0.0&type=5 "With Personalization’s identity system, you can configure the identifiers in the Event API to create Unified Customer Profiles for each of your customers. To merge user profiles from various sources, you designate an identity type to use when matching users between the Event API and Personalization. You can use multiple identifiers in the Event API."), [Web](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_identity_web_sdk.htm&release=264.0.0&type=5 "To create unified customer profiles for each of your customers, use Personalization’s identity system to configure the identifiers in the Marketing Cloud Personalization module of the Salesforce Interactions SDK. To merge user profiles from various sources, you designate an identity type to use when matching users between channels. You can use multiple identifiers in a web event."), [Email](https://help.salesforce.com/s/articleView?id=mktg.mc_pers_identity_open_time_email.htm&release=264.0.0&type=5 "To create unified customer profiles for each of your customers, use Personalization’s identity system to configure the identifiers in your Open Time Email campaigns. To merge user profiles from various sources, you designate an identity type to use when matching users between your email service provider and Personalization. You can use only one identity type. If you send multiple identifiers in an Open Time Email campaign, Personalization ignores all but the designated identity type.").
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_personalization-264-0-0-production-enus/16bf1f60-f44c-4260-a56e-f052cfe515a3/images/icon_note.png)
    
    Note Channel Identity Type is a dedicated identity type set for each channel. This identity type identifies a known user for the specified channel. By default, the identity type for each channel is set to the built-in `customerId` identity. Changing the channel identity type after collecting data with a previous identity can corrupt data and affect user merging.
9. If your implementation uses Channel Identity Type, make sure that your sitemap and event sources from other channels use the identity type correctly.
    
    Send the value for the Channel Identity Type in events as `user.id`. For example, if the Channel Identity Type for a web integration is configured to be `customerId`, the sitemap for this integration must map the value for `customerId` to `user.id`.