You are here:
Contact Points and Source Priority Order
Contact point selection determines which objects and fields are included in an activation and sent to an activation target. Use the source priority order to determine which contact point value is selected for the activation.
You can include these contact points when creating an activation. Each activation target type can receive different contact points. For contact point values to be sent to an activation, certain data model object (DMO) fields must contain your contact point values.
To add contact points to your activations, first complete all required data stream mappings and add the data model relationships. For more information, see Data Mapping Requirements.
To learn how to model and map digital identifiers to the ContactPointDigitalId DMO to successfully use the activation toolkit for external platforms, see Ingest and Model Digital Identifiers for JSON-based External Activation Targets.
| Contact Point | Description | Supported Platforms (Activation Targets) | Required Mappings and Relationships | Required Fields |
|---|---|---|---|---|
| Phone Number | Selecting phone as a contact point adds attributes related to phone for your activation. |
|
Contact Point Phone.Party→ Individual.Individual Id (ManyToOne) | Contact Point Phone:
The Country code has to be in ISO 3166 two-letter format for Marketing Cloud Engagement. For example, US–United States and JP–Japan. |
| Email Address | Selecting email as a contact point adds attributes related to email for your activation. |
|
Contact Point Email.Party →Individual.Individual Id (ManyToOne) | Contact Point Email:
|
| Mobile App (MobilePush) | Selecting MobilePush as a contact point adds attributes related to mobile apps for your activation. |
|
Contact Point App.Party → Individual.Individual Id (ManyToOne) | Contact Point App:
|
| Mobile Advertiser ID (MAID) | Selecting MAID as a contact point adds attributes related to MAID as attributes for your activation. |
|
|
Contact Point App:
Device:
The OS Name field value must be iOS or Android. Values aren’t case-sensitive. |
| Over-the-top (OTT) ID | Selecting OTT as a contact point adds attributes related to OTT as attributes for your activation. |
|
|
Contact Point App:
Device:
The OS Name field value must be RokuOS, AndroidTV, tvOS, FireOS, Tizen, SmartCast, or WebOS. Values aren’t case-sensitive. |
| Selecting WhatsApp as a contact point adds attributes related to WhatsApp for your activation. |
|
Contact Point OTT Service.Party → Individual.Individual Id (ManyToOne) | Contact Point OTT Service:
The Country code has to be in ISO 3166 two-letter format for Marketing Cloud Engagement. For example, US–United States and JP–Japan. |
|
Contact Point Digital Id This contact point doesn’t appear on the Channel Selection page. After you add attributes from the Contact Point Digital Id DMO, it's displayed in the Contact Point Filter section when creating or updating an activation. |
Selecting Digital ID as a contact point adds attributes related to the digital ID for your activation. |
|
Contact Point Digital Id.Individual → Individual.Individual Id (ManyToOne) | Contact Point Digital ID:
|
Source Priority Order
Use source priority order to determine which contact point value is selected for an activation when multiple values are available. Also, to reorder which contact point value is selected for segment members with data from multiple sources. You can change the priority by adding, reordering, or deleting sources.
All contact points remain part of the Unified Individual DMO after unifying your source data in Identity Resolution. Identity Resolution reconciliation rules only reconcile fields for the unified individual object, not unified contact point objects. Use source priority to make sure that you deliver a contact point from your desired data source to your activation target regardless of your reconciliation rules. If the Email Type didn't select Any, then the Primary Flag must be mapped on the corresponding contact point DMO for contact points to match.
| Value | Description |
|---|---|
| Primary | If the Primary Flag field is mapped in Data Streams, Primary is listed as an option. |
| Any | If the Primary Flag field isn’t mapped, the activation retrieves a contact point value from any available source. |
| Personal | If the For Personal Use field is mapped in Data Streams, Personal is listed as an option. The value for the For Personal Use field must be 1. |
| Business | If the For Business Use field is mapped in Data Streams, Business is listed as an option. The value for the For Business Use field must be 1. |
To use values only from specific sources in your activation, delete Any Source and Any Type for the source priority order. Expect the population count of your activation to be lower because you’re selecting values from fewer data sources.
Default Source Priority Order
Each platform has a default source priority order. For external platforms, the creator of the platform determines the default source priority order. For B2C Commerce Cloud and MobilePush, the default source priority order is always the same and can’t be changed.
| Platform | Priority | Source | Type |
|---|---|---|---|
| Marketing Cloud Engagement (Phone, Email, and WhatsApp) | 1 | Marketing Cloud Engagement | Primary |
| 2 | Any | Any | |
| Marketing Cloud Personalization (formerly Interaction Studio) | 1 | Marketing Cloud Personalization | Primary |
| 2 | Marketing Cloud Engagement | Primary | |
| 3 | Any | Any | |
| Cloud File Storage (Amazon S3, SFTP, Google Cloud Storage, Microsoft Azure) | 1 | Any | Any |
| MobilePush (in Marketing Cloud Engagement) | 1 | Marketing Cloud Engagement | Primary |
