---
schema_version: "1"
id: 564759599df2caa8265954fafb8b3380f500b6c950838089cb4df96ba789d688
title: Journey Decisioning Subscriber Key Resolution
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mceplus_jd_subscriber_key_resolution.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mceplus_jd_subscriber_key_resolution.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1068da2dc12f9b84e593654400a5f861560ea7177d4255dce0ec03fa10d5df3b
description: This content describes the behavior of specific Agentforce actions related to the Marketing Cloud Engagement inputs, particularly focusing on the crucial step of resolving customer identifiers.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Journey Decisioning Subscriber Key Resolution

This content describes the behavior of specific Agentforce actions related to the Marketing Cloud Engagement inputs, particularly focusing on the crucial step of resolving customer identifiers.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Enterprise and Unlimited Editions with Marketing Cloud Next</td></tr></tbody></table>

<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="d16184e52">User Permissions Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e52 ">To build an agent in Marketing Cloud Next</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e52 ">
            <p>Manage AI Agents AND</p>
            <p style="margin-bottom:0;">Manage Agentforce Employee Agents</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e52 ">To set up and configure data in Data Cloud</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e52 ">Data Cloud Architect</td>

        </tr>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e52 ">To use Agentforce in Journey Builder in Marketing Cloud Engagement</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e52 ">Marketing Cloud Engagement+, access to Data Extensions, Journey Builder, and
            optionally, Automation Studio</td>

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

The Select Journey and Create Journey Content agent actions accept either a `subscriberKey` or a `UnifiedIndividualId` as input. The action records these values in its respective data extensions. The subscriber key is essential for deriving value and successfully sending messages in Marketing Cloud Engagement. Although both inputs are accepted, both are not required.

Think of the Unified Individual ID as a new universal keycard that works across the entire Salesforce campus, but the subscriberKey is the specific door key required to enter the Marketing Cloud Engagement building. If you only present the keycard but not the specific door key, the system tries to find the matching door key based on the general keycard data, ensuring you get access to Marketing Cloud Engagement if a connection exists in the data streams.

To streamline action execution, the system attempts to resolve the necessary subscriberKey when a Unified Individual Id is provided, but the subscriberKey is missing. This resolution relies on the data following the standard Marketing Cloud Engagement Contact Mappings and Data Lineage Fields practices established through SFMC Data Streams.

## SubscriberKey Resolution Logic

The system determines the subscriberKey using this prioritization:

<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="d16184e128">Scenario</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d16184e131">Resolution Logic</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Scenario" class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e128 ">Subscriber key is provided by the utterance</td>

            <td data-label="Resolution Logic" class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e131 ">The action uses that value directly, even if a Unified Individual ID is also
              provided.</td>

          </tr>
          <tr class="">
            <td data-label="Scenario" class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e128 ">A Unified Individual ID is provided, but there’s no subscriber key</td>

            <td data-label="Resolution Logic" class="slds-cell-wrap" style="vertical-align:top;" headers="d16184e131 ">
              <p>The system attempts to resolve the key by querying your SFMC Data Streams.</p>
              <ul>
                <li>The system queries the SFMC subscriber data stream sourced data.</li>

                <li>If no match is found, the system checks the Email Profile data stream sourced
                  data.</li>

                <li>If a match is still not found, the action continues execution without a
                  subscriber key.</li>

              </ul>
            </td>

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

![Diagram of subscriber key logic](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mceplus_agentforce_JD_subscriberkey_diagram.jpg)

## Template Query

Run a SQL query in the Data Cloud Query Editor to verify whether records can be found for a unified individual. The SourceRecordId\_\_c is the subscriber key.

```
SELECT "UnifiedRecordId__c", "ssot__DataSourceId__c", "ssot__DataSourceObjectId__c", "ssot__InternalOrganizationId__c", "SourceRecordId__c" 
FROM "{UnifiedLinkIndividual DMO Name}"
WHERE "UnifiedRecordId__c" = '{UnifiedIndividual ID}'
AND (
 	"ssot__DataSourceObjectId__c" LIKE '%SFMC_{SFMC EID}_Subscriber%'
  	OR "ssot__DataSourceObjectId__c" LIKE '%SFMC{SFMC EID}_EmailProfile%'
)
```

In the Query Editor, use the Unified Link Individual object for your query context.

![Drag and drop the Unified Link Individual object to the query context window.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mceplus_agentforce_JD_data_query.jpg)

Copy and paste the SQL query in the query window. Replace the UnifiedLinkIndividual DMO Name and UnifiedIndividual ID in the SQL query. Click Run the query. The results appear below the SQL window.

![Copy and paste the SQL in the query window and run the query.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_marketing_cloud_overview-264-0-0-production-enus/2555afdb-8049-4e3c-8043-0e04803e5f16/mc_marketing_cloud_overview/images/mceplus_agentforce_JD_data_query_sql.jpg)