> For the complete documentation index, see [llms.txt](https://documentation.crossengage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.crossengage.io/data-and-engagement-platform/messages/integrations/channels/segment-transfer/airship/set-up-an-airship-account.md).

# Set up an Airship Account

Before you begin, you will need:

* A paid Airship account.
* A CrossEngage account.
* User data (with named user ids)

### Generating a bearer token for an Airship project <a href="#generating-a-bearer-token-for-an-airship-project" id="generating-a-bearer-token-for-an-airship-project"></a>

Bearer tokens are used to authenticate grant and control permissions for entities using the Airship API, sending custom events into the system, or supporting a Real-Time Data Streaming integration. To generate a bearer token,

* Log in to your Airship account.
* Go to the ‘Settings’ page.

<figure><img src="/files/Fw3JG9gS64h5JmXoBi3v" alt=""><figcaption></figcaption></figure>

* Go to the ‘Tokens’ page.

<figure><img src="/files/2H4pAHlrUAtKipaBXqFI" alt=""><figcaption></figcaption></figure>

* Click on ‘Create Token'.

<figure><img src="/files/ZRWI373nn61DMwY88PU6" alt=""><figcaption></figcaption></figure>

* Give your token a name and choose the role ‘All Access’.

<figure><img src="/files/cyRVRcZHBcfQ5RMWhpgy" alt=""><figcaption></figcaption></figure>

Once the token is generated, store it safely as it is needed when you setup your Airship integration in CrossEngage.

### User identification in Airship <a href="#user-identification-in-airship" id="user-identification-in-airship"></a>

In Airship, users can be identified either by a Channel ID, which identifies each individual device, or by a Named User ID, which identifies individual users. The essential distinction between these two types of identification is that one client may own multiple devices. We currently support user identification with the named user id.

Airship allows you to configure a unique user identifier called the named user id. Messages sent to a Named User ID are automatically routed to all linked Device IDs.

Be sure to remember which option you’ve chosen, which will be necessary when you set up the integration in CrossEngage.

### Loading user data into CrossEngage <a href="#loading-user-data-into-crossengage" id="loading-user-data-into-crossengage"></a>

**Creating users**

You can either upload users via API call or via user feed.&#x20;

* Instructions on how to load users into the CrossEngage platform via API can be found in User Profile Management> Bulk User Management in our [API documentation](https://docs.crossengage.io/user-management/v2).&#x20;
* Instructions on how to load users into the CrossEngage platform via user feed can be found [here](/data-and-engagement-platform/data-management.md).&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.crossengage.io/data-and-engagement-platform/messages/integrations/channels/segment-transfer/airship/set-up-an-airship-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.