Skip to main content

What this is

The Airship real-time destination sends users out of Zeotap CDP to Airship as they qualify a Journeys workflow, so you can engage them on the channels Airship manages. Airship is a customer engagement platform that helps marketers deliver personalised and relevant experiences across multiple channels and touchpoints; integrated with Zeotap CDP, it lets you act on those audiences in real time and at scale. You attach the destination to the Send to Destinations node inside a workflow. The destination holds the Airship connection credentials; the node holds the action and the field mapping used for that workflow. Airship appears elsewhere in Zeotap CDP, in both directions:

Supported identifiers and actions

This integration exposes one action, Send Named User to Airship, which sends data from the workflow you built in Journeys. You must map at least one ID for data to transfer from Zeotap CDP to the Airship destination. The IDs are Named User, iOS channel, Android channel and Web channel. If you map more than one ID, Zeotap CDP chooses the ID highest in the priority order below. Event Name and Event Timestamp are mandatory and are mapped to the destination fields by default.

Prerequisites

Obtain the following from Airship, and confirm your Zeotap CDP access, before you create the destination:
  • Access Token — an authentication mechanism that allows authorised users to access resources within an Airship integration. It confirms that the user is authorised for the resources they request and helps secure the Airship integration against unauthorised access. See Create an Airship access token.
  • X-UA-Appkey — in Airship, a header that identifies the unique app key associated with each mobile device. The app key is a unique identifier assigned to each mobile device by Airship and is used to manage device information, send notifications and track app usage.
  • Region — the region your Airship account subscription is registered for. Confirm it with your Airship account manager.
  • A Journeys workflow with the user filters or conditions already applied. See Create a workflow.
  • A role that grants Create and Edit Destinations and Create, Edit, and Archive Journeys on the organisation that owns the destination. For the role-to-permission matrix, see User Roles and Access.

Create an Airship access token

Perform the following steps in Airship:
1
Log into the Airship Static Lists console and navigate to Settings.
2
Under Settings, select Project Configuration and click Manage for Tokens.
3
Click Create Token.
Airship token management screen with the Create Token button
4
Enter a token name. This is a friendly name that helps you recognise your tokens in Airship.
5
Select the Role you want to grant for this token. For more information, see Airship API Security.
  • Audience Modification — grants read and write permission to audience APIs, including channels, named users, segments, lists and so on. Use this permission for users sending custom events into Airship.
  • All Access — grants full access to your Airship project, except Acoustic integrations. You must use this permission when creating a token for an inbound message handling web-hook.
6
Click Create Token.
Airship token creation form with the token name and role fields completed
7
Copy the values, then click Got it to close the window.
Airship confirmation window shown after a token is created

Create the Airship destination

After you have applied filters or added conditions for your users in Journeys, open the Send to Destinations node. A window appears where you can set up the destination: reuse an existing destination from the list, or create a new one with + Add New Destination.
Send to Destinations panel listing the destinations already available in the workspace, with the + Add New Destination link above the search box
1
Click + Add New Destination.
2
Search for Airship.
3
Click the Airship Static Lists tile and enter a name for the destination.
4
Enter the Access Token and X-UA-Appkey you obtained from Airship.
5
Choose the appropriate Region from the drop-down menu and click Next.
6
On the mapping screen, under Choose your Action, select Send Named User to Airship. Under Map the Fields, map the relevant output identifiers and attributes — see Supported identifiers and actions for the full list and the priority order. The mandatory Event Name and Event Timestamp fields are mapped to the destination fields by default.
Mapping screen with Send Named User to Airship selected under Choose your Action and catalogue fields mapped to the Event Name and Event Timestamp destination fields
7
Click Create Destination. The destination is created and becomes available for activation in Journeys.

Activate the destination in a Journeys workflow

Once the destination exists, link it in the Send to Destinations node of the workflow.
1
In the workflow, click + and choose Send to Destinations.
Node menu on the workflow canvas with Send to Destinations highlighted among the available node types
2
Choose the destination from the list of available destinations, using the search box to find it.
Send to Destinations panel with the search box highlighted above the list of available destinations
3
On the Destination Details tab, the Access Token, X-UA-Appkey and Region fields are populated automatically from the values you entered when you created the destination.
4
On the Destination Settings tab, choose the action and mapping for this node.
Destination Settings tab showing Send Named User to Airship as the chosen action and the Event Name and Event Timestamp fields listed under Mapping
5
Click Save Destination. The destination is attached to the node.
Attached destination card on the Send to Destinations node showing the destination name, its ID, the mapping name and the Send Named User to Airship action
For the rest of the workflow — adding further nodes, setting re-entry criteria and publishing — see Activate your real-time audiences.

Verify the activation worked

The destination is set up correctly when all of the following hold:
  1. After you click Create Destination, the new destination appears in the list of available destinations on the Send to Destinations node.
  2. After you click Save Destination, the destination card is attached to the node and shows the destination name, the mapping name and the Send Named User to Airship action.
  3. The workflow shows Published status in the workflow listing screen. See Activate your real-time audiences.
  4. In Airship, new records or events arrive carrying the identifiers and attributes you mapped.
  5. For a single user, Journey Traces shows the output event that was sent to the Airship node, so you can confirm the mapped fields left Zeotap CDP with the values you expect.

Troubleshoot the Airship destination

For the failure status code on a node and its resolution path, see Journey Error Codes. When you escalate, include the journey execution ID, the error code and timestamp, the destination name and type, the Request ID from the Execution Details panel, and the steps you have already taken — see Troubleshooting Workflows.

FAQ

No. A destination is a workspace-level object. Once created, it appears in the destination list on the Send to Destinations node of any workflow in the same workspace. The credential fields are shared; the action and mapping on the Destination Settings tab are set per node.
Yes. In the Send to Destinations node, add each additional destination. Every attached destination receives users as they qualify the workflow.

Next steps

Last modified on November 5, 2026