This integration was created by Stitch for Singer, an open-source, composable ETL platform. Check out & contribute to the repo on GitHub.
Urban Airship is currently in Open Beta. The info in this article is subject to change.
Release Status | Open Beta | Availability | Free |
Status Page | Urban Airship Status Page | Default Historical Sync | 1 year |
Whitelist Tables/Columns | Unsupported/Unsupported | Default Replication Frequency | 30 minutes |
Full Table Endpoints | 1 | Incremental Endpoints | 3 |
Destination Incompatibilities | None |
Connecting Urban Airship
Connecting Stitch to Urban Airship is a four-step process:
- Retrieve your Urban Airship app credentials
- Add Urban Airship as a Stitch data source
- Define the Historical Sync
- Define the Replication Frequency
Connecting Multiple Apps
If you want to connect multiple Urban Airship apps to Stitch, you will need to create a separate Urban Airship integration for each app. App credentials are app-specific, meaning only a single app can be connected per Stitch integration.
Retrieving Your Urban Airship App Credentials
- Sign into your Urban Airship account.
- In the dashboard, open the app you want to connect to Stitch.
- If the Engage tab doesn’t open, click Engage at the top to open it.
- Click the gear icon located near Reports, then select APIs & Integrations.
- The APIs & Integrations page will display.
Leave this page open for now - you’ll need it to complete the setup.
Add Urban Airship as a Stitch Data Source
- On the Stitch Dashboard page, click the Add an Integration button.
-
Click the Urban Airship icon.
-
Enter a name for the integration. This is the name that will display on the for the integration; it’ll also be used to create the schema in your data warehouse.
For example, the name “Stitch Urban Airship” would create a schema called
stitch_urban_airship
in the data warehouse. This schema is where all the tables for this integration will be stored. - In the App Key field, paste your Urban Airship App Key.
- In the App Secret field, paste your Urban Airship App Key.
Defining the Historical Sync
The Sync Historical Data setting will define the starting date for your Urban Airship integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to sync data beyond Urban Airship’s default setting of 1 year. For a detailed look at historical syncs, check out the Syncing Historical SaaS Data article.
Define the Replication Frequency
The Replication Frequency controls how often Stitch will attempt to replicate data from your Urban Airship integration. By default the frequency is set to 30 minutes, but you can change it to better suit your needs.
Before setting the Replication Frequency, note that:
- The more often Urban Airship is set to replicate, the higher the number of replicated rows.
-
The number of rows in the source may not equal the number of rows replicated by Stitch. Tables that use Full Table Replication will result in a higher number of replicated rows.
- If you’re using a data warehouses that doesn’t natively support nested structures, you’ll see a higher number of replicated rows due to the de-nesting Stitch performs.
To help prevent overages, we recommend setting the Replication Frequency to something less frequent - like 6 hours instead of 30 minutes. For tips on reducing your row count, check out the Reducing Your Row Count section of our Billing Guide.
After selecting a Replication Frequency, click Save Integration.
Urban Airship’s Intial Sync
After you finish setting up Urban Airship, you might see its Sync Status show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial sync for the integration. This may take some time to complete.
Urban Airship Schema
Stitch's Urban Airship integration includes these tables:
channels
Replication Method: Incremental
Primary Key: channel_id
Contains Nested Structures?:
Yes
channels
table contains info about the channels - or unique identifiers - used to address applications on iOS, Android, and Amazon devices.channels & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
channels Attributes
While we try to include everything Urban Airship has here, this may not be a full list of attributes. Refer to Urban Airship's documentation for a full list and description of each attribute.
channel_id
device_type
installed
background
opt_in
push_addresses
created
last_registration
named_user_id
alias
tags
*
tag_groups
*
ios__badge
ios__quiettime__start
ios__quiettime__end
ios__tz
lists
Replication Method: Incremental
Primary Key: name
Contains Nested Structures?:
No
lists
table contains info about device lists.lists Attributes
While we try to include everything Urban Airship has here, this may not be a full list of attributes. Refer to Urban Airship's documentation for a full list and description of each attribute.
name
description
extra
*
created
last_modified
channel_count
status
named_users
Replication Method: Full Table
Primary Key: named_user_id
Contains Nested Structures?:
No
named_users
table contains info about named users, or individual consumers. These identifiers can be used to map CRM data to channels.named_users Attributes
While we try to include everything Urban Airship has here, this may not be a full list of attributes. Refer to Urban Airship's documentation for a full list and description of each attribute.
named_user_id
tags
*
channels
*
segments
Replication Method: Incremental
Primary Key: id
Contains Nested Structures?:
Yes
segments
table contains info about segments, or portions of your audience that have arbitrary metadata attached.segments & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
segments Attributes
While we try to include everything Urban Airship has here, this may not be a full list of attributes. Refer to Urban Airship's documentation for a full list and description of each attribute.
Segment ID (
id
)display_name
creation_date
modification_date
Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, please reach out to us.