ActvPlatformAdncIdentifier Metadata Type in SFDX

Architectural Overview#

The ActvPlatformAdncIdentifier (Activation Platform Audience Identifier) metadata type configures the Contact Point and Identity Match Keys for an ActivationPlatform in Salesforce Data Cloud. When activating a segment of Unified Individuals to an external advertising platform or clean room, the destination platform matches audience members using deterministic identifiers—such as SHA-256 hashed email addresses (ContactPointEmail), normalized E.164 phone numbers (ContactPointPhone), Mobile Advertiser IDs (ContactPointApp / IDFA / GAID), or external subscriber IDs (PartyIdentification).

By defining ActvPlatformAdncIdentifier components on an ActivationPlatform, architects codify which contact point DMO entities, identifier subtypes, and hashing/formatting rules the platform requires to resolve audience members.

Directory and File Conventions#

In SFDX source format (apiVersion 68.0), ActvPlatformAdncIdentifier files are stored in the actvPlatformAdncIdentifiers folder.

Key Metadata Fields#

The ActvPlatformAdncIdentifier XML schema includes the following core properties:

Declarative XML and Package Manifest Examples#

The following example configures a Contact Point Email audience identifier for Enterprise_DSP_Platform:

<?xml version="1.0" encoding="UTF-8"?>
<ActvPlatformAdncIdentifier xmlns="http://soap.sforce.com/2006/04/metadata">
    <activationPlatform>Enterprise_DSP_Platform</activationPlatform>
    <activationPlatformField>DSP_Hashed_Email_Field</activationPlatformField>
    <entityName>ssot__ContactPointEmail__dlm</entityName>
    <fieldName>ssot__EmailAddress__c</fieldName>
    <identifierType>Email</identifierType>
    <masterLabel>DSP Hashed Email Identifier</masterLabel>
</ActvPlatformAdncIdentifier>

Package Manifest (package.xml)#

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>Enterprise_DSP_Platform</members>
        <name>ActivationPlatform</name>
    </types>
    <types>
        <members>DSP_Hashed_Email_Field</members>
        <name>ActivationPlatformField</name>
    </types>
    <types>
        <members>DSP_Email_Identifier</members>
        <name>ActvPlatformAdncIdentifier</name>
    </types>
    <version>68.0</version>
</Package>

SOQL Queries and CLI Automation#

Query ActvPlatformAdncIdentifier records via SOQL or deploy using Salesforce CLI:

SELECT Id, DeveloperName, MasterLabel, EntityName,
       FieldName, IdentifierType, IdentifierSubType
FROM ActvPlatformAdncIdentifier
ORDER BY MasterLabel ASC

# Retrieve all ActvPlatformAdncIdentifier components
sf project retrieve start --metadata "ActvPlatformAdncIdentifier:*"

# Deploy a specific audience identifier definition
sf project deploy start --metadata ActvPlatformAdncIdentifier:DSP_Email_Identifier

Architect Best Practices and Gotchas#

• Identity Resolution Ruleset Alignment: An ActvPlatformAdncIdentifier can only export contact points if the underlying ssot__ContactPointEmail__dlm or ssot__ContactPointPhone__dlm DMO is properly linked to ssot__Individual__dlm in your Data Cloud Data Space and Identity Resolution Ruleset.
• Phone Number Normalization: When configuring phone-based ActvPlatformAdncIdentifier components, always map ssot__FormattedE164PhoneNumber__c rather than raw unformatted phone strings so SHA-256 hashes match the E.164 normalization standard expected by Meta, Google, and DSP endpoints.

Frequently asked questions

What is ActvPlatformAdncIdentifier in Salesforce Data Cloud?

It defines the audience identity match keys—such as Contact Point Email, Contact Point Phone, Mobile Advertiser ID (MAID), or Party Identification—used to match unified profiles on an external ActivationPlatform.

Why are audience identifiers separated from standard ActivationPlatformActvAttr attributes?

Audience identifiers represent 1:M contact points (Email, Phone, Device ID) that often require hashing (SHA-256) and priority ranking during identity resolution, whereas standard attributes describe 1:1 profile properties.

Where are ActvPlatformAdncIdentifier files stored in SFDX source format?

They are stored in force-app/main/default/actvPlatformAdncIdentifiers with the .actvPlatformAdncIdentifier-meta.xml file extension.

Can an ActivationPlatform support multiple ActvPlatformAdncIdentifier records?

Yes. An ad-network ActivationPlatform commonly includes multiple identifiers—such as hashed email, hashed phone, IDFA, and AAID—to maximize match rates.