Acquia CDP

Choosing a destination

After choosing the appropriate content as described in Adding content, you must choose a destination to send the output list of customers and content that CDP generates.

Note

Some destinations might require a public IP address to authenticate or send data to your SFTP or server.

Adding a destination channel

To add a destination channel:

  1. Click Add new destination channel.

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

  2. (Optional) If you cannot find the destination you are looking for, refine the available options using the search bar and category filter.

To configure additional destinations, contact Acquia Support team or your customer value manager (CVM) if you have the location and credentials available. For a list of common downstream destinations, see Connectors.

Choosing 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.

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 to.

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.

Selecting a second channel and destination (optional)

You can push to multiple destinations. You can select an additional destination. The same audience and content is sent to both destinations.

When the campaign executes, CDP 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 in order 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 (optional)

If you have Cohort Analysis, you can additionally select the campaign audience with segments and variants to be sent to Metrics for further analysis. The audience appears in Metrics so that you can analyze them further or report on how the marketing affects their behavior.

Next Steps

After choosing a destination, you can schedule the campaign for execution: