> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/airship.md).

# Airship

Share segments with Airship as tags, so an audience built in the CDP can be messaged from Airship.

The Airship connector shares your segments with Airship as [Airship tags](https://docs.airship.com/guides/messaging/user-guide/audience/segmentation/tags/), so an audience built in mediarithmics becomes targetable in your Airship messaging.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/esp-and-marketing-automation.md">ESP &#x26; marketing automation</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Emails, Channels, Named User, Open Channel</td></tr><tr><td><strong>Authentication</strong></td><td>Credentials shared with your mediarithmics account manager</td></tr></tbody></table>

## Description

### What is Airship?

Airship is a customer engagement platform. Audiences in Airship are described with **tags**, which are held in **tag groups**, and messages are addressed to the devices and applications those tags resolve to.

### What you can do with this connector

* Push a mediarithmics segment into an Airship tag group, so it can be targeted in Airship.
* Keep that tag in step with the segment as users enter and leave it.
* Activate the same segment across several Airship properties, once each has been configured.

### Which identifiers are sent

When you share a segment through this connector, mediarithmics can send:

* **Emails** - plain text email identifiers.
* [**Channels**](https://docs.airship.com/guides/messaging/getting-started/developers/channels-intro/) - Airship's identifiers for addressing applications on iOS, Android, Fire OS and web devices.
* [**Named User**](https://docs.airship.com/guides/messaging/user-guide/audience/segmentation/named-users/) - the Airship identifier that maps several devices and channels to one individual.
* [**Open Channel**](https://docs.airship.com/guides/messaging/user-guide/messages/content/open/) - custom communication channels configured in Airship. Available in a later release.

## Connector setup

### Prerequisites

The initial setup is done **once per Airship property** you want to activate segments to.

* A **tag group** created on the Airship side to hold your mediarithmics tags. Ask your Airship account manager for it; naming it `mediarithmics` makes it easy to identify in your Airship instance.
* Your [Airship endpoint](https://docs.airship.com/api/ua/?openapi=http#servers), which depends on your geography.
* An Airship token carrying the **Audience Modification** role - created from **Settings > Tokens > Create Token**. See [Airship API security](https://docs.airship.com/guides/messaging/getting-started/developers/api-security/index.html#basic-auth).
* Your Airship **Project Token**.

### Authentication

mediarithmics authenticates to Airship with credentials that you provide. Share the **App Key**, **Access Token** and **Project Token** with your mediarithmics account manager **in a secure way**. They are held in the mediarithmics back office and referenced from the feed by an Airship project name, rather than entered again on each feed.

### Setup steps

{% stepper %}
{% step %}
**Have the tag group created in Airship.**

One per property you intend to activate segments to.
{% endstep %}

{% step %}
**Send the credentials to your mediarithmics account manager.**

Endpoint, App Key, Access Token and Project Token, shared securely.
{% endstep %}

{% step %}
**Ask your Solution Architect for the first configuration.**

The data files and back-office configuration are set up on the mediarithmics side.
{% endstep %}

{% step %}
**Select the Airship connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="220">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Identifies this feed inside mediarithmics.</td></tr><tr><td><strong>Airship Tag Group</strong></td><td>The tag group that will hold the shared segment tags. It must already exist in Airship.</td></tr><tr><td><strong>Airship Project</strong></td><td>The project name configured by your account manager. It points at the Airship project and its credentials.</td></tr><tr><td><strong>Identifiers resources</strong></td><td>The identifier types and compartments to push to Airship.</td></tr><tr><td><strong>Tag Name</strong> <em>(optional)</em></td><td>The value shown on the Airship side under the tag group.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## Good to know

* **Tag Name defaults to the segment.** If you leave it empty, the tag is the mediarithmics segment ID and segment name joined by a semicolon.
* **Tag Name is capped at 128 characters.**

## FAQ

#### Do I need to repeat the setup for each Airship property?

Yes. The tag group and the credential exchange are done once per Airship property you want to activate segments to.

#### Who creates the tag group?

Airship, on your request - ask your Airship account manager. mediarithmics does not create it, and the feed will not work if the tag group is missing.

#### Can I control the name of the tag Airship receives?

Yes, through the optional **Tag Name** field. Left empty, it falls back to the segment ID and name.

## Partner documentation

Airship documents its own platform at <https://www.airship.com/docs/>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/connectors/destinations/airship.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.