Urban Airship (v1)

Urban Airship integration summary

Stitch’s Urban Airship integration replicates data using the Airship API version 3. Refer to the Schema section for a list of objects available for replication.

Urban Airship feature snapshot

A high-level look at Stitch's Urban Airship (v1) integration, including release status, useful links, and the features supported in Stitch.

Connecting Urban Airship

Urban Airship setup requirements

To set up Urban Airship in Stitch, you need:

• To verify your Urban Airship API access. Urban Airship limits API access based on their product plans, meaning some plans have access while others do not.

  If you create an Urban Airship integration and Stitch displays a 401 Unauthorized or 403 Forbidden error, you may not have access to Urban Airship’s API.

We recommend reaching out to Urban Airship support to confirm your API access level before beginning the setup in Stitch.

Step 1: Retrieve your Urban Airship app credentials

1. Sign into your Urban Airship account.
2. In the dashboard, open the app you want to connect to Stitch.
3. If the Engage tab doesn’t open, click Engage at the top to open it.
4. Click the gear icon located near Reports, then select APIs & Integrations.
5. The APIs & Integrations page will display.

Leave this page open for now - you’ll need it to complete the setup.

Step 2: Add Urban Airship as a Stitch data source

1. Sign into your Stitch account.

2. On the Stitch Dashboard page, click the Add Integration button.

3. Click the Urban Airship icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch Urban Airship” would create a schema called stitch_urban_airship in the destination. Note: Schema names cannot be changed after you save the integration.

5. In the App Key field, paste your Urban Airship App Key.
6. In the App Secret field, paste your Urban Airship App Secret.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines 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 replicate data beyond Urban Airship’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Urban Airship integrations support the following replication scheduling methods:

• Replication Frequency

• Anchor Scheduling

• Advanced Scheduling using Cron (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up Urban Airship, its Sync Status may 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 replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Urban Airship table reference

channels.channel_id = named_users.channels

channels.named_user_id = named_users.named_user_id

named_users.channels = channels.channel_id

named_users.named_user_id = channels.named_user_id

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.