Adding a destination channel

To add a destination channel:

1. Complete the previous steps of creating a campaign.

2. On the Destination(s) page, click Add new destination channel.

   

   CDP displays a list of destinations that are configured for your environment.

3. (Optional) If you cannot find the intended destination, refine the available options using the search bar and category filter.

   

For a list of common downstream destinations, see Standard Connectors.

Selection of a destination within the channel

After selecting a communication channel, you must choose a destination within the channel. The options for selecting a destination differ by the type of downstream data integration. Some destinations further ingest and utilize data, and require a pre-configured data mapping. Whereas, some destinations do not have any downstream automation configured and do not require formatted data in a fixed standard. 

Providing output file name

After choosing a destination, you must provide an output file name that has an alphanumeric name with a special character '_'. For example: Campaign_Name_01. CDP displays the following checkboxes under the output file name:

• Add current date suffix: This option is selected by default and adds the date of execution to the output file name. Clear this checkbox to skip adding the date.

• Exclude master customer ID: Master customer ID is a standard column output. Select this checkbox to exclude the master customer ID in the output file name. 

• Exclude execution ID: Execution ID is a standard column output. Select this checkbox to exclude the execution ID in the output file name. 

• Exclude file headers: Select this checkbox to exclude the file headers in the output file name. 

You can select a specific output folder path if needed.

Destinations that require strict data mapping

Downstream destinations that utilize a database require a pre-configured data mapping of CDP’s output data to their data store because data integration must know the arriving data before CDP can send it. Data integration must also know:

• How data is named and structured
• What is the type of data
• What is the destination of data in their data store

This is applicable for email service providers such as SFMC, Responsys, CheetahMail, EuroMessage, Facebook, and Google Ads.

For destinations that have these requirements, you must choose an existing data mapping to push your content.

For example, to push data to Facebook Connector, you can push email addresses by using this destination table.

Destinations that allow free-form output

Downstream destinations that are not trying to load CDP’s outbound data into their data store have less requirements around data structure. SFTP destinations may be an intermediary store for your data, but they do not have to load data into a database. Therefore, they allow a fairly flexible data format. For SFTP destinations, you must define a name for the output file.

Selection of an additional destination channel

CDP allows you to push campaigns to multiple destinations. To achieve this, you can select an additional destination. The same audience and content is sent to both destinations.

When CDP executes the campaign, it first pushes the output to Destination 1, and pushes the same output to Destination 2. If Destination 1 fails, an alert is sent and CDP does not push the output to Destination 2. If Destination 1 succeeds and Destination 2 fails, CDP pushes the output to Destination 1 when you retry or restart the campaign execution.

Some destinations such as ESPs and social media require the output data to be structured with specific attributes to fulfill a strict data mapping. Currently, you can select only one destination with a structured output because of the constraints that this fixed data mapping impresses upon Actions. For example, if your first destination is an ESP, then the second destination cannot be Facebook because the ESP and Facebook may require different output attributes.

Send to Cohort Analysis

If you have access to Cohort Analysis, you can send the campaign audience with segments and variants to Metrics for more analysis. This helps you to adequately analyze the audience and report on how the marketing affects the behavior of campaigns.

Using destinations

Adding a destination channel

To add a destination channel:

1. Complete the previous steps of creating a campaign.

2. On the Destination(s) page, click Add new destination channel.

   

   CDP displays a list of destinations that are configured for your environment.

3. (Optional) If you cannot find the intended destination, refine the available options using the search bar and category filter.

   

For a list of common downstream destinations, see Standard Connectors.

Selection of a destination within the channel

After selecting a communication channel, you must choose a destination within the channel. The options for selecting a destination differ by the type of downstream data integration. Some destinations further ingest and utilize data, and require a pre-configured data mapping. Whereas, some destinations do not have any downstream automation configured and do not require formatted data in a fixed standard. 

Providing output file name

After choosing a destination, you must provide an output file name that has an alphanumeric name with a special character '_'. For example: Campaign_Name_01. CDP displays the following checkboxes under the output file name:

• Add current date suffix: This option is selected by default and adds the date of execution to the output file name. Clear this checkbox to skip adding the date.

• Exclude master customer ID: Master customer ID is a standard column output. Select this checkbox to exclude the master customer ID in the output file name. 

• Exclude execution ID: Execution ID is a standard column output. Select this checkbox to exclude the execution ID in the output file name. 

• Exclude file headers: Select this checkbox to exclude the file headers in the output file name. 

You can select a specific output folder path if needed.

Destinations that require strict data mapping

Downstream destinations that utilize a database require a pre-configured data mapping of CDP’s output data to their data store because data integration must know the arriving data before CDP can send it. Data integration must also know:

• How data is named and structured
• What is the type of data
• What is the destination of data in their data store

This is applicable for email service providers such as SFMC, Responsys, CheetahMail, EuroMessage, Facebook, and Google Ads.

For destinations that have these requirements, you must choose an existing data mapping to push your content.

For example, to push data to Facebook Connector, you can push email addresses by using this destination table.

Destinations that allow free-form output

Downstream destinations that are not trying to load CDP’s outbound data into their data store have less requirements around data structure. SFTP destinations may be an intermediary store for your data, but they do not have to load data into a database. Therefore, they allow a fairly flexible data format. For SFTP destinations, you must define a name for the output file.

Important

A forward slash / in an output file name allows you to specify a folder path on the SFTP. Therefore, you cannot use it within a file name unless it is specifically referencing a pre-existing folder. For example, the following output file name: ‘Production/ActionsOutput/campaign123’ places the output file campaign123_yyyymmddhhmiss.csv in the Production > ActionsOutput folder. If the ActionsOutput folder does not exist within the Production folder, this data push fails.

Selection of an additional destination channel

CDP allows you to push campaigns to multiple destinations. To achieve this, you can select an additional destination. The same audience and content is sent to both destinations.

When CDP executes the campaign, it first pushes the output to Destination 1, and pushes the same output to Destination 2. If Destination 1 fails, an alert is sent and CDP does not push the output to Destination 2. If Destination 1 succeeds and Destination 2 fails, CDP pushes the output to Destination 1 when you retry or restart the campaign execution.

Some destinations such as ESPs and social media require the output data to be structured with specific attributes to fulfill a strict data mapping. Currently, you can select only one destination with a structured output because of the constraints that this fixed data mapping impresses upon Actions. For example, if your first destination is an ESP, then the second destination cannot be Facebook because the ESP and Facebook may require different output attributes.

Send to Cohort Analysis

If you have access to Cohort Analysis, you can send the campaign audience with segments and variants to Metrics for more analysis. This helps you to adequately analyze the audience and report on how the marketing affects the behavior of campaigns.