Configure audience data type
When you build a destination connector with Destination SDK, you can define the type of audience that will be exported to your destination. Configuring the correct audience data type ensures that your destination receives the right data for its intended use case, whether it’s for marketing campaigns, account-based strategies, or data analysis.
Review the audience data types below to learn about the differences between them and identify the type that you need for your integration. Then, read the sections further below on the page to learn how to configure your destination to export different audience types.
The supported audience data type depends on the type of destination that you create.
Refer to the table below to understand which destination types support which audience data types.
The sources
array sources
The sources
array specifies the type of audience data that your destination supports. It is required for account audiences, prospect audiences, and dataset exports but is not needed for people audiences, as they are supported by default.
"sources":[
"ACCOUNTS" // Specifies that this destination supports account audiences
]
The sources
array accepts the following values:
"ACCOUNTS"
: Specifies that your destination supports the export of account audiences."UNIFIED_PROFILE_PROSPECTS"
: Specifies that your destination supports the export of prospect audiences."DATASETS"
: Specifies that your destination supports the export of datasets.
Depending on the audience type that you want to export to your destination, review the sections below for destination configuration examples.
Export people audiences people-audiences
People audiences are supported by default for all destination types and do not need a specific sources
value. To build a destination that supports people audiences, you do not need to use the sources
array at all, since that is the default behavior.
This is an example of a streaming destination that exports people audiences. Notice how there is no sources
array in the configuration."
code language-shell |
---|
|
Export account audiences account
Consider adding account audience support to your destination when you want to configure a B2B destination for account-based marketing. For example, you can use account-based audiences to retrieve records of all the accounts that do not have contact information for any people with the title Chief Operating Officer (COO) or Chief Marketing Officer (CMO).
To build a destination which supports the export of account audiences, add the configuration snippet below to your destination configuration.
"sources":[
"ACCOUNTS" // Specifies that this destination supports account audiences
]
code language-shell line-numbers h-12-14 |
---|
|
Export prospect audiences prospect
Consider adding prospect audience support to your destination when you want to target individuals who are not yet customers but share characteristics with your target audience. With prospect profiles, you can supplement your customer profiles with attributes from trusted third-party partners. See this prospecting use case for more information.
To build a destination which supports the export of prospect audiences, add the configuration snippet below to your destination configuration.
"sources":[
"UNIFIED_PROFILE_PROSPECTS" // Specifies that this destination supports prospect audiences
]
code language-shell line-numbers h-12-14 |
---|
|
Export datasets datasets
Consider adding dataset export support to your destination when you are looking to export raw datasets, which are not grouped or structured by audience interests or qualifications. You could use this data for reporting, data science workflows, and many other use cases. For example, as an administrator, data engineer, or analyst, you can export data from Experience Platform to synchronize with your data warehouse, use in BI analysis tools, external cloud ML tools, or store in your system for long-term storage needs.
To build a destination which supports the export of datasets , add the configuration snippet below to your destination configuration.
"sources":[
"DATASETS" // Specifies that this destination supports dataset exports
]
code language-shell line-numbers h-12-14 |
---|
|
Next steps next-steps
After reading this article, you should have a better understanding of how to configure the audience data type for your destination.
To learn more about the other destination components, see the following articles:
- Customer authentication configuration
- OAuth2 authorization
- Customer data fields
- UI attributes
- Schema configuration
- Identity namespace configuration
- Supported mapping configurations
- Destination delivery
- Audience metadata configuration
- Aggregation policy
- Batch configuration
- Historical profile qualifications