# Marketing Platforms

Marketing automation, journey orchestration, and CRM platforms integrated with Airship help you coordinate messaging across your stack.

<!-- PAGE: Acoustic, PATH: https://www.airship.com/docs/integrations/marketing-platforms/acoustic/ -->

# Acoustic

> Export and target audiences aggregated across marketing platforms.
<!-- this page gets linked from within Acoustic; so don't move it without aliasing or whatever -->

Acoustic (formally IBM UBX) is a marketing cloud and analytics platform. With this integration you can send audience lists and [custom events](https://www.airship.com/docs/reference/glossary/#custom_event) from Acoustic to Airship. You can design personalized Airship [Sequences and Automations](https://www.airship.com/docs/guides/messaging/messages/sequences/about/) based on the custom events.

## Acoustic Integration Requirements

* **Accounts**
  1. Acoustic
  1. Airship — Must include messaging
* **Airship project**
  * [named user](https://www.airship.com/docs/reference/glossary/#named_user) must be enabled for your project.

### Named Users and Acoustic Audiences

To use the Acoustic integration, you must enable named users in Airship. The `named_user_id`
for your named users must be an audience identifier (type) in your Acoustic environment
so that Airship can associate your Acoustic shared audience — exported from Acoustic as
custom events or static lists — with named users.

If your `named_user_id` and Acoustic identifier types do not match,
Airship will not be able to associate custom events or static lists with named users, preventing you
from effectively issuing automated messages or performing other operations based
on your Acoustic audience.

See the [Named users feature guide](https://www.airship.com/docs/guides/audience/named-users/) or
the [Named Users API](https://www.airship.com/docs/developer/rest-api/ua/operations/named-users/) for more information about configuring
named users.

## Understanding Acoustic Deployment Types

When configuring the integration, you will create an endpoint in Acoustic and determine whether you want to export your Acoustic audience as a series of custom events or as a static list. This is the **Deployment Type**.

The **Custom Events** deployment type sends your Acoustic audience to Airship as custom events associated with your named users. This deployment type lends itself to automation using the Acoustic-generated custom event as a triggering event.

The **Static Lists** deployment type sends your Acoustic audience to Airship as a static list. You can schedule the deployment of the static list. If you do not rename the list in Acoustic between scheduled intervals, the contents of the list are overwritten during the scheduled interval. For example, if you have a list called `abandoned_cart`, and you deploy it every Tuesday, the contents of the list will change every Tuesday; members of the list will only remain the same if they abandoned their carts for two straight weeks. [Learn more about static lists and audience selection](https://www.airship.com/docs/guides/audience/segmentation/audience-lists/uploaded/).

## Configuring the Acoustic Integration 

In Airship:

1. Next to your project name, select the dropdown menu (▼), then **Settings**.
1. Under **Project settings**, select **Partner Integrations**.
1. Select **Acoustic**.
1. Select **Configure** for the inbound integration and follow the onscreen instructions to:
   * Create an authentication token for your project. Acoustic uses the token to communicate with your project in Airship
   * Register an endpoint in Acoustic.

## Syncing Identifiers for Users

To take advantage of Acoustic, you have to determine the Acoustic identifier that you want to associate with named users in your app's audience. Your Acoustic identifier should be the same type of value as your
`named_user_id` in Airship. For example, if your named users are organized by
an account or username for your service, you must select the Acoustic Identifier type
that corresponds the account or username value.

1. Select the options menu next to your new endpoint and select **Edit Endpoint Details**.
1. Go to the **Identifiers** tab and select **Edit** for the `named_user` identifier. > **Note:** You can only edit identifiers once.
<!-- do you need to delete the endpoint if you screw up and start over? -->
1. Set the Identifier type to the identifier that corresponds to the`named_user_id` values for your named users.
1. Select **Save**. You are now ready to share your Acoustic audience with your app.

## Sharing Your Audience with Airship

After you configure your endpoint, you have to determine when and how often to share
your Acoustic audience with your Airship app. Your source audience is unique to your Acoustic environment and use case.

1. Go to the **Audiences** tab in the Acoustic dashboard and select **Share audiences and identifiers**.
1. Select **Share an audience**, then **Next**.
1. Select the Acoustic Source Audience that you want to share with your Airship app, and then select your Airship endpoint as the Destination Audience.
1. In **Create New Audience**, enter a name without spaces for this audience, then select **Next**. The audience name becomes the `name` of your custom event or static list in Airship.
> **Note:** If sharing an audience as custom events, the event name must be entirely lowercase. If the name contains uppercase characters, Airship will not receive the event.

1. Under **Map audience identifiers**, select the **Source identifier** for your audience. This is the value mapped to your named users in Airship.
1. For **Destination identifier**, enter `named_user`, and then select **Next**.
   ![Mapping audience identifiers in Acoustic](https://www.airship.com/docs/images/acoustic-map-audience_hu_7d6ae8b9660f936c.webp)
   
   *Mapping audience identifiers in Acoustic*
1. For **Share audiences and identifiers**, determine the frequency, and then select **Next**. By default, Acoustic shares custom events with Airship as they occur.
   ![Configuring audience sharing frequency in Acoustic](https://www.airship.com/docs/images/acoustic-share-audiences_hu_b2fa273bc0e09a80.webp)
   
   *Configuring audience sharing frequency in Acoustic*
1. To provide destination options, select **Add New Records**, then specify a minimum number of records to share.
   * If you opt to share immediately, Acoustic will share an audience as soon as it meets the minimum threshold.
   * If you share the audience on a schedule, and you do not reach the minimum number of records before the scheduled interval, Acoustic will wait to share audiences and identifiers until the next scheduled interval.
1. Select **Share** to initiate audience sharing with Airship.

## Using Acoustic Custom Events as Automation Triggers

You can use your Acoustic audience as a trigger in Automations and Sequences. As Acoustic shares
custom events with your app, your app will trigger sending messages to associated named users,
providing a powerful, automated way to stay in touch with your audience.

In the *Setup* step in an Automation or *Trigger* step in a Sequence:

1. Select the **Custom Event** trigger, and specify the name of your custom event. The
custom event name is the same as the *Audience name* in the Acoustic dashboard.
1. Configure the message that you want to send when Airship receives the corresponding
audience of custom events from Acoustic.

See also:

* [Configure Triggers: Custom Event](https://www.airship.com/docs/guides/messaging/messages/sequences/triggers/#custom-event)
* [Automation composer tutorial](https://www.airship.com/docs/guides/messaging/messages/sequences/create-automation/)
* [Create a sequence](https://www.airship.com/docs/guides/messaging/messages/sequences/create/create/)

## Sending a Message to Your Acoustic Audience List

If you deploy your Acoustic audience as a static list, you can target that list in the Audience step when sending a message. The name of your list in Airship is the same as the name of your audience set in Acoustic under *Audiences*.

Follow the steps in the [Audience step](https://www.airship.com/docs/guides/messaging/messages/create/#audience) of *Create a Message*. Using the **Target by conditions** or **Target specific users** option, search for and select your list.


<!-- /PAGE: Acoustic -->

<!-- PAGE: Customer.io, PATH: https://www.airship.com/docs/integrations/marketing-platforms/customer-io/ -->

# Customer.io

> Add mobile event data to your customer profiles.
[Customer.io](https://customer.io/) is a behavioral email platform that
harnesses user activity and profile data to send targeted campaigns at scale.
With the Airship [Real-Time Data Streaming](https://www.airship.com/docs/reference/glossary/#rtds) and Customer.io integration, incorporate mobile
engagement data into your Customer.io profiles and run email campaigns based
on Airship events.

## Customer.io Integration Requirements

This integration requires these accounts:
   1. Customer.io
   1. Airship — Must include both:
      * Messaging
      * [Real-Time Data Streaming](https://www.airship.com/docs/reference/feature-packages/#data)

<!-- Commented out for DOC-1704.

* **Airship project**
  * [named user](https://www.airship.com/docs/reference/glossary/#named_user) must be enabled for your project.

---

In order for Airship to send events to Customer.io, you need to register users in Customer.io and associate an email address. See [Integrating with Customer.io](https://customer.io/docs/basic-integration.html) for more information on registering users.

The important thing to remember is that your Airship [named user](https://www.airship.com/docs/reference/glossary/#named_user) must match the identifier you send over to Customer.io in your `identify` call. In the next sections we'll show you how to set the Airship named user to match your Customer ID.

### Client Code: iOS

In your iOS project, set the Airship named user to be the same ID you use in the Customer.io `identify` call.

```swift
UAirship.namedUser().identifier = "NamedUserID"
```


```obj-c
[UAirship namedUser].identifier = @"NamedUserID";
```


See [Mobile: Contacts](https://www.airship.com/docs/guides/audience/your-audience/)
for more detail.
### Client Code: Android/Fire OS

In your Android/Fire OS project, set the Airship named user to be the same ID you use in the Customer.io `identify` call.

```java
// Associate the channel to a contact.
Airship.getContact().identify("NamedUserID");
```


See [Mobile: Contacts](https://www.airship.com/docs/guides/audience/your-audience/)
for more detail.

-->

## Configuring the Customer.io Integration 

You will need your **Customer.io Site ID** and **API key**, found in your [Customer.io dashboard Integration settings](https://fly.customer.io/).

In Airship:

1. Next to your project name, select the dropdown menu (▼), then **Settings**.
1. Under **Project settings**, select **Real-Time Data Streaming**.
1. Under **Real-Time Data Streaming**, select **Customer.io**.
1. Follow the onscreen instructions to configure the integration.

Once you've configured the integration, we'll start sending events from this project
to your Customer.io instance, and they will appear in your user activity
stream.

The following example from the Customer.io dashboard shows an expanded custom
event and open event.

![Sample Customer.io event data in Airship](https://www.airship.com/docs/images/connect-customer.io-sample-data_hu_71514492b07fc6e6.webp)

*Sample Customer.io event data in Airship*


<!-- /PAGE: Customer.io -->

<!-- PAGE: Salesforce Marketing Cloud, PATH: https://www.airship.com/docs/integrations/marketing-platforms/salesforce/ -->

# Salesforce Marketing Cloud

> Leverage Airship from within Salesforce Marketing Cloud.
Companies engage with their users to deliver positive brand experiences, support
their business goals, and build long-term relationships. You can coordinate all
your engagement campaigns within the Salesforce Marketing Cloud (SFMC) Journey Builder. And you can consume Airship's events in SFMC, adding Airship-gathered engagement data to your CRM system.

![Salesforce Marketing Cloud integration uses](https://www.airship.com/docs/images/sfmc-benefits_hu_f42e76b44600070c.webp)

*Salesforce Marketing Cloud integration uses*

## Inbound integration

When you integrate Airship into SFMC's Journey Builder, you can send Airship app, SMS, and web messages from an SFMC journey. You can also send [wallet push notifications](https://www.airship.com/docs/guides/wallet/user-guide/notifications/push-notifications/), both to external IDs and pass IDs.

* **Create a compelling campaign in minutes** — Initiate campaigns with easy-to-use tools that don't require a development team. With Airship, you can add mobile, SMS, and web messaging to any customer journey that will deliver in-the-moment value to your app audience.

* **Create automated SFMC journeys triggered by cross-channel events** — Send targeted campaigns to onboard, activate, retain and re-engage your customers. Easily zero in on the insights necessary to drive targeted actions in other systems.

* **Use multiple Airship projects in SFMC** — Most companies have different Airship projects for different purposes. You can add all your projects to SFMC and use them in individual campaigns.

* **Add actions and extras to message payloads** — Do more with your messages by adding Actions (Deep Links, Landing Pages, Tagging, etc.) and Extras (key/value pairs available to the app upon direct open).

* **Re-engage users** — Use cross-channel marketing to re-engage users when they uninstall your app or convert on their mobile device or web browser.

For additional uses, see [Using the inbound integration with SFMC journeys](#using-the-inbound-integration-with-sfmc-journeys) below.

### Integration requirements

This integration is fairly flexible in terms of audience mapping. In the context of an individual Airship Activity, you can target an audience using either:

   * A value from the Journey's Entry Source — This can be either a [named user](https://www.airship.com/docs/reference/glossary/#named_user) ID or [channel](https://www.airship.com/docs/reference/glossary/#channel_term) ID.
   * The named user associated with the subscriber from the project configuration

Named users map IDs from your CRM or another backend system (like SFMC) to device IDs. The named user IDs you set must map to a data extension in SFMC. Airship cannot target devices if you do not set named users appropriately. See
[Associating Channels with Named Users](https://www.airship.com/docs/guides/audience/named-users/#associate) in the *Named users* guide
to set the named user ID for a device via the iOS SDK, Android SDK, or the
server-side API.

### Configure Airship in SFMC

The steps for configuring Airship in SFMC are provided in the Airship dashboard:

1. Next to your project name, select the dropdown menu (▼), then **Settings**.
1. Under **Project settings**, select **Partner Integrations**.
1. Select **Salesforce Marketing Cloud**. If the SFMC tile is not visible, please fill out our [interest form](https://www.airship.com/lp/airship-sfmc-integration/).
1. Select **Configure** for the inbound integration and follow the onscreen instructions to:
	* Create [tag group](https://www.airship.com/docs/reference/glossary/#tag_group) `sfmc-integration` and an authentication token. All tags set from Salesforce appear in this tag group, and it used to reference Salesforce tags in the API. SFMC uses the token to communicate with your project in Airship.
	* Configure the Airship integration in SFMC.

### Add Airship projects to SFMC

After configuring Airship in SFMC, add your Airship projects to SFMC. You can select the project that you want to send messages from when configuring activities in SFMC journeys.

In SMFC:

1. Hover over **AppExchange** and select **Airship**.
1. Select **New Project** or select the edit icon (
) to edit the settings for an existing Airship project.
   ![Adding an Airship project to SFMC](https://www.airship.com/docs/images/salesforce-config.2_hu_c64253cd79ddb7cb.webp)
   
   *Adding an Airship project to SFMC*
1. Configure for the project:
   | Field | Description | Steps |
   | --- | --- | --- |
   | **Project** | The name of your Airship project | Enter the project name. |
   | **App Key** | Your Airship project [app key](https://www.airship.com/docs/reference/glossary/#app_key). You can find this in your Airship project in **Settings**. | Enter the app key. |
   | **Auth Token** | The auth token you created when [configuring Airship in SFMC](#configure-airship-in-sfmc) | Enter the auth token. |
   | **Email Address** | The address where SFMC should send notifications about send issues | Enter an email address. |
   | **Contact Attributes** | The field in your Data Extension External Key that you want to map to your Airship named users | Navigate to the data extension containing the field you want to map. In **Named User**, select the field.<p>Data extensions are displayed as they are represented in your SFMC Attribute Groups. If you need assistance locating the field, contact your SFMC administrator. |
   | **Wallet Config (Optional)** | Enables including Airship [wallet push notifications](https://www.airship.com/docs/guides/wallet/user-guide/notifications/push-notifications/) in an SFMC journey | See [Enable sending Airship wallet push notifications](#enable-sending-airship-wallet-push-notifications). |
   {class="table-col-1-20 table-col-2-40"}
1. Select **Add Project**.

### Enable sending Airship SMS messages

To support including Airship SMS messages in an SFMC journey, you must add your Airship [sender IDs](https://www.airship.com/docs/reference/glossary/#sender_id) to SFMC. You add a sender ID to SFMC by entering a name and its Airship long code or short code. Do this after you add your Airship project to SFMC.

If you do not know your long or short codes, you can find them in the Airship dashboard:

1. Select the **Messages** menu, then **SMS Keywords**.
1. Select **+ Create new keyword**.
1. Select **Settings**, then the **SMS Sender** menu. You will see all the long codes and short codes for your project. Each sender in the list is formatted as a 2-character country code followed by the actual long or short code. 
1. Note the long and short codes, then leave the page without saving a new keyword.

If you do not have access to the Airship dashboard, [contact Airship Support](https://support.airship.com) to request the codes.

---

Add Airship sender IDs to SFMC:

1. Hover over **AppExchange**, then select **Airship**.
1. Select the edit icon (
) for the project you want to add your sender IDs to.
1. Under **SMS Sender**, select **Add SMS Sender** and configure for each sender you want to add:
   | Field or setting | Description | Steps |
   | --- | --- | --- |
   | **Name** | Required. A descriptive name for the sender that will help you identify it in Salesforce. | Enter a name. |
   | **Number** | Required. The long code or short code you want to send messages from. | Enter a long or short code. |
   | **Enable MMS** | Optional. Allows sending MMS messages in your SFMC Journey Builder. | Check the box to enable. |
1. Select the add icon (+).

### Enable sending Airship wallet push notifications

To support including Airship [wallet push notifications](https://www.airship.com/docs/guides/wallet/user-guide/notifications/push-notifications/) in an SFMC journey, you must add your Airship wallet project credentials to an SFMC project that is also configured for messaging. You can add or remove these credentials from SFMC at any time. When present, the wallet channel will be available when [including an Airship message in an SFMC journey](#include-an-airship-message).

First, get your credentials from your Airship wallet project:

1. Go to **Settings**, then **API**.
1. Copy your wallet API key and secret.

Now you can add them to an SFMC project:
   * If you are setting up a new project, follow the steps in [Add Airship projects to SFMC](#add-airship-projects-to-sfmc) and enter your credentials in the **Wallet Config** section.
   * To add your credentials to an existing project in SFMC:
      1. Hover over **AppExchange**, then select **Airship**.
      1. Select the edit icon (
) for the project you want to enable for sending wallet push notifications.
      1. Under **Wallet Config**, enter your API key and secret.
      1. Select **Save Project**.

## Using the inbound integration with SFMC journeys

In addition to sending Airship app, SMS, and web messages from an SFMC journey, you can:

* Send custom events from an SFMC journey to Airship
* Personalize messages and custom events with information from your SFMC Contacts model
* Set tags on named users that you can use for tracking or to trigger automation

When you install the Airship AppExchange package as part of the integration setup, two activities are automatically added to your Journey Builder:

* Message activity — *Airship Notification*
* Custom — *Airship Events/Tags*

You will use these activities in the following steps.

### Include an Airship message

Include Airship app, web, and SMS messages to SFMC journeys. You must set up messages per channel in individual activities, but message types per channel can be combined. For example, you can set up a push notification and an in-app message in a single Mobile App activity.

In SFMC:

1. Go to **Journey Builder**, then **Journey Builder**.
1. Select an existing journey or select **Create New Journey**.
1. In the left sidebar, go to **Activities**, then **Messages**, then drag the **Airship Notification** activity into your journey.
   ![Adding an Airship Notification activity to a journey](https://www.airship.com/docs/images/integrations/sfmc-activity-mobile_hu_f5b95b09160e7d9b.webp)
   
   *Adding an Airship Notification activity to a journey*
1. Select the **Airship Notification** activity in the journey.
1. Select a configuration section from sidebar and configure the message:
   * **Project**: Select the Airship project you want to send the message from.
   * **Channel**: Select an engagement channel for the message: Mobile App, Web, SMS, MMS, or Wallet. For Mobile App, also select a message type: Push Notification, In-App Message, or both. For SMS and MMS, also select a [sender](#enable-sending-airship-sms-messages).

      By default, audience members are targeted using Contact Data as configured for the project. To target using Entry Source data instead, select **Entry Source**, and then select a field and type. You must already have an Entry Source configured for the journey.

   * **Content**: Enter the text to display in the message.

      For Mobile App, when you combine a push notification and in-app message, the in-app message's alert text is the same as the push notification text by default. To use different messages, under **In-App Message**, select **Write Alternative**, then enter message text.

      For Wallet, when using an external ID as the audience identifier, a template ID is required. Template IDs can be found in a wallet project dashboard under **Templates**.

      All other Content settings are optional:
      | Setting | Description | Steps |
      | --- | --- | --- |
      | **Title** | For Mobile App push notifications and Web only. A heading that appears above the notification text.<p>For push notifications, it appears in the iOS Notification Center, Apple Watch Looks, and the Android and Fire OS Notification Area/Drawer.<p>For Web, the title entered here overrides [the default set in Airship](https://www.airship.com/docs/developer/sdk-integration/web/getting-started/#airship-setup) and appears in the iOS Notification Center and Android and Fire OS Notification Area/Drawer. | Enter text. |
      | **Label** | For wallet push notifications only. A description of the notification. The label is for reference only, it is not included in the push notification. | Enter text. |
      | **Media** | For Mobile App, Web, and MMS only. Media to display in your message. See [Media guidelines](https://www.airship.com/docs/reference/messages/media-guidelines/). | Enter an HTTPS URL. |
      | **Notification Buttons** | For Mobile App and Web only. Interactive buttons that appear after the message text. You can select from [predefined interactive buttons](https://www.airship.com/docs/reference/messages/built-in-interactive-notifications/) and configure adding or removing tags when the button is selected. Some buttons also require setting an [action](https://www.airship.com/docs/reference/glossary/#action): Home, Web Page, or Dismiss. | Select and configure buttons. See also [Actions](https://www.airship.com/docs/guides/messaging/messages/actions/). |
      | **Shorten Links** | For SMS and MMS only. Enables [link shortening](https://www.airship.com/docs/reference/glossary/#sms_link_shortening). | Check the box to enable. |
      | **SMS Fallback Text** | Recommended, for MMS only. Users who cannot receive your MMS message will receive an SMS message with this text along with the media URL, if any. 160 characters maximum. | Enter text. |
      | **Action** | For Mobile App and Web only. The Home, Web Page, Landing Page, Deep Link, or Share [action](https://www.airship.com/docs/reference/glossary/#action). You can also add or remove [tags](https://www.airship.com/docs/reference/glossary/#tag) and set key value pairs ([custom keys](https://www.airship.com/docs/reference/glossary/#custom_keys) in Airship) for users who interact with the message. | Select and configure an action. Follow the steps in [Actions](https://www.airship.com/docs/guides/messaging/messages/actions/). For tags, enter a tag name, select the add icon (+), then select **Add** or **Remove**. For key value pairs, enter the key name and value, then and select the add icon (+). |
      | **Campaigns<sup>1</sup>** | Tracks the message in Airship using [campaign categories](https://www.airship.com/docs/reference/glossary/#campaign_categories). Each category has a 64-character maximum. 10 maximum categories. | Enter categories. |
      {class="table-col-2-50"}
      <sup>1. In addition to campaign categories you add, Airship automatically adds two to each send from SFMC: the ID of the SFMC Journey and the ID of the activity in the Journey.
1. Select **Review** to view a summary of the activity and a preview of your message. 
1. Select **Done** to save the activity.

### Send custom events to Airship

You can send [custom events](https://www.airship.com/docs/reference/glossary/#custom_event) from an SFMC journey to Airship for triggering, segmentation, and reporting.

When you set up a custom event in your journey, you can determine the properties that you want to send with the event. The event name appears in the `body.name` of the custom event that SFMC sends to Airship, and its properties appear in the custom event's `body.properties` object.

Issue a custom event to Airship as a part of a Salesforce journey:

1. Go to **Journey Builder**, then **Journey Builder**.
1. Select an existing journey or select **Create New Journey**.
1. In the left sidebar, go to **Activities**, then **Custom**, then drag the **Airship Events/Tags** activity into your journey.
1. Select the **Airship Events/Tags** activity in the journey.
1. Select the Airship project you want to send the custom event to.
1. For **Audience Trigger**, select **Custom Event**.<p>By default, audience members are targeted using Contact Data as configured for the project. To target using Entry Source data instead, select **Entry Source**, and then select a field and type. You must already have an Entry Source configured for the journey.
1. Select **Custom Event** in the sidebar or scroll down to its section, then enter an event name in snake case. Example: `hot_sauce`. Event names cannot contain uppercase characters.
1. Select **Add Property**, then enter a property name in snake case, and enter a value for the property and select its type. You can add up to 10 properties. Select **Add Another Property** for more properties. 
1. Select **Done**.

### Personalize custom events and messages

To personalize Airship activities, create a merge field representing a value you want to personalize, surrounded by double percent signs, e.g., `%%customer_name%%`. Airship replaces the merge field (and braces) with the data specified by the merge field at send time — just like mail merge in a word processor or mail client.

Use the fields in your Salesforce Contacts model that are linked by Attribute Group (Attribute Sets).

For example, if you have a field called `customer_name`, you could use the value from that field in your custom event with `%%customer_name%%`. If you have multiple fields in the model with the same name, reference the data extension name to select the correct field, using the format `%%data_extension_name.field_name%%`.

> **Note:** The support of AMPScript syntax is limited. You may use it for referencing fields by name, but program logic control structures, such as *if* statements or function calls, are not supported.


> **Important:** Data that is available for personalization is tied to the audience being used in the activity. If the audience is Contact Data (the default), use Contact Attributes to personalize. Since the audience is linked to a Subscriber in that case, any Contact Attribute linked to that Subscriber should be available for personalizing messages and custom events. If the audience is Entry Data, there's no guaranteed notion of associated Subscriber, so in that case you can only use fields in the Entry Source for personalization.


### Add or remove tags

You can add tags to, or remove tags from, named users as they progress through a Salesforce journey. Setting tags on your audience results in `tag_change` events in Airship that you can use as message triggers or to track changes to your audience. All tags set from Salesforce appear in the Airship tag group `sfmc-integration` that is automatically created when [configuring Airship in SFMC](#configure-airship-in-sfmc).

Set tags in Airship as a part of a Salesforce journey:

1. Go to **Journey Builder**, then **Journey Builder**.
1. Select an existing journey or select **Create New Journey**.
1. In the left sidebar, go to **Activities**, then **Custom**, then drag the **Airship Events/Tags** activity into your journey.
1. Select the **Airship Events/Tags** activity in the journey.
1. Select the Airship project containing the audience you want to set tags on.
1. For **Audience Trigger**, select **Tag Change**.<p>By default, audience members are targeted using Contact Data as configured for the project. To target using Entry Source data instead, select **Entry Source**, and then select a field and type. You must already have an Entry Source configured for the journey.
1. In the **Set Tags** field, enter the name of the tag that you want to set or remove, select the add icon (+), then select **Add** or **Remove** as the action. Repeat this step for each tag.
   ![Setting tag change actions in an SFMC journey](https://www.airship.com/docs/images/sfmc-tag-change_hu_41058278cdda991d.webp)
   
   *Setting tag change actions in an SFMC journey*
1. Select **Done**.

## Outbound integration

> **Important:** This integration is not recommended for real-time workflows, as there are many factors that can limit the speed of updates.


Send events from Airship to SFMC using [Real-Time Data Streaming](https://www.airship.com/docs/reference/glossary/#rtds) to incorporate your audience's message activities into your CRM environment.

* **Track Airship user engagement in Salesforce** — Understand and leverage how and when your users are using (or not using) your app in the Marketing Cloud interface.

* **Trigger SFMC journeys from Airship engagement events** — Take advantage of Airship's Real-Time Data Streaming events in SFMC to trigger new journeys and keep your audience engaged.

### Configure your SFMC account

You need your SFMC API account credentials, SOAP WSDL URL, and MID when configuring the integration in Airship. If these items are not available to you, contact your SFMC admin.

Complete the following steps in SFMC:

1. Create an **API account username and password**:

   1. Select your username in the upper right corner, then select **Setup**.
   1. In the sidebar, select **Administration**, then **Users**, then **Users**.
   1. Select **Create** and fill in the user information. **Make sure to check the box for *API User*.**
   1. Select **Save**.

1. **Set permissions for the API user account**:

   These permissions can also be set by a role assigned to the user account.

   1. Select your username in the upper right corner, then select **Setup**.
   1. In the sidebar, select **Administration**, then **Users**, then **Users**.
   1. Check the box for the API user account and select **Manage Roles**.
   1. Select **Edit Permission** and expand the **Email** section.
   1. Navigate to each section and set each permission to Allow:
      | Section path | Permission |
      | --- | --- |
      | Email » Subscribers » Data Extension | Create |
      | Email » Subscribers » Data Extension | View |
      | Email » Subscribers » Data Extension | Update |
      | Email » Subscribers » Data Extension | Manage Data |
      | Email » Admin » API Access | Webservice API |
   1. Select **Save**.

1. Verify **web services permissions** for the Business Unit:

   1. Select your username in the upper right corner, then select **Setup**.
   1. In the sidebar, select **Security**, then **Security Settings**.
   1. Under **Username and Logins**, verify that **Enable Username and Password for Web Services** is set to Yes. If not, contact your SFMC admin.

1. Get your **SOAP WSDL URL**:

   1. Select your username in the upper right corner, then select **Setup**.
   1. In the sidebar, select **Settings**, then **Company Settings**, then **Account Settings**.
   1. In **General Settings**, copy the SOAP WSDL URL.

1. Get your **Marketing Cloud Member ID (MID)**:

   Hover over the Business Unit name  (it's to the left of your username) and copy the MID from the modal that appears:
   ![ Finding your Salesforce Marketing Cloud Member ID (MID)](https://www.airship.com/docs/images/salesforce-mid_hu_2f7fbfb6ee615c09.webp)
   
   * Finding your Salesforce Marketing Cloud Member ID (MID)*

### Configure SFMC in Airship

In Airship:

1. Next to your project name, select the dropdown menu (▼), then **Settings**.
1. Under **Project settings**, select **Real-Time Data Streaming**.
1. Under **Real-Time Data Streaming**, select **Salesforce AppExchange**.
1. Follow the onscreen instructions to configure the integration to:
   * Enter [your SFMC API account credentials, SOAP WSDL URL, and MID](#configure-your-sfmc-account)
   * Select the Airship event types you want to send to SFMC

> **Tip:** You can configure different Airship project RTDS data to route to specific Business Units in SFMC by using the MID for the specific Business Unit in the RTDS configuration. It's also possible to use a single MID for all Airship projects, which will share Data Extensions. This is feasible because the app key is included in the Data Extensions.


### Data extensions and storage location

A short time after completing integration configuration, the folder /airship will be automatically created in your Data Extensions root folder. Do not create this folder manually.

The folder will contain data extensions representing the Airship event types you selected when setting up the integration. Unlike other event types, Airship `tag_change` events are represented by two data extensions: TAG_CHANGE_EVENTS and TAG_ACTION_EVENTS. The TAG_ACTION_EVENTS data extension lists added and removed tags.

See [SFMC Data Extension Schemas for RTDS](https://www.airship.com/docs/integrations/marketing-platforms/salesforce-schemas/).

> **Important:** 1. **DO NOT EDIT** Data Extensions, or you may break your integration.
> 1. In order to prevent data loss, integrations require a data retention policy for all
>    Salesforce Data Extensions created in the /airship folder.
> 
>    See Salesforce documentation for more information about how to set up a data retention policy:
> 
>    * [Manage Data Retention Policy](https://help.salesforce.com/articleView?id=sf.mc_cab_manage_data_retention_policy.htm)
>    * [Manage Contact Data](https://trailhead.salesforce.com/en/content/learn/modules/marketing-cloud-contact-management/manage-contact-data)



<!-- /PAGE: Salesforce Marketing Cloud -->

<!-- PAGE: Export Lists from Salesforce Marketing Cloud, PATH: https://www.airship.com/docs/integrations/marketing-platforms/sfmc-export-lists/ -->

# Export Lists from Salesforce Marketing Cloud

> Export lists of users or attributes from Salesforce Marketing Cloud to Airship.
You can turn a Salesforce Marketing Cloud (SFMC) audience into an Airship [uploaded list](https://www.airship.com/docs/reference/glossary/#uploaded_list). You can also send SFMC Text, Number, and Date [attributes](https://www.airship.com/docs/reference/glossary/#attribute) to Airship for personalization and targeting. Even better, you can automate the exports to save time.

This document walks you through creating an SFMC Data Extension, creating keys and configuring SFTP for the file transfer, creating SFMC activities that perform the data extraction and file transfer, and automating the tasks.

## Creating the Data Extension

Your SFMC data will be converted to CSV format before transfer to Airship. The structure of your Data Extension table defines the CSV.

### Formatting for Static Lists

For Static Lists, your Data Extension must contain a [named user](https://www.airship.com/docs/reference/glossary/#named_user) value for each audience member. Configure your Data Extension with these two fields:

| Field name | Value |
| --- | --- |
| **Identifier type** | `named_user` |
| **Named User** | The ID string that represents the user in Airship |

Each row of the CSV will contain an `Identifier type, Named User` pair. However, the field names you enter in your Data Extension do not matter since they are omitted when the CSV is created. Example conversion to CSV:
```text
named_user,customer-009842
named_user,customer-277099
```


### Formatting for Attributes

For Attributes, configure your Data Extension with a field named `named_user` and an additional field for each attribute to associate with the named user:

| Field name | Value |
| --- | --- |
| **named_user** | The ID string that represents the user in Airship |
| **&lt;attribute_id&gt;** | The named user's data in [Text, Number, or Date format](https://www.airship.com/docs/guides/audience/attributes/about/#attribute-types), depending on the attribute type |

The Data Extension field names are used as the header row in the CSV, so you must enter the them exactly. Subsequent rows list a named user ID and the value of each attribute for that user. Example conversion to CSV:

```text
named_user,first_name,last_name
customer-009842,Freddy,Shoop
customer-059874,Denise,Green
customer-277099,Francis,Gremp
```


> **Important:** You must [define custom attributes or add predefined attributes in Airship](https://www.airship.com/docs/guides/audience/attributes/adding/) before associating them with named users. Using a custom or predefined attribute that you haven't yet set up in the Airship will result in an error.



## Setting up file transfer requirements

Airship's SFTP implementation uses SSH key pairs for authentication. You must create a pair of keys: a private key for your client and a public key for Airship. Then you can add the keys to Airship and SFMC and create a storage location to transfer your file from.

In Airship:

1. Follow the steps in [Generate keys](https://www.airship.com/docs/guides/audience/segmentation/sftp-upload/#generate-keys) in *SFTP upload for CSV files*.

1. Follow the steps in [Add your public key to Airship](https://www.airship.com/docs/guides/audience/segmentation/sftp-upload/#add-your-public-key-to-airship) in *SFTP upload for CSV files*.
   * Making sure to set the Purpose to `Static Lists` or `Attributes`, depending on your list type.
   * Note the host, port, and username for use in the following SFMC steps.

In SFMC:

1. Create an SSH encryption key. Follow the steps in Salesforce's [Create an Encryption Key for Marketing Cloud](https://help.salesforce.com/s/articleView?id=sf.mc_overview_create_a_key.htm&type=5). Since it is for file transfer activities, make sure to use the private key of the key pair generated using the Airship steps above.

1. Create an External SFTP Site [File Location](https://help.salesforce.com/s/articleView?language=en_US&id=sf.mc_overview_file_locations.htm&type=5). Follow the steps in Salesforce's [Set Up an External FTP, SFTP, or FTPS Site File Location](https://help.salesforce.com/s/articleView?id=sf.mc_overview_set_up_external_ftp_location.htm&type=5) using the stored key from the previous step as well as the host, port, and username provided by Airship. See also [Set up your client and transfer CSVs](https://www.airship.com/docs/guides/audience/segmentation/sftp-upload/#set-up-your-client-and-transfer-csvs) in *SFTP upload for CSV files*.

## Setting up data extraction and transfer

Set up SFMC tasks that extract the data from the Data Extension, format it, and transfer it to your SFTP File Location.

Follow the steps in the following two Salesforce documents:

1. [Data Extension Extract in Automation Studio](https://help.salesforce.com/s/articleView?id=sf.mc_as_data_extension_extract.htm&type=5)

   For Static Lists:
      * The file name entered will be the name of the Uploaded/Static list in Airship.
      * Be careful about using wildcard dates. They could result in exceeding the 100 list per project limit. 
      * Use a comma as the column delimiter.
      * Leave **Has Column Headers** unselected.
      * Select **Uses Line Feed**.

   For Attributes:
      * The file name is not used anywhere in Airship, only in the File Transfer activity.
      * Use a comma as the column delimiter.
      * Select **Has Column Headers**.
      * Select **Uses Line Feed**.

1. [Create a File Transfer Activity in Automation Studio](https://help.salesforce.com/s/articleView?id=sf.mc_as_use_a_data_extract_activity.htm&type=5)
   * Use the same file naming pattern as the Data Extension Extract.
   * Select file action **Move a File From Safehouse**. This is where the files will be when the previous activity completes.
   * For **Destination**, select your previously created External SFTP Site File Location.
   * Do not encrypt.

## Automating the flow

The final step is using SFMC's [Automation Studio](https://help.salesforce.com/s/articleView?id=sf.mc_as_automation_studio.htm&type=5) to automate running, in order, the two tasks created in the previous step.

## Verifying transfer

After running the automation, verify it was successfully transferred.

* For Static Lists, select the **Audience** menu, then **Lists**. You should see your list in **Uploaded Lists** with more than zero entries.

* For attributes, select the **Audience** menu, then **Attributes**, then **Upload History**. For more information, see [Viewing upload history](https://www.airship.com/docs/guides/audience/attributes/managing/#viewing-upload-history) in *Managing attributes*.

## Targeting users

You can now use the transferred data for targeting. See:

* [Using uploaded lists](https://www.airship.com/docs/guides/audience/segmentation/audience-lists/uploaded/#using-uploaded-lists)
* [Targeting your audience using attributes](https://www.airship.com/docs/guides/audience/attributes/targeting/)
* [Segments](https://www.airship.com/docs/guides/audience/segmentation/segments/)


<!-- /PAGE: Export Lists from Salesforce Marketing Cloud -->

<!-- PAGE: Zeta Global, PATH: https://www.airship.com/docs/integrations/marketing-platforms/zeta-global/ -->

# Zeta Global

> Create and adapt powerful app experiences that accelerate customer understanding for next-level personalization to capture more business value for everyone involved.
To create and adapt powerful app experiences that accelerate customer understanding for next-level personalization to capture more business value for everyone involved, Zeta has partnered with Airship, a leader in the space of push notifications with proven scale and a significant integration footprint. With this, we are leapfrogging our mobile app strategy and in no time, expanding to deliver data-driven personalized experiences to you all. Owing to this integration with Airship, you now have a multitude of options for push notification solutions to choose from:

* Deliver and report on mobile push messages
* Send push notifications to Android or iOS through the familiar interface of building Broadcast Campaigns or Experience Builder
* Retrieve push notification events and track your campaign’s performance through Report Builder

## Zeta Global Integration Requirements

**Accounts**
   1. Zeta Global
   1. Airship — Must include messaging

## Configuring the inbound Zeta Global Integration

1. Next to your project name, select the dropdown menu (▼), then **Settings**.
1. Under **Project settings**, select **Partner Integrations**.
1. Select **Zeta Global**.
1. Select **Configure** for the inbound integration and follow the onscreen instructions to:
	* Create an authentication token. Zeta uses the token to communicate with your project in Airship.
	* Add a new connector for Airship in Zeta Global.

## Configuring the outbound Zeta Global Integration

1. Next to your project name, select the dropdown menu (▼), then **Settings**.
1. Under **Project settings**, select **Partner Integrations**.
1. Select **Zeta Global**.
1. Select **Configure** for the outbound integration and follow the onscreen instructions to:
   * Provide your Zeta Marketing Platform endpoint URL
   * Select the Airship events to send to Zeta Global

For information about configuration and usage, see Zeta's [Airship integration](https://knowledgebase.zetaglobal.com/kb/integration-with-airship) documentation.


<!-- /PAGE: Zeta Global -->