[B2B Edition]{class="badge informative"} [B2P Edition]{class="badge positive"}

Activate account audiences

The functionality to activate account audiences to destinations is available for companies purchasing the Business-to-Business and Business-to-Person editions of Real-Time Customer Data Platform.

This article explains the workflow required to export account audiences from Adobe Experience Platform to your preferred destination.

Supported destinations supported-destinations

Go to Connections > Destinations, and select the Catalog tab. Use the Data types filter and select Accounts to see the destinations which support the activation of account audiences. Currently, exporting account audiences is available only to certain cloud storage destinations (Amazon S3, ADLS Gen 2, Azure Blob Storage, Data Landing Zone, and SFTP) and the (Companies) LinkedIn Matched Audiences destination.

Destinations which support account audiences.

Video overview

View the video below for an overview of creating and activating account audiences, and the supported use cases when activating account audiences.

Hi, I’m Margaret Trinh, Senior Product Manager. Today I’ll be sharing with you more about the XDM Business classes and field groups. In this video, we’ll discuss the data structure of XDM Business classes and field groups, understand identity namespaces and the relationship between entities and how to create namespaces, schemas and set those relationships. Let’s first learn about the XDM Business classes and field groups. Its development was driven by industry standards of important B2B entities and the common property that all schemas would include. On top of the classes, we have field groups, which are a reusable component used to define one or more fields, which ultimately expands the schema by extending the class. To get a better understanding of how the classes and field groups are put together to make a schema, this table describes the recommended composition of business classes and field groups along with the description to learn about each schema. Notice that some classes can have no additional field groups, just one or multiple. If you’re including custom attributes, you’ll include your custom field group to the related class. In addition, we leveraged the XDM experience event, also used for B2C scenarios, With field groups that are specific to Marketo standard activity types. This list will continue to expand to support the dozens of Marketo, Salesforce and Dynamic standard activity types, but this shows what we support for now. Now, onto identity namespaces. Namespaces are created to differentiate between identities ingested from various sources and data sets. The creation of a namespace includes a name, identity symbol and identity type. Customers have access to an automated script that can be executed through postman. The script will generate all the required B2B namespaces and schemas for you to get started. This will be demonstrated in the video later on. As part of the B2B edition of real-time customer data platform, we are introducing a new account entity. Account records come through that real-time customer data platform from a number of different sources. So we’ll be leveraging the unified identity service to stitch these various account records together to build an account profile. Similar to the individual profile. And to associate accounts to the familiar people entity, it’s important to know that people have a many-to-many relationship to accounts. These account IDs appear as an array on the profile. Another set of entities we’re introducing are marketing lists and campaigns. These are both important concepts in Marketo, Salesforce and Microsoft Dynamics. So it’s helpful to understand when to use which. Campaigns, otherwise known as programs in Marketo, are a list of leads or contacts used to manage marketing engagements and activities. On the other hand, we have marketing lists, also known as a static list in Marketo. These are a list of leads built by the end-user. Between these many entities, we need to set up relationships within the schema. Relationships are used to define each identity within a schema and how they relate to other entities, such as people and accounts or accounts and opportunities. As you’ll see in the demo shortly, you will associate the identity field with its reference schema and its identity namespace, along with labels for these relationships.
Now that you have received an intro, let’s see all of this in action.
Let’s start out by looking at our list of new XDM Business classes and field groups, that have been provisioned for us. By navigating to the schemas tab, under data management on the left hand side, you can first start out by searching for your classes. Enter in a term such as XDM Business, and you’ll be presented with the eight new classes that you can use to start building out your schema. Feel free to click into any of the classes, to see data structure and attributes within each class. Now, going back to schemas, if you also click on to the field groups tab and again, search for the term XDM Business, you’ll see a subset of a new field groups that you can use. Again, feel free to click into any of these field groups, to see an example of the properties and fields within each field group. Others that didn’t appear in the list are either not B2B specific, such as XDM Experience Events or the field groups related to those experience events, such as visit web page, which you can really search for, or add to opportunity.
And again, feel free to click into any of these. These are just some of the standard Marketo activity types that are extended via field groups to work with the XDM Experience Event.
Now, if we navigate over to the menu item called identities, we also have addition of new identity namespaces, which are used to differentiate between identities that get ingested from various sources. These will get used to stitch various identities together to a unified profile. For our B2B use case, we’re introducing a new set of B2B identity types, such as B2B account or B2B opportunity, for example. To help expedite the setup of both namespaces and schemas we have provided an automated script that can be executed through Postman, which will generate all the required B2B namespaces and schemas to get you started with ingesting data. Let’s run through that now. For this demo, we will use the Marketo utility, but know that that’s set up for a CRM utility is very similar, aside from the org ID. Through the documentation link, you’ll have access to the GitHub repository.
There are two parts for setup. First, is the environment setup, and you also have an auto-generation utility, both of which you’ll download and import into Postman.
For the environment, although it’ll look empty initially, if you look at the documentation, you have sample values that will help you figure out what values to replace in the Potman utility. The end result will look something like this.
This top section is composed of Adobe components. So you’ll find the values by following the Adobe Developer Console instructions, which will walk you through the steps to grab the access tokens, client IDs and API keys necessary for the utility to run against your IMS org’s API. Next, we have the Rikard Marketo Munchkin ID, since this demo will create Marketo-specific namespaces and schemas. This behavior is similar if you’re using the CRM utility and will require a CRM org ID. If you have a Marketo subscription synced to a CRM, the Marketo script is set to handle the secondary identities, by entering the SFDC or MSD org ID here. Lastly, these two variables are pre-configured for features in Marketo, which are defaulted to false, but can be altered if you know you have these features enabled in Marketo. To get the utility to run, we leverage the Postman runner. Click on your collection on the top level folder called Namespaces and Schemas Autogen Utility.
Click the run section that will take you to the Postman runner. It’s useful to note that we’ll want to run all scripts in order and run the full progression rather than attempting to execute each individually. So you shouldn’t uncheck any of these boxes. Before we run the utility, we’ll go ahead and go to view and select Show Postman Console. This will be helpful to have up because the Postman Console will show any conflicts, errors and details. We simply want to verify that conflicts are acceptable and that we have no error. Now we can go ahead and run the utility.
Back in Adobe Experience platform, after your page is refreshed, you’ll now see the new namespaces that have been created. What you’ll see is a series of namespaces that follow a standard B2B naming convention, starting with issuer, such as Marketo, then entity type, such as Static List, Program Member, or Opportunity Contact Role, then the org ID. We can also take a look at some of the schemes that have been created.
If we click into one of them, we can also see that the established relationships are already there, such as from opportunity to account.
Know that these have the base setup of the schemas. So with each base class and field group that we recommend for B2B use cases, they’re already there for you. You can optionally be modified or extended to include your custom attributes and field groups. Before we wrap up, I’d like to highlight that with the schema, we’ve also established relationships between entities. One critical new relationship that we’re introducing as part of our B2B use cases, is between an individual and an account. People have a many-to-many relationship to accounts, meaning that you can have multiple individual profiles that can be related to multiple accounts. By setting up that relationship, those accounts will appear as values on the profile. We’re also introducing an entity called the Account Person relation, and that defined the connection between individuals and account. And so, although we’ve programmatically set up the relationships, I’ll demonstrate how the relationships can be established. First off, it’s defined within the schema, allowing each identity to be linked to its related entity. Within the schema builder, you’ll see this arrow that designates an identity.
By clicking that we’ll be presented with a new window to add the relationship. Let’s start from left to right. We first have the relationship type. It’s selected to be the default value of many-to-one. Then you’ll select the schema that you’re relating this identity to and by doing so you’ll have the reference identity namespace auto-populate. Then you’re going to select or set a friendly name or a label for the relationship name from both the current schema, as well as the schema that you’re referencing. These are used as labels within profile and segmentation. So you want to make sure that they’re useful. And if it applies, you’re able to add multiple relationships to a single identity by clicking the Add Relationship button below. We can take a look at one of those examples when we have multiple relationships established. In this case, we have the person ID field and it’s being referenced to the opportunity contact role, the program member, as well as these static list membership.
Now with namespaces, schemas and relationships all set up, you’re ready to move on to the next training module. So in summary, within this video, you’ve learned about the data structure of XDM Business classes and field groups. You now have a better understanding of identity namespaces and their relationships. And how to create namespaces, schemas and set up those relationships. Thank you for watching. -

Prerequisites prerequisites

  • You must first ingest account profiles and create account audiences before you can activate them to downstream destinations.
  • To activate account audiences to destinations, you must have successfully connected to a destination. If you haven’t done so already, go to the destinations catalog, browse the supported destinations, and configure the destination that you want to use. Read the UI tutorial on connecting to destinations for more information.

Required permissions permissions

To activate account audiences, you need the View Destinations and Activate Destinations access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

To ensure that you have the necessary permissions to activate account audiences, browse the destinations catalog. If a destination has an Activate control, then you have the appropriate permissions.

Select your destination select-destination

Follow the instructions to select a destination where you can export your datasets:

  1. Go to Connections > Destinations, and select the Catalog tab.

    Destination catalog tab with Catalog control highlighted.

  2. Select Activate on the card corresponding to the destination that you want to export datasets to.

The destinations that can export account audiences are indicated with an icon in the upper right corner of the card, similar to the destination highlighted below, or you can use the data type filter to only display destinations that can export account audiences, as shown higher on the page.

Amazon S3 destination page that can export profile audiences highlighted.

  1. Select Data type Accounts, followed by the destination connection that you want to export datasets to, then select Next.
If you want to set up a new destination to activate account audiences, select Configure new destination to trigger the Connect to destination workflow and select accounts as data type.

Destination activation workflow with accounts control highlighted.

  1. Proceed to the next section to select your account audiences for export.

Select your account audiences select-account-audiences

Use the check boxes to the left of the account audiences names to select the audiences that you want to export to the destination, then select Next. Note that only account audiences are shown in this view, and no other audience types are displayed.

Dataset export workflow showing the Select audiences step where you can select which account audiences to export.

Scheduling and next steps

For the rest of the activation workflow to export account audiences, read the tutorial on activating data to file based-destinations. Continue from the schedule audience export step. If you are activating account audiences to the (Companies) LinkedIn Matched Audiences destination, read the tutorial on activating streaming destinations. Continue from the mapping step.

Note that in the scheduling step when exporting account audiences to cloud storage destinations, the workflow to activate account audiences only allows you to export full files and incremental files on a daily schedule. Hourly exports are not supported. Note also that After audience evaluation is the only supported evaluation type.

Important callouts and known limitations important-callouts-known-limitations

Note the following important callouts and known limitations for the general availability release of the functionality to activate account audiences.

Required mapping pairs in the mapping step when activating account audiences to the (Companies) LinkedIn Matched Audiences destination required-mappings

When activating account audiences to the (Companies) LinkedIn Matched Audiences destination, note that the following two mapping pairs are mandatory to successfully export data:

LinkedIn mapping required fields.

Source field
Target field
primaryId (select this field in the Select Identity namespace view, when selecting the Target Field).
Select identity namespace highlighted in the workflow to activate account audiences to destinations. {width="100" modal="regular"}

Data governance enforcement data-governance-enforcement

Consent is enforced at the person or profile level for customer and prospect audiences. Therefore, consent policy evaluation is currently not supported when activating account audiences to destinations. In the review step of the activation workflow, you can see a greyed out control for View applicable consent policies.

Review step of the activate account audiences workflow with the consent enforcement control greyed out.

Other data governance mechanisms in Real-Time CDP such as data usage policy checks and attribute-based access control are supported.