This integration is maintained by Airship. Please contact Airship for support.

Tealium is a Customer Data Platform (CDP). CDPs collect, store, and normalize large volumes of data while creating a persistent identifier that spans across data sets. You can use the inbound and source integrations together or separately.

Inbound Integration
Use Tealium to set TagsMetadata that you can associate with channels or named users for audience segmentation. Generally, they are descriptive terms indicating user preferences or other categorizations, e.g., wine_enthusiast or weather_alerts_los_angeles. Tags are case-sensitive., AttributesMetadata used for audience segmentation and personalization. They extend the concept of Tags by adding comparison operators and values to determine whether or not to target a user, helping you better evaluate your audience., and deliver Custom EventsEvents that indicate that a user performed a predefined action, such as adding an item to a shopping cart, viewing a screen, or clicking an Unsubscribe button. Custom events can trigger automation, including Sequences, Scenes, and Surveys. You can code them into your app or website, or send them to Airship from an external source using the custom event API. Custom events contain properties that you can use to personalize messages. in Airship. This data is synced between Tealium and Airship using Named UserA customer-provided identifier used for mapping multiple devices and channels to a specific individual..

Once in Airship, customers can segment based on those tags, events, and custom event properties, as well as trigger Automations and Sequences. Personalization using attributes and custom event properties is also supported.

Source Integration
Rich user-level App, SMS, Web, Email, and Open channel data is sent from Airship to Tealium using Real-Time Data StreamingA service that delivers engagement events in real time via the Data Streaming API or an Airship partner integration.. Tealium then transforms Airship data into traits and audiences, unifying users and content across different platforms. You choose which RTDS events to send to Tealium.

Tealium integration requirements

Configuring the Tealium inbound integration

In Airship:

  1. Go to Settings.
  2. Under Project Configuration, select Manage for Partner Integrations.
  3. Select Tealium.
  4. Select Configure for the inbound integration and follow the onscreen instructions to:

Configuring the Tealium source integration

To set up this integration, you will:

  1. Configure your app to set the tealium_visitor_id on Airship events. See the Kotlin and iOS setup sections below for more information.
  2. Add Airship to Tealium as a source and retrieve your Data Source Endpoint.
  3. Set up the RTDS integration for Tealium in the Airship dashboard.

When you set up a Tealium RTDS integration, your events will contain a tealium_visitor_id key. This is the identifier Tealium uses to differentiate between unique events. As a fallback, you may want to set your Airship Named UserA customer-provided identifier used for mapping multiple devices and channels to a specific individual. value to tealium_visitor_id to ensure that events are matched within Tealium.

Set the tealium_visitor_id on Airship events

Kotlin SDK example
// Initialize the Tealium library
TealiumConfig tealiumConfig = TealiumConfig(
    dataSourceId = {DATASOURCE_ID},  //optional
    modules = mutableSetOf(VisitorService),
    dispatchers = mutableSetOf(TagManagement, Collect)
Tealium tealium = Tealium.create("tealium_instance", tealiumConfig);
// Get the Tealium visitor ID
String visitorId = tealium.getVisitorId();

// Add the visitor ID to the current associated identifiers
  .addIdentifier("tealium_visitor_id", visitorId)

See also: Tealium Kotlin Identity Resolution documentation.

Swift SDK example
// Initialize the Tealium library
let config = TealiumConfig(account: {ACCOUNT},
               profile: {PROFILE},
               environment: {ENVIRONMENT},
               datasource: {DATASOURCE})
let tealium = Tealium(config: config)
// Get the Tealium visitor ID
let visitorId = tealium.visitorId

// Add the visitor ID to the current associated identifiers
let identifiers = Airship.analytics.currentAssociatedDeviceIdentifiers()
identifiers.set(identifier: visitorId, key:"tealium_visitor_id")

See also: Tealium Swift Identity Resolution documentation.

Add Airship to Tealium as a source

You will also retrieve your Data Source Endpoint URL.

  1. Log in to Tealium.
  2. In the sidebar, select Sources, then Data Sources, which will take you to a page where you can add Airship as a data source.
  3. Select Add Source.
  4. Under Communication, select Airship.
  5. Enter a name for your Airship source integration.
  6. Select Continue until you reach the Choose Event Specifications page.

    The event specifications currently do not support Airship-specific events. Tealium may add these in the future. For now, you can ignore the event specifications.

  7. Select Continue to proceed to the Get Code page.
  8. Copy the Data Source Endpoint URL. You will paste this in the Airship dashboard when setting up the RTDS integration.

    The Install steps listed in the Tealium Get Code page are the same as provided in the next section on this page. Please read the steps for information not provided by Tealium.

Set up a Tealium RTDS integration in Airship

You will need your Tealium Data Source Endpoint URL.

In Airship:

  1. Go to Settings.
  2. Under Project Configuration, select Manage for Real-Time Data Streaming.
  3. Under Real-Time Data Streaming, select Tealium.
  4. Follow the onscreen instructions to configure the integration.

    You have the option to include anonymous data. Events that have a tealium_visitor_id, named user, or delivery_address (phone number, MSISDNThe mobile phone number of an individual in your Airship audience. Each MSISDN represents an individual mobile device., or email address) are delivered to Tealium by default. When electing to send anonymous data, Airship sends all events to Tealium regardless of whether the user is identified with a Visitor ID or Secondary Visitor ID.

See also Airship incoming webhook setup guide in Tealium’s Incoming Webhooks documentation.