Introduced as Region Attributes in our API, we now have UI support for this feature, via a new Automation rule event trigger: Location Attributes.
Location attributes are key/value pair metadata associated with a particular location, e.g., chain:BobsBurgers, has_blender:yes.
Using that pair, you can trigger an automated message to any user who enters a Bob’s Burgers franchise location that has a blender* and offer them a deal on a milkshake.
If you have more than just a few Engage projects, switching between them just got easier.
For starters, the dashboard list of your projects now loads in milliseconds, and searching and filtering projects after that is instantaneous.
Next, if you have more than eight projects, we display your four most recently accessed projects at the top so you don’t have to scroll or search to return to them.
Now you can track user activities and conversions on your website with Custom Events. Track common account-, media-, or retail-related events using ready-made Custom Event Templates, or create your very own bespoke, hand-crafted, artisanal events.
We’re excited about the rapid pace of devlopment on our Web Notify product line. Since launching in May 2017, we have added support for Insight, Connect, and now Custom Events, with lots more coming later this year.
iOS SDK Updates Apple is releasing iOS 11 on September 19, 2017, and in preparation released their Gold Master this week. If you are looking to launch your iOS app with full iOS 11 support, we’ve got you covered.
If you are targeting iOS 11 in your build, and/or using Xcode 9, we recommend that you update to our latest SDK to remove build warnings and address the few minor issues addressed in the changelog below.
Effective today, all Web Notify events, which include web sends, clicks, sessions, and uninstalls can be streamed in real time using Connect. Combined with Named Users, our user-mapping utility, this release takes you one step further in your omnichannel user engagement strategy.
Web Notify events now supported in Connect:
SEND WEB_CLICK WEB_SESSION UNINSTALL See Connect Event Types in our Connect API reference for details on these and other event types.
Today marks the first GA release of our Channels API extension, open channels. This new platform service extends the Channels API to send a notification to anything. For the first time, a customer can send personalized, interactive notifications at the right time and place across their digital marketing stack.
We built this to address a growing market need from enterprise businesses faced with an unprecedented expansion of marketing technologies and notification channels: a centralized platform from which to send 1:1 notifications to each of their customers in the optimal moment, and to any device or messaging platform.
Following on our initial support for Android O, today we added support for Android notification categories in the Urban Airship Engage dashboard. Notification categories allow your users to manage notification settings for each category that you have defined for your app, e.g., “promotions” or “breaking news”. Categories represent the Android notification channels that you implement in your app. It’s as easy as 1-2-3 (🎶 As simple as do-re-mi, A-B-C, 1-2-3, baby, you and me, girl… 🎶):
We’re pleased to announce support for tvOS 10 in our latest iOS SDK release: 8.4.0. This release includes support for building a tvOS-compatible framework that can be integrated into any project running tvOS version 10 and above.
The tvOS framework supports the following features:
Remote badging Content-available notifications Analytics (Including Urban Airship Connect and Insight) With these features you can implement some of the following use cases:
Badging an app icon to draw users’ attention to new content.
Furthering our commitment to customer security, and adding to our recently released set of enterprise security features, today we have enabled a new security feature for all customers: the Team Activity log.
Now account Owners can view a record of their users’ key activities within Urban Airship, from login/logout to sending messages or editing segments. If something unexpected happens, you can see who did what and when.
Get all the details in Managing Your Account: Team Management: Activity.
As a Connect customer, you can now integrate server-side custom events with your business systems. We have added a new source attribute to the Custom Event object that specifies the origin of the event, either your app or your server.
All events sent via our server-side custom events API can now be streamed in real time via Connect. See custom events in our Connect API reference for details on the custom event object.
Announcing the general availability of our web notification solution, Web Notify, for enterprise customers. Web Notify is available as a standalone service or in combination with our Engage platform. Whether or not you have a mobile app, you can now use Urban Airship’s world-class messaging platform to target mobile and desktop browsers.
The feature set of this first release includes:
API & UI support. Web Notify is fully integrated into our existing Message Composer.
Today we shipped a powerful set of new enterprise security features to further protect your data. In response to a growing number of requests from our enterprise customers, we are enhancing our user management framework to include Security options:
Password Reset requires users to update their password after 90 days. Unique Password Requirement tracks previously-used passwords to prevent reuse. Block Multiple Sessions helps prevent login sharing to promote accountability.
We’re pleased to announce support for IoT devices running Android Things. And by ‘announcing support’ we mean ‘it just works.’ So you can think of this as more of a serendipitous discovery than a release note but still. We wanted you to know. Thanks, Google!
Push notifications, In-App Messaging, Message Center, and analytics are all supported. Send data to and and run Urban Airship Actions on your connected devices.
Simply install the Urban Airship Android SDK in your Things project as you would in and Android project, and take advantage of (nearly) all the notification and messaging features Urban Airship has to offer.
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 UI 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 Builder 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:
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
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.
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.
Making Room for New Features and Functionality We have rolled out some changes in the navigation for our web dashboard. Don’t fear: we haven’t actually moved anything! We’re just making navigation simpler across the product to accommodate some exciting new products and features related to messaging and A/B/n testing.
Engage Navigation Moves Up Engage navigation has moved from the left-hand side of the page to the top, just above your workspace.
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.
Out-of-the-Box Message Center makes Urban Airship’s flagship rich messaging feature, Message Center, available to all customers using iOS or Android SDK 7.0.0 or later, without requiring a separate integration. Read on for context, a description of the benefits, and for links to additional resources.
What Is Message Center? Urban Airship Message Center is a place in your app where you can display persistent rich messages, including HTML, video, etc. The messages are hosted by Urban Airship, and are typically displayed in standard inbox-style within your app.
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.
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.
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.
Getting started with Urban Airship’s engagement services just got easier. The new Quickstart Guide, located in Go, will walk you through the process of integrating our SDK, uploading certificates, and sending a test push:
Please see the Getting Started guide for more information.
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. You can filter your messages by trigger type and status. For details, please see the user guide documentation.
The Urban Airship SDK collects huge quantities of data on user devices, and we are now making this data available to you in the form of Device Property Tags:
With Device Property Tags, you can target users based on the following device-centric information:
Locale country setting
iOS/Android app version
Notification opt-in status
Background push status
Location enabled status
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.
Support for a granularity of minutes when creating Location Segments has been deprecated.
See Time Period Specifier in our API reference for information on valid time resolutions, and Geographic Location Criteria for User Guide instructions.
We now offer official support for a Ruby library which handles requests to our push and scheduled push endpoints. The library was previously open source, but will now be officially supported along with our other supported server libraries.
For details, please visit the Ruby library documentation, or get up and running quickly by viewing some of our Ruby examples on the API examples page.
We are excited to announce the general availability of Location Triggers, which had previously been in beta. Thanks to all of our beta customers for the feedback!
Location Triggers extend the functionality of Urban Airship’s Automation toolset, introducing a fourth option for setting up Automation triggers, in addition to existing tag, inactivity, and first open trigger options.
For more detailed information about using Location Triggers, see our Location Triggers topic guide.
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.
We now support uploading custom lists of device identifiers for message targeting:
If you collect data on customers via a CRM database or some other backend system, you can start putting this information to use by generating targeted device lists. For example, if some users on your website have indicated interest in weekly offers, create a Weekly Offers Audience List containing the device identifiers associated with those users, and then push to that list.
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 Notifications. You can send in-app messages on their own, or you can include an associated push notification.
Urban Airship now supports push to Apple Watch!
To start pushing to this exciting new platform, see our topic guide on Apple Watch display styles. If you would like to push to Apple Watch using the API, please read about the title and category keys.
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.
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.
Additionally, we have altered the Message Composer checklist UI. Previously, this sidebar would track your progress as you created a message:
As you worked through the message creation process, green checkmarks would appear alongside completed steps.
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.
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. To gain access, contact your account manager to learn more, and then enter into a Beta Agreement.
We have added an option to our UI to deliver a notification to iOS with the Content Available Flag:
When this flag is present, your notification will wake up your app in the background to preload content or perform any other custom background processing. These notifications can be sent with or without notification text. Here are some example use cases:
Silent Push - Send a notification with the Content Available flag on, but without user notification text.
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.
The Message Composer now supports Interactive Notifications. You can choose from the 27 built-in interactive notification types provided by Urban Airship.
The main difference between a standared push notification and an interactive notification is the addition of buttons that prompt a user to take specific action outside of the app:
In the above example, selecting Shop Now may take you to the Woman’s sandals section of The Ship, while clicking Remind Me Later could trigger a reminder notifiication that will be sent after a delay.
Custom Events on the Message Report If you have Custom Events set up in your app, you will now see events associated with a push notification on that notification’s Message Report. The table will appear at the bottom of the report, and detail events attributed to that push notification.
This table will show events directly or indirectly attributed to the push notification, and any value associated. The columns are sortable.
The “Rich Push Users” page has been removed from the “Audience” tab in the left-hand navigation menu.
With the release of version 3 of the Urban Airship API and Channel identifiers, there is no reason to be concerned with, let alone manage Rich Push Users from the UI. If you rely on this feature, contact Urban Airship Support.
The share action requires use of our new SDK, 5.0 or above, available for iOS8, Android, and Amazon.
Last month, we introduced the share action to the API. This month we have enabled Share Action support in the dashboard via the Message Composer.
In the example of a Yes or No interactive notification below, a user’s interaction with the Yes option will take the user to the app via the experience you select.
A user’s level of interest in your app is typically highest at the moment he or she downloads the app and interacts with it for the first time. Studies have shown that a user’s failure to reengage with the app within the subsequent 7 days is a strong signal that the user will never open the app again.
In order to address this severe attrition risk, we are introducing the First Open Automation trigger.
The Message Center and Notification Expiry features have been redesigned to encourage use of the default push platform expiration value. The Notification Expiry option now hides the expiration field, auto-selecting the Default option:
The Default option depends on platform:
APNs: Indefinite expiration (approximately 1-2 weeks)
GCM: 4 weeks
ADM: 1 week
To enter a custom expiry time, select Specify to reveal the entry form, and enter the desired value:
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. Stay tuned for more details in October.
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.
Urban Airship now provides support for push and rich messaging to Amazon devices:
This release includes:
Message Composer Support
Rich Pages: delivery as Landing Pages or to a Message Center
Rich Actions: push to URL, Deep Links, Dynamic Segmentation
Push-level Analytics (deeper reporting after initial release)
See our blog post for an overview, or view the platform docs.
Push to Local Time is an option when scheduling a message to have Urban Airship deliver it at the same time of day, no matter what time zone your audience is in. For example, if you were a national restaurant chain, you could deliver a push message or rich content “Special lunch offer, 50% off” that arrives at 10:00 AM whether the user is in New York City, Chicago, or Honolulu.
Statistics Report The (app) Statistics Report has been updated, with better presentation of metrics and new tooltips with relevant help text. The updated Statistics Report provides greater context and serves as a simple, current snapshot of your app’s installations and notification sends:
Push Response Report The Push Response Report has been updated to present a more streamlined visualization of app open attribution.
The new Push Response Report design presents the total Opt-in Opens , Direct Opens and Influenced Opens side-by-side for the relevant time period.
Automated Messages can now check a device’s tags to determine if the message should be sent or not. This feature lets you target your audience at a more granular level, adding an additional filter for relevance.
Tag Conditions will check devices for the existence or non-existence of the tag(s) before delivering or not-delivering the specified message.
See the Tag Conditions UI documentation or API documentation for more information.
The Billing History table now brings a full view of your monthly billing metrics to the dashboard, broken out by app and by platform. The chart includes the top 20 apps that contribute to your monthly bill. For customers with more than 20 development apps, complete billing information is available via the CSV downloand feature.
This layout will help you more easily track billing information over time and see how apps (and plaftorms) compare head-to-head.
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.
iOS 8 is in developer preview as of the date of this release (July 1, 2014), and the information included here is based on the technical information disclosed by Apple at 2014 WWDC regarding iOS 8.
Channels are a new Urban Airship-specific identifier that will replace the device token as the primary means of addressing an iOS device for notifications, messages, and metadata.
Depending on how your app interacts with device tokens today, you may need to take steps to update your Urban Airship integration, but in most cases, the transition to Channels will be seamless.
For a more detailed look at Channels, see: Channels Primer.
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.
See Rich Page Tags for documentation.
You’ll notice a small change in the Message Composer when selecting the Single Device audience option.
This a small change to this interface that introduces validation lookup in our system for the device identifier that you enter in the text box. If the device does not exist, an “Invalid device ID” error appears after clicking “Validate device ID.”
Invalid device ID error:
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. These three interfaces with Urban Airship all have their own role to play in this quarterly release, but the short version is that we have added new functionality in four major areas:
Now that the sending of Rich App Pages (formerly known as Rich Push Messages) is handled in the same workflow as push notifications in our Message COmposer, it’s time to say goodbye to Rich Push Composer.
Today we are announcing that we will retire Rich Push Composer on March 31, 2014. If you are currently using Rich Push Composer to craft and send Rich App Pages, please familiarize yourself with the new sending workflow.
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.
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). The report is downloadable in CSV format making it easy to download multiple snapshots for comparison.
This is now the Devices report.
Until today in the Urban Airship UI, most dates were displayed in GMT. With this release, wherever possible we will display dates and times in the end user’s local browser time. This provides a simpler solution for most of our customers, removing the additional step of calculating time offsets.
Most of the time, the browser time will be accurate. However, it can can diverge if, for example, you travel and don’t have your device set to update its time zone automatically.
With this release we provide the ability to edit a scheduled message. Previously we only provided the ability to cancel a message that has been scheduled but not yet sent. This feature enables customers to both open a message to validate its accuracy and to edit that message with necessary changes.
To edit a message, just click on the new edit message icon, and the message opens up in the push composer.
Custom HTML Preview Now when you upload custom HTML to send as a Rich App Page, you have the ability to review what you’ve uploaded. Just click the “Preview” button:
This displays the same preview window you get with the template editor where you can test the layout in several mobile device types:
From the History section of the Messages Overview page, you can now click on the plus icon to duplicate a sent message. If the message was originally created in the new composer, the duplicated message will open into the new composer. If the message was created in the old Push or Rich Push composers, the duplicated message will open in that old composer.
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.
Now you can push to a set of tags in the New Composer. Rather than having to first create a segment, you can select them in the same message composer. Push to tags is still represented in our new Composer and API as a type of audience segment. You can choose an existing segment, or a tag segment you create on the fly:
This is a change in behavior from the old Push and Rich Push composers, where you had to first create a segment in the Segments area of the UI.
In the New Composer, you can now save a draft of your work and come back to it later. Click the dark gray “Save as Draft” button in the upper right to save changes. After clicking, the button turns light gray to confirm your changes are saved.
This is a change in behavior from the old Rich Push composer, which saved drafts automatically but did not provide feedback when it was saved.