To use Data 360 Data Governance features for Marketing Cloud Engagement, you need to grant access to the impacted objects according to an access policy.
You can use attribute-based access control (ABAC) or role-based access control (RBAC), giving you more granular control over your users' access to data. To assign these objects to an available policy, grant access to Data 360 objects.
Associated Data 360 Objects
Note Marketing Cloud Engagement appends the Enterprise ID (EID) or Member ID (MID) to stream
names.
| Object Type | Associated Bundle | Name |
|---|---|---|
| Data Lake Objects (DLOs) | Common bundle across channels | SFMC Campaign |
| SFMC Einstein Email Scores | ||
| SFMC Journey | ||
| SFMC Journey Activity | ||
| SFMC Journey Activity Run | ||
| SFMC Subscriber | ||
| Selectable outside of channels | SFMC Subscriber BU Mapping | |
| MCE Email Bundle | SFMC Contact Point Email | |
| SFMC EES Email Snapshot | ||
| SFMC Einstein Email Scores | ||
| SFMC Email Bulk Message | ||
| SFMC Email Complaint | ||
| SFMC Email Engagement Bounce | ||
| SFMC Email Engagement Click | ||
| SFMC Email Engagement Not Sent | ||
| SFMC Email Engagement Open | ||
| SFMC Email Publication | ||
| SFMC Email Engagement Send | ||
| SFMC Email Template | ||
| SFMC Email Unsubscribe | ||
| SFMC Ent Profile Attribute | ||
| MCE Mobile Connect Bundle | SFMC Contact Point Phone <MID> | |
| MCE Mobile Connect Bundle 1.0 | SFMC Message Engagement Event <MID> | |
| MCE Mobile Connect Bundle 2.0 | SFMC SMS Bulk Message <MID> | |
| SFMC SMS Delivery Receipts <MID> | ||
| SFMC SMS Inbound Message <MID> | ||
| SFMC SMS Inbound Rsp Click <MID> | ||
| SFMC SMS Outbound Click <MID> | ||
| SFMC SMS Outbound Message <MID> | ||
| SFMC SMS Subscription <MID> | ||
| SFMC SMS Template <MID> | ||
| MCE Mobile Push Bundle | SFMC Contact Point App <MID> | |
| SFMC Einstein Push Scores <MID> | ||
| SFMC EES Push Snapshot <MID> | ||
| SFMC Push Template <MID> | ||
| MCE Mobile Push Bundle 1.0 | SFMC Push Engagement Event <MID> | |
| SFMC Push Undeliver Event <MID> | ||
| MCE Mobile Push Bundle 2.0 | SFMC Push Application Cache <MID> | |
| SFMC Push Bulk Message <MID> | ||
| SFMC Push Display <MID> | ||
| SFMC Push Fence Entry <MID> | ||
| SFMC Push Fence Exit <MID> | ||
| SFMC Push Message Tracking Supplemental <MID> | ||
| SFMC Push Open <MID> | ||
| SFMC Push Tracking <MID> | ||
| MCE WhatsApp Bundle | SFMC Contact Point WhatsApp <MID> | |
| SFMC WhatsApp Bulk Message <EID> | ||
| SFMC WhatsApp Message Template <MID> | ||
| SFMC WhatsApp MO Event <MID> | ||
| SFMC WhatsApp Send Event <MID> | ||
| SFMC WhatsApp Tracking Event <MID> | ||
| Data Model Objects (DMOs) | Shared bundle across channels | Affiliation |
| Campaign | ||
| Individual | ||
| Market Journey | ||
| Market Journey Activity | ||
| Marketing Journey | ||
| Party Identification | ||
| Selectable outside of channel bundles | Market Journey Activity Run | |
| MCE Email Bundle | Contact Point Email | |
| Einstein Email Engagement Scores | ||
| Email Engagement | ||
| Email Publication | ||
| Email Template | ||
| Engagement Topic | ||
| MCE Mobile Connect | Communication Subscription Consent | |
| Contact Point Phone | ||
| Message Engagement | ||
| SMS Template | ||
| MCE Mobile Push | Contact Point App | |
| Device | ||
| Device Application Engagement | ||
| Device Application Template | ||
| Einstein Push Engagement Scores | ||
| MCE WhatsApp | Contact Point OTT Service | |
| Message Template |
If you have more than one data space, grant access to objects in each data space. Object names in non default data spaces follow the convention of <DataSpace Prefix>_<Object Name>.