---
schema_version: "1"
id: bae0e616e669f5a717be34ce85bc7768ce6ecd954f48604dd499313a58498c20
title: Unified Individual for Activation Membership
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_unified_profile_activation.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_unified_profile_activation.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 485fdb63f7e54666249c599800f90bc5e3e3daf14459546cd3724c8590a131fd
description: To take advantage of identity resolution, use the Unified Individual data model object (DMO) as the Activation Membership. With identity resolution, you combine data from disparate data sources to create one Unified Individual. When selecting Unified Individual as the DMO, the Individual ID attribute is included and not the Unified Individual ID.
products:
  - Data 360
release: "264"
---
# Unified Individual for Activation Membership

To take advantage of identity resolution, use the Unified Individual data model object (DMO) as the Activation Membership. With identity resolution, you combine data from disparate data sources to create one Unified Individual. When selecting Unified Individual as the DMO, the Individual ID attribute is included and not the Unified Individual ID.

## Contact Points for a Unified Individual

If you have data from multiple data sources in Data 360, use Unified Individual as the Activation Membership. Selecting Individual instead of Unified Individual as the Activation Membership can result in duplicate entries in your count. When any DMO besides Unified Individual is selected as the Activation Membership, Data 360 includes all contact points associated with the object.

Data 360 activates one row for a Unified Individual. Unified Individual includes different fields depending on which contact point channel you select.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d40740e55">Contact Point</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d40740e58">Field</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Contact Point" class="slds-cell-wrap" style="vertical-align:top;" headers="d40740e55 ">Email Address</td>

            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d40740e58 ">
              <ul>
                <li>Subscriber key</li>

                <li>Contact email address</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Contact Point" class="slds-cell-wrap" style="vertical-align:top;" headers="d40740e55 ">Phone Number</td>

            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d40740e58 ">
              <ul>
                <li>Subscriber key</li>

                <li>Contact phone number</li>

                <li>Phone country code</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Contact Point" class="slds-cell-wrap" style="vertical-align:top;" headers="d40740e55 ">MobilePush</td>

            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d40740e58 ">
              <ul>
                <li>Subscriber key</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Contact Point" class="slds-cell-wrap" style="vertical-align:top;" headers="d40740e55 ">WhatsApp</td>

            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d40740e58 ">
              <ul>
                <li>Subscriber key</li>

              </ul>
            </td>

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

If contact points come from multiple sources, Data 360 selects the contact points you prioritized in source selection. If there are multiple contact points for a single source, the contact point with the highest Einstein engagement score is selected. If the score isn't available or has the same score, the lowest alphanumeric ID is selected.

#### See Also

- [_Salesforce Help_: Identity Resolution Match Rules](https://help.salesforce.com/s/articleView?id=data.c360_a_match_rules.htm&release=264.0.0&type=5 "Match rules tell Data 360 which profiles to unify during the identity resolution process. Each match rule contains one or more criteria. Profiles are matched when all criteria within a match rule are satisfied.")