Airship provides push messaging services, including segmentation and targeting capabilities.
The following types of data can be configured to be sent from Airship to mParticle
The Airship field mapping referred to in the table below can be found in the Airship Connect Schema, found at:
Airship events are mapped as follows:
| Airship Field | mParticle Mapping | Description |
|---|---|---|
| type | Event Type = Custom Event Custom Event Type = Other Event Name = type where type is: CONTROL RICH_DELIVERY RICH_READ RICH_DELETE REGION IN_APP_MESSAGE_DISPLAY IN_APP_MESSAGE_RESOLUTION IN_APP_MESSAGE_EXPIRATION Event Type = Uninstall Event, when type is UNINSTALL |
Event Type |
| occurred | timestamp_unixtime_ms | Unix timestamp in milliseconds |
| os_channel for iOS android_channel or amazon_channel for Android |
Platform | Channel Identifier |
| named_user_id | Customer ID User Identity | Customer ID |
| com.urbanairship.idfa | iOS Advertising ID | IDFA |
| com.urbanairship.vendor | IDFV | IDFV |
| com.urbanairship.aaid | Android Advertising ID | Android Advertising ID |
| com.urbanairship.limited_ad_tracking_enabled | LimitAdTracking | Indicates if the user has enabled limit ad tracking |
| app_package_name | Package Name | A unique identifier for the app name |
| app_version | Application Version | The version of the application |
| device_model | Device Model | The device model |
| device_os | OS Version | The device operating system |
| carrier | Network Carrier | The carrier of the device |
Information about configuring the Airship output for mParticle can be found at the Airship Partner Integrations documents.
You will need to work with your Airship Account Manager to setup the Airship to mParticle Feed.
Was this page helpful?