ESP - Campaign Studio

ESP - Campaign Studio

Capability

Campaign Studio is a marketing automation platform that you can inject with CDP-enriched data to enable new features. The most important feature is the omni-channel drip campaign builder, known as Journeys.

Input data

The following are the two ways in which data is pulled from Campaign Studio to Customer Data Platform (CDP):

• Contacts and campaigns - The API-based integration daily pulls the Campaign Studio contacts and campaigns.

• Events - Campaign Studio events such as email send, click, and open are received in real time from the Campaign Studio webhook to the CDP’s Kafka cluster. Therefore, Campaign Studio email events can be acted upon in real time within the CDP.

Output data

With this output connector, you can use a CDP campaign to push any one-to-one (1:1) content to Campaign Studio to append to the Campaign Studio contact profile (glossary term, activate to view definition) as a custom field. CDP does not support One-to-many (1:N) datasets.

You can use this integration to push all CDP Customer Summary and Machine Learning segments on a daily basis to Campaign Studio after the daily orchestration and Machine Learning workflows are complete.

CDP is integrated with the Machine Learning bulk create contact API to upload a list of customers for upserting into Campaign Studio’s contact list. By default, Campaign Studio uses email address as the primary key, and exactly matches the email address when upserting contacts.

The following are the constraints:

Data:

• You can push only one-to-one contact-level data to Campaign Studio through this output connector. CDP does not support one-to-many datasets and non-contact data.
• CDP cannot push a NULL or empty value to Campaign Studio to overwrite an existing value in Campaign Studio with NULL.

Volumes:

• Campaign Studio is limited to no more than 3 million contacts per Campaign Studio instance. The performance starts to degrade at around 1 million contacts per instance.

Setup

To set up the ESP - Campaign Studio:

1. Create a Campaign Studio user that can push contacts through the API:
   1. Log in to Campaign Studio.
   2. Click Settings > Users.

   3. Create a new user with API access by providing the necessary information.

      Ensure that you use a strong password to protect this service account.

   4. Set the access level for this API user to Admin.
   5. Click Settings > Configuration > API Settings.
   6. Set the Enable HTTP basic auth toggle bar to Yes.
2. Create custom contact fields in Campaign Studio for any CDP attributes that you want to push to Campaign Studio:
   1. Log in to Campaign Studio.
   2. Click Settings > Custom Fields.
   3. Add new custom fields by providing the following information:
      • Label: This is equivalent to a CDP display name.
      • Unique alias: This is equivalent to a column header. It is used within APIs for reading and writing data in Campaign Studio. It only contains lowercase alphanumeric and underscore [a-z0-9_].
      • Group: Specify the suitable contact field group.

      • Data type: CDP supports the following Campaign Studio data types:

        Campaign Studio Data Type	CDP AIF Data Type	CDP UDM+ Data Type	Details
        Text	String	String	For text <=255 characters. Set the maximum character length accordingly.

With this output connector, you can use a CDP campaign to push any one-to-one (1:1) content to Campaign Studio to append to the Campaign Studio contact profile (glossary term, activate to view definition) as a custom field. CDP does not support One-to-many (1:N) datasets.

You can use this integration to push all CDP Customer Summary and Machine Learning segments on a daily basis to Campaign Studio after the daily orchestration and Machine Learning workflows are complete.

CDP is integrated with the Machine Learning bulk create contact API to upload a list of customers for upserting into Campaign Studio’s contact list. By default, Campaign Studio uses email address as the primary key, and exactly matches the email address when upserting contacts.

The following are the constraints:

Data:

• You can push only one-to-one contact-level data to Campaign Studio through this output connector. CDP does not support one-to-many datasets and non-contact data.
• CDP cannot push a NULL or empty value to Campaign Studio to overwrite an existing value in Campaign Studio with NULL.

Volumes:

• Campaign Studio is limited to no more than 3 million contacts per Campaign Studio instance. The performance starts to degrade at around 1 million contacts per instance.

Setup

To set up the ESP - Campaign Studio:

1. Create a Campaign Studio user that can push contacts through the API:
   1. Log in to Campaign Studio.
   2. Click Settings > Users.

   3. Create a new user with API access by providing the necessary information.

      Ensure that you use a strong password to protect this service account.

   4. Set the access level for this API user to Admin.
   5. Click Settings > Configuration > API Settings.
   6. Set the Enable HTTP basic auth toggle bar to Yes.
2. Create custom contact fields in Campaign Studio for any CDP attributes that you want to push to Campaign Studio:
   1. Log in to Campaign Studio.
   2. Click Settings > Custom Fields.
   3. Add new custom fields by providing the following information:
      • Label: This is equivalent to a CDP display name.
      • Unique alias: This is equivalent to a column header. It is used within APIs for reading and writing data in Campaign Studio. It only contains lowercase alphanumeric and underscore [a-z0-9_].
      • Group: Specify the suitable contact field group.

      • Data type: CDP supports the following Campaign Studio data types:

        Campaign Studio Data Type	CDP AIF Data Type	CDP UDM+ Data Type	Details
        Text	String	String	For text <=255 characters. Set the maximum character length accordingly.
        TextArea	String	String	For text >255 characters.
        Number	Integer	Integer	For integers <=4 bytes. Set precision accordingly.
        Number	Long	Long	For integers between 4 and 8 bytes. Set the precision accordingly.
        Number	Decimal	Decimal	For floating point numbers <= 4 bytes. Set the precision accordingly.
        Number	Decimal	Double	For floating point numbers between 4 and 8 bytes. Set the precision accordingly.
        Date/Time	Date	Long	Both Campaign Studio and CDP store date time in UTC.
        Date	Not supported	Not supported	Not supported
        Boolean	Boolean	Boolean	Accepted values are true, yes, 1, false, no, 0.