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. Directly below the Relevant Location is a new option to add beacons. You may use the existing location triggers as well as Beacon triggers either separately or in combination.
Fill out the Beacon UUID, major/minor values, and the notification text you wish to appear on the lock screen. These can be edited or deleted as needed.
Any changes made to the template for location will be applied to all new passes that are created. Existing passes can be updated in batch with our bulk update API call.
Offers Support for Google Wallet
Wallet Studio now supports Google Wallet Offers templates. Consumers can save offers and coupons to their Google Wallet account by using the “Save to Google” button on websites and emails. Consumers can then use the offer in store by showing or scanning their mobile phone at time of purchase.
Use the drag and drop wizard in the Wallet Studio to craft the offer and then utilize the Save to Wallet feature to distribute the offer to consumers. In order to create a Google Wallet Offer, use the Coupon pass type when creating a new project, or use an existing Coupon type project. Add a new template and click on the Google Wallet option. You can now customize your offer just like any other pass type. You can also reuse existing fields from other templates that you may have already created.
Once the Offers template is ready, simply save it and utilize the Save to Wallet functionality to distribute. You can also make updates to offers that have been distributed just as you would with Google Loyalty Cards.
Single Device Validation
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: