We have released two new endpoints in support of location triggers for Automation. The Region Listing and Region Lookup APIs let you easily query all of your defined regions and associated details such as creation date, lat/long, and region attributes. If you’re not familiar with region attributes, take a look at Region Attributes from our August 2016 release notes for an overview and examples.
We are thrilled to announce the public beta for the first feature in our new Predictive Analytics toolset: Predictive Churn. In our private beta release in late 2016, we introduced the concept of churn as the likelihood that an app user will become inactive. In this public beta release, we are providing full support for predictive churn tags for targeting and automation via Engage, analysis via Insight, and data export via Connect.
Now you can delete Message Center messages with a simple API call. We encourage you to set an expiration time for rich messages, but for those times when you don’t, and that pesky old message is just sitting there in your users’ Message Centers, taunting you with its obsolescence, give this new method a try. See Delete Rich Message From Inbox for details. Enjoy!
Apple News notifications are now supported via the Engage platform, as announced in our press release on November 2nd. Select Apple News publishing partners may now have access to our Apple News Composer. This new composer enables support for yet another engagement channel through our popular Engage platform. Contact your Urban Airship Account Manager if you are interested in enabling this feature. Connect seamlessly with your Apple News publishing workflow.
When using Custom Events for automated messages, you can now set specific properties and assign a range of values that must be met in order to trigger the message. Basically, your automation options are now infinitely more customizable. We’re very excited about this enhancement and we know you will be too. Here’s an example from our Custom Event Selectors API documentation: Example: - this selector will match if a device emits a custom event that matches any of these criteria:
Customers with CDN access now have the option to upload the media included in notifications, rather than entering a URL. This is the easiest way to include rich media in your notifications, especially if you don’t have another way to host media yourself. A CDN supports optimized delivery of rich media to mobile devices across a global audience. It dynamically caches the media in critical locations across the globe to minimize download times, even across lower-bandwidth cellular connections.
We are excited to announce expanded support for custom events. Our new server-side custom events API accepts events from outside systems such as your corporate website, CRM/POS systems, or social media. You can now instrument your servers and other backend systems to send events to Urban Airship in order to send automated messages using custom event triggers. See our Automation Composer and API documentation on custom event triggers. Use Cases Server-side custom events enable a number of new automated messaging options, tying in user lifecyle events from outside of your app.
We are pleased to bring more detailed count estimation to our segments builder tool. View audience estimates while building your segments, including breakdowns by both platform and opt-in status. Estimates are updated automatically as you make changes to your segment, allowing you to quickly see how your audience changes. To learn more about this updated feature, see Estimated Audience in the Segments section of our Audience documentation.
We are pleased to announce support for iOS 10 in our latest iOS SDK release: 8.0.0. With the launch of iOS 10, we are adding support for iOS Rich Notifications and content extensions. Get started creating iOS 10 apps today by: Installing our iOS SDK 8.0.0. Enabling a notification service extension in your project. Sending rich notifications via our API by using the Media Attachment key.
In June we released two new Automation Triggers for the Engage API. Today we are excited to announce dashboard support for both of these new features: Custom Event Triggers and Cancellation Events. Custom Event Triggers Trigger a notification when a Custom Event fires: With Urban Airship’s Custom Events feature you can set Automation rules that trigger notifications when we see an occurence of the custom event. See Custom Events to learn how to set up custom events.
Defining a region just got infinitely more powerful and, dare we say, fun. When describing a region for targeting, you are no longer restricted by the binary limitations of the region’s name. You can now specify attributes for regions and define desired values for those attributes, giving you the ability to target users with fine-grained accuracy, based on their interactions with your regions. With Region Attributes you can now create Automation rules that trigger notifications not just on a user’s entry/exit with any of your locations.
Our new Automation workflow gives you several new tools to control the exact time your message is delivered. You can easily configure message delivery windows by specifying valid hours of the day and days of the week. For example, you can define one window for weekday hours, and a second for weekend hours. You can also schedule one or more consistent times of day you want all messages to be sent, e.
Can we say we simplified something while also saying we expanded it? Well, we’re saying it. We updated our composer workflows, separating messages from automation rules, while also adding multiple new features. Here are the highlights. Improvements One button to rule them all: Instead of starting a message and later deciding its type, you now get started by clicking the Create New button, then choose between Message, Automation, and A/B Test.
If you’re an avid reader of these release notes, you’ll remember that in April we released Personalization Templates, supporting the concept of Little-p personalization via our API. Today we are excited to announce dashboard UI support for creating personalization templates. This has been one of our most requested features recently, as marketing teams are increasingly looking for ways to deliver more relevant, timely, you might even say personalized content without needing to rely on their development teams.
A/B Test response data is now available through two new public endpoints designed for both overview and detailed reporting. GET /api/reports/experiment/overview/(push_id) Provides an overview of the experiment (A/B Test) with overall response statistics per variant. See Experiment Overview Report for details. GET /api/reports/experiments/detail/(push_id)/(variant_id) This endpoint returns a detailed response for a specific variant of the experiments, broken out by iOS, Android, and Amazon devices. See Variant Detail Report for details.
When a user interacts with an A/B Test message, their next destination action is up to you. With the initial release of A/B Tests you had the choice to direct users to one of four actions: Home Screen Deep Link Web Page Social Sharing Today we are adding Landing Page to the Message Action options. A Landing Page is HTML content that appears as an overlay above your app.
Dayparting Now you can specify dayparts for targeting users in your peak audience windows. Daypart is a term borrowed from the broadcasting industry, used to denote times of day within which you would like to reach your target audience. Some recognizable examples from television and radio include Morning Rush, Afternoon Drive, or Must-see TV. Since advertisers know that the eyeballs (or ears) they are targeting are in abundance during those days and times, they will pay a premium to advertise during those dayparts.
Our Automation team has been hard at work this spring, bringing you Automation Timing earlier this month, and now two new types of triggers to add to our Automation product suite: Custom Event Triggers Cancellation Triggers Custom Event Triggers Trigger Automated Messages when custom events fire. If you’re using Custom Events, now you can trigger automated messages when we see these events. If you’re not using custom events, now is a great time to give them a look.
We are pleased to announce the release of the Engage Java Library 1.0.0. This release includes: Support for the channel, named user, and static list APIs. Major refactors of the push, scheduled push, reports, segments, and location APIs. An overhauled client class with support for async requests and callbacks. For details, please check out the Java library documentation, API examples page, or view the source on GitHub.
We’re excited to announce the release A/B Tests! Thanks to all of our customers who participated in the A/B Test beta. Your feedback was most welcome and helpful. We now support A/B Tests for up to 26 variants, so you might even say that we support A/Z Tests, A/B/n Tests, Multivariate Tests, or whatever the cool kids are calling them these days. To keep things simple, we refer to them as A/B Tests in our composer, and experiments in our API, located at:
Personalization is here! If you follow our blog, you may have noticed that we have been tackling the issue of personalization for a while. See Big “P” and Little “p” in Message Personalization for more background. tl;dr Big-P Personalization means delivering timely and relevant messages to users. Messages are based on a user’s tastes and preferences, they show up at just the right time, and they do not disturb or annoy the user.
Unity We’re excited to announce the 2.0 release of our Unity plugin. This release simplifies installation and setup, and adds support for a number of Urban Airship features, including: Channel registration events Tag Groups Custom Events Named Users Message Center See the changelog for the full list of changes. To download and install this new version, and register for plugin updates, head over to our package distribution site on Bintray.
Migrate Parse Apps to Urban Airship Update: Parse no longer supports the access of your data. See their archived Migration Guide If you’re looking for Parse alternatives for push notifications, please visit our docs home page. SDK SDK 7.0.0 We’re excited to announce the release of the 7.0.0 SDK versions for iOS and Android, featuring Out-of-the-Box Message Center. For details on upgrading to the new SDKs, see: SDK Migration Guides.
Automation Automation Limits Knowing when not to send a message can be as critical to your messaging campaigns as knowing when to send one. At Urban Airship, we understand the delicate balance between under- and over-engagement. And we are excited to announce the release of Automation Limits, a new app-level control option for Automated Messages. Automation Limits give you another tool to manage the engagement balance, beyond the message-level limits that exist today.
Automation Improved Message Response Reporting When viewing a Message Report for an Automated Message, you can now view sends, influenced opens, and direct opens for the timeframe you are viewing. Previously, only Lifetime Range data were shown above the graph visualization, regardless of the timeframe you selected. Example Data shown for last 30 days: Data shown for the lifetime of the Automated Message: For more information about Message Response Reporting, please see Message Reports.
Wallet Studio Dashboard We have redesigned the Wallet Studio Dashboard: For details, please see the Wallet Dashboard documentation. Automation UI We’ve added the ability to search through and filter your automated messages on the dashboard. To use this new feature, navigate to Messages » Messages Overview, and click on the Automated tab: At the top of the page you should see a search bar and a collection of filters.
Lifecycle Lists Last month, we released Audience Lists, a method for targeting custom lists of device identifiers. We are pleased to announce an upgrade to the Audience List functionality with Lifecycle Lists. Lifecycle Lists are similar to the previously released Uploaded Lists, but rather than being based on uploaded CSV files, they are auto-generated by Urban Airship: We currently provide three different list types: First App Open: Users that have opened the app for the first time in the given time interval.
SDK We’re happy to announce the release of the Urban Airship SDK version 6.1.0, which provides additional support for our spring release features. Highlights include: Tag Groups You can now easily add or remove tags to/from Tag Groups via the SDK. This functionality allows you to coordinate tag events that occur on the device with tag groups that may be primarily managed in a different database, e.g., a customer loyalty program.
In-App Messaging We are excited to announce the release of In-App Messaging: In-app messages are banner notifications that appear inside of your app. Aside from empowering you to engage with users as they browse your app, you can also reach opted-out users, a previously unreachable audience segment. In-app messages support all of the features supported by standard push messages, including Actions and Interactive Buttons. You can send in-app messages on their own, or you can include an associated push notification.
Mobile Data Bridge We are happy to announce the release of Mobile Data Bridge, a major update to the Urban Airship audience management toolset. The two main features of Mobile Data Bridge are Named Users and Tag Groups. Named Users are a system for mapping customer-chosen IDs to channels. Named Users supersede aliases, our previous CRM-mapping standard. Named Users Like aliases, Named Users represent users, i.e., devices. You may associate multiple Channel IDs with a single Named User ID, and when you push to a Named User ID we will send to each device associated with that ID.
Per Push Batch API The /api/reports/perpush/detail/ endpoint now supports batch requests. Now you can retrieve per-push reporting detail for up to 100 push IDs at a time. ` in our API Reference for details. --
Remove Tag Action You may now remove tags via the Message Composer: The Remove Tag action will remove a certain tag from a user’s device after the user interacts with a push. User Interface We made several small changes to the Dashboard UI. The Welcome Message section, under the Messages category, is now hidden by default. The feature will become visible once you enable the Message Center on the Settings » Configuration screen.
Reports A/B Testing Beta One of our most requested features is A/B Testing. We think it’s important to be able to find out what works for your users by trying different tone of voice, calls to action, or framing of a promotion. We have big plans for testing in the future, but we wanted to get some functionality in your hands right away, so we set up the A/B Testing beta program.
Reports Custom Events See the Custom Events Topic Guide for a complete overview of this new feature. Custom Events let you track user activities and key conversions in your app, and tie them back to corresponding push messaging campaigns. An Event can be tracked anywhere in an app where specific user actions are critical to the success of your app. Some examples: A retail app might record an event each time a user makes a purchase following a promotional message.
iOS 8 New Feature Roundup On September 17th, we made publicly available two major components of our iOS 8 feature support: iOS SDK version 5.0 API support for Interactive Notifications Coming in October, we will launch support for the use of these features in the Urban Airship web application as well as SDK and API support for the features on Android and Amazon with a new, combined Android/Amazon SDK.
Message Center Expiry This feature automatically removes time-sensitive offers and messages from a user’s Message Center, helping you keep your users’ content fresh and relevant. For example, you could set expiry for a Labor Day Weekend offer so that it is removed when the sale is over. The message would automatically disappear from the message listing, reducing clutter. Another example would be setting a standard, e.g., 6-month, expiry on all articles you publish, so that a user’s inbox never becomes too stale.
WWDC Roundup: New Feature Support Notification Actions: “category” API Support In iOS 8, a number of new options are introduced that allow users to interact with custom functionality in the context of a user task. These customization options are known broadly as app extensions. Today we are releasing partial API support for the Action app extension, which allows you to pass through the new category field in the APNS payload.
Tag on Open Events The Rich Page Editor now supports user tagging upon Rich Page open events, for both Rich App and Landing Pages. Previously, users could only be tagged upon interaction with the push notification, i.e., when tapping the notification alert. The “Tag on Open” setting supports a number of use cases in which no alert accompanies the rich content, e.g., sending only badge (no notification) to indicate unread Message Center content.
Wallet Beacon Support in PassBook Wallet Studio now supports beacons for PassBook passes. Enter up to 10 iBeacons per template to be loaded onto a consumer’s pass. When the consumer enters within range of a defined beacon, a notification and a pass icon will show on the lock screen. In order to manage iBeacons on passes, navigate to the appropriate project and click on the Triggers icon. This will bring up the Relevant Location information view.
Q1 Release Overview/FAQ March was a busy month at Urban Airship as we finished up the quarter by releasing a number of significant new features that will greatly enhance not only your user experience as an Urban Airship customer, but the experience of your app users. We’ll go into specific detail on each new of updated features below as they relate to the Urban Airship dashboard, API and Mobile SDKs.
User Dashboard Test Devices We’re happy to announce the release of one of our most requested UI features. Test Devices is a simple way to create and store a list of trusted devices, e.g., for your QA or Product teams, to test end-to-end message flow prior to pushing to a live audience. Test Devices is available to Urban Airship Enterprise Edition customers effective February 26th, 2014. For details on accessing and using this new feature, see Test Devices.
# User Dashboard Audience Report Display Messages in Local Browser Time Edit Scheduled Messages User Dashboard Audience Report The Audience Report provides a current view of your audience by the number of devices opted-in and out- of notifications for iOS and Android. It also includes your total opted-in uninstall count. The data is updated daily and you can view previous snapshots (back to Jan 1st, 2014).
User Dashboard New Composer Easier to Find We’ve made it easier to get to the new Composer. From the top of the Messages Overview page, click the “+ Message” button. You no longer have to click through to the old composers to get there. Alternatively, you can click the “Message” option in the shortcut button in the lower left-hand corner. Save Message as Draft In the New Composer, you can now save a draft of your work and come back to it later.
What are Ad IDs? Ad IDs are user-level IDs that are the same for a user over multiple apps on their device. They allow marketers to send content and ads to users that have not limited their ad tracking. Other services such as Facebook and Twitter capture the same Ad ID and have ad platforms to target specific users based on Ad IDs. This topic guide covers use cases and technical details on how to send Urban Airship Ad IDs so you can begin to optimize your user acquisition and re-marketing campaigns.
Overview The Urban Airship Event Templates provide a way to create custom events for common account, media or retail-related events. They are a wrapper for Custom Events and are available in UA Android 7.3.0 SDK. Resources Custom Events Guide Custom Events Quick Start Guide CustomEvent class Required Dependencies Analytics must be enabled to use this feature. Verify analytics is enabled boolean analyticsEnabled = UAirship.
This tutorial will cover how to build a custom Message Center. Before continuing, read Android: Message Center to see if the provided Message Center is suitable for your application. Message Center is provided out-of-the-box as of the release of SDK 7.0, and supports some basic theming options. This tutorial is for more advanced implementations. If you are looking for an out-of-the-box solution, see Out-of-the-Box Message Center. Message Listing The easiest way to display the Message Center message listing is to use MessageListFragment :
Android widgets provide a way to display a view of the app to the user on the homescreen or keyguard. When building widgets, you have full access to the Urban Airship SDK, including access to the app’s Message Center. The following example code shows how to create a home screen widget that lists the messages. This example utilizes the RemoteViewsService class in order to display a collection in a widget, making the widget incompatible with Android Gingerbread.
Urban Airship supports push to Apple Watch. This topic guide covers the new interfaces for Apple Watch notifications and the process of sending notifications to Apple Watch via the Urban Airship API. When testing Apple Watch notifications, keep in mind that you must configure it to receive notifications in the Apple Watch app on the connected iPhone. The Apple Watch must also be worn to receive notifications. Apple Watch Notification Display Styles When paired with a user’s iPhone, Apple Watch can display local or remote notifications in one of two interfaces:
What are Channels? Channels are a new way of addressing your application installations on iOS, Android and Amazon devices. With iOS 7, Apple drastically changed the way device tokens are issued, and to prevent a similar change from affecting our customers in the future, we create a Channel identifier for each installation which will map to an iOS device token if one is available. Android APIDs have been updated to the latest infrastructure and are now known as Android Channels.
Custom events let you track user activities and key conversions in your app or from your site, tying them back to corresponding mobile engagement campaigns. In this guide, we will show you how to implement custom event tracking from both within your app and on the server-side, tying activites from your website or CRM to users of your app. What are Custom Events? Urban Airship analytics reports on a number of different kinds of events automatically via our iOS and Android/Amazon SDKs.
The purpose of this guide is to provide code samples that can be easily implemented to get started with Custom Events right away. While you can certainly build on this functionality over time, this implementation will yield value immediately and give you a pattern to use in the future. The implementations below are intended to represent the highest impact Custom Event for a variety of business verticals, making it easy to pinpoint the best starting point for your app.
When an end user runs your application for the first time after installing it, a Channel is created and returned to Urban Airship. The channel registration automatically occurs on the application’s first run. This Channel then becomes the primary identifier used to address notifications and/or messages to the device. In special situations where you do not want channel registration to occur on the application’s first run, a configuration flag can be used to delay channel registration and a method can be used to enable channel registration.
This guide explains how to deliver Apple Wallet passes via push notifications. You can send a single unique pass to a specific customer, or create a shareable pass and push it out to as many customers as you like. The Pass URL If you don’t have one already, create a template in Urban Airship Reach, and use the Reach API to create a pass. The API also provides an option for creating a Public URL hosted at https://wallet-api.
This document is intended to provide a way to disable sending the GCM token, ADM ID or device token during channel registration. Disabling this will cause analytics and push notifications to not work correctly. Android By default, we send the GCM token or ADM ID during channel registration. Disable sending the GCM token or ADM ID To disable sending the GCM token or ADM ID during channel registration, you need to disable analytics and disable sending the token during takeOff.
With the Urban Airship API, you can design and automate a complex messaging strategy, retrieve detailed analytics, and more. In order to help you begin testing in your own environment we have pulled together a collection of common use-cases, providing example requests in multiple languages. This guide is neither an introduction to the Urban Airship API nor a full reference. Rather, this document serves as a middle ground— you should have a high-level understanding of our APIs before proceeding, but you are not expected to be an expert.
In-app messages are banner notifications that appear inside of your app. Aside from giving you the power to engage with users as they browse your app, they allow you to reach opted-out users, a segment of the app audience previously unreachable with this type of messaging. With in-app messages, you can: Create relevant, branded in-app messages that interface with existing Urban Airship features (e.g. Actions, Interactive Notifications, etc)
The purpose of this guide is to help you get started with the new In-App Messaging feature in Urban Airship’s Composer. For more details on how In-App Messaging works, see In-App Messaging. In-App Messaging requires Urban Airship 6.0 or later SDK. There are a number of ways to send an In-App Message, whether in conjunction with a push notification or on its own. In-app messages can use zero, one, or two interactive Notification Buttons.
Interactive Notifications iOS8, Android, and Amazon support push notifications with additional buttons for secondary, complementary actions, allowing users to interact with notifications from outside of the app. There are a number of common options for actions that are enabled by the Urban Airship SDK (5.0 or later). Additionally, you can define any number of custom interactions for a specific use case. Interactive Notifications can drive the user to: Take immediate, specific action
This guide is a quick walkthrough of downloading one of our Lifecycle Lists in CSV format. Each Lifecycle List row includes your users’ channel IDs , which you can associate with your backend system. Downloading a List To download a Lifecycle List you must be either an Owner or Adminsistrator. Please note that once initially enabled, your first Lifecycle Lists will be available in 24 hours. The delay is necessary in order to populate the minimum data required for the shortest time interval: Last Whole Day.
Lifecycle Lists are Urban Airship-generated Audience Lists that group users based on certain lifecycle events. Use these lists to target users with personalized messages based on these behaviors. You can: Specify a Lifecycle List as your recipient group when selecting your audience in the A/B Tests or Message composers. Include a Lifecycle List as an audience segment in the Segments Builder. Download Lifecyle Lists and add the users to your CRM or other backend system.
Location Triggers are an out-of-the-box way for you to send real-time Automated Messages to your audience as they enter or exit a specific geographical location. Location Triggers introduce a more dynamic application of location-based notifications, moving beyond historical location and segmentation to real-time triggers based on users’ movements in and out of geofences and proximity to beacon signals. Urban Airship Location Triggers rely on coordination between two technologies: Urban Airship Automation and the Gimbal Platform.
Actions are a powerful way to enhance the user experience of your app users. From a technology perspective, the Urban Airship Actions framework represents a big leap forward in the potential use cases surrounding mobile messaging. Actions introduce a level of sophistication to mobile messaging previously unseen, and combined with other Urban Airship products and features such as Automation and Rich Pages, dramatically extend your ability to measure the interplay between your messaging strategy and user behavior.
Mobile Data Bridge enables you to segment your audience based on both mobile and non-mobile data. The data sources are Named Users and Tag Groups, working together to optimize your segmentation and targeting capabilities. Bridging Mobile and Non-Mobile Data In the context of our customers’ end/app users, user data must exist as a tag (metadata) in order to function as a targeting mechanism for notifications. This metadata is easily associated with a user’s mobile device by using Urban Airship’s tagging functionality.
This topic guide will give you ideas on how to use the new Mobile Data Bridge functionality with your app. We begin by elaborating on the general problems solved by Mobile Data Bridge, and then proceed to give specific use cases. Unify Mobile and Non-Mobile Data Mobile Data Bridge serves multiple purposes, but its core functionality is to unify mobile and non-mobile data. In the following section, we’ll examine how Tag Groups and Named Users work together by examining a simple example: pushing to a segment created with mobile and non-mobile data.
At Urban Airship, we provide our customers with tools for every step of the customer lifecycle, from user acquisition to conversion to engagement to retention. This topic guide focuses on user retention, specifically, identifying the risk factors in your user base that lead to attrition, or churn. Churn is a natural component of mobile engagement ebb and flow, and while a certain amount of churn is normal and healthy, there are ways to identify churn risk factors and mitigate the erosion of your user base with corrective action.
Urban Airship announced support for Apple Watch in February, and reporting is a major area of interest. This step-by-step guide provides instructions for implementing Custom Events and Tags to report on engagement and segment for future messaging. If you want to identify when a user views a notification on their Apple Watch or interacts with that notification, and be able to create segments that include or exclude these users, follow these steps.
This topic guide covers the Static List API workflow and integration process. Static Lists are great for targeting groups of users with similar characteristics which are tracked externally, e.g., in your CRM system. For example, if your CRM is tracking customers interested in weekly offers, you can create a weekly offers list in Urban Airship, upload the user list, and manage list membership based on changes in your CRM.
This walkthrough will guide you through the process of creating and using your first Tag Group. Before you attempt to create a Tag Group, you must complete a very important preliminary step: Step 0: Learn about Tag Groups and the audience management problems they solve by closely reading the Mobile Data Bridge Primer. It is difficult to adequately emphasize the importance of Step 0. As you will discover, the process of creating and using a Tag Group is simple, assuming you understand what a Tag Group is.
While Urban Airship supports tracking of rich page opens out of the box, often customers like to track opens and clicks within a Rich Page with a third-party tool like Google Analytics. Setup These directions assume you already have created a Google Analytics account. Go to the Admin page in Google Analytics. Under the Property menu, select “Create new property” and name it something like “Urban Airship Rich Pages”
Beginning with Windows Phone 8.1, Microsoft supports push notifications for mobile apps via WNS, the notification service previously available only for desktop applications. According to Microsoft: “The Windows Notification Service (WNS), and its associated APIs, represents the common push notification service platform being used by all Windows Phone Store apps today, and in the future”. (Choosing MPNS or WNS for a Windows Phone Silverlight 8.1 app, Windows Dev Center)
This is a collection of example Push API V3 payloads for WNS. Platform Specific Section In order to send to Windows devices, you must choose wns as the device_type. See Audience Selection for mor detail. The platform-specific key for WNS is wns. The data format is a JSON mirror of the XML schema for WNS. Common Data - WNS Header Fields There are 3 values in the wns section which are common to all push types, and are sent as HTTP headers in the native WNS payload.
What is iBeacon? iBeacon is a new technology that extends Location Services in iOS by monitoring for proximity to a new class of Bluetooth-powered transmitters that emit information about their presence. Any compatible iOS device with iOS 7 or later, Bluetooth enabled, and Location Services opted in can receive the information and take action based on this transmission. For more detail about device compatibility, please see iOS: Understanding Beacon.
Deep linking is a technique that allows an app to be opened to a specific UI or resource, in response to some external event. By implementing a deep linking strategy, your app becomes more responsive and capable of navigation to arbitrary content in response to push notifications, much in the same way that URLs can link you to specific pages on the Web. With the Actions Framework, the Urban Airship SDK now supports opening deep links from push notifications, and through Rich HTML content interactions.
Overview The Urban Airship Event Templates provide a way to create custom events for common account, media or retail-related events. They are a wrapper for Custom Events and are available in UA iOS 7.3.0 SDK. Resources Custom Events Guide Custom Events Quick Start Guide UACustomEvent Required Dependencies Analytics must be enabled to use this feature. Verify analytics is enabled let analyticsEnabled = UAirship.
Starting with Urban Airship SDK 7, apps have access to a default Message Center which requires little to no integration to get started. However, most developers will want to customize the look and feel to match their existing style and layout. This topic guide cover the various tools available for creating custom Message Center implementations, starting with the simplest and moving on to more advanced use cases. The Default Message Center As its name suggests, the default Message Center is an out-of-the-box Message Center implementation built into the Urban Airship SDK.
As of iOS 8, apps can now deploy associated widgets to the Today screen in the iOS Notification Center. This topic guide will cover how to build a custom widget that embeds a message center in the user’s Today screen. Use cases for this may include apps that either don’t need or can’t include a message center in their own UI, as well as the desire to allow users to check for new messages without needing to launch the parent application.