{"id":11512,"date":"2018-10-22T10:16:27","date_gmt":"2018-10-22T10:16:27","guid":{"rendered":"https:\/\/passkit.com\/blog\/?p=11512"},"modified":"2021-01-22T18:21:36","modified_gmt":"2021-01-22T18:21:36","slug":"how-to-engage-your-customers-with-the-apple-wallet-changemsg","status":"publish","type":"post","link":"https:\/\/passkit.com\/blog\/how-to-engage-your-customers-with-the-apple-wallet-changemsg\/","title":{"rendered":"How to engage your customers with the Apple Wallet changeMsg"},"content":{"rendered":"

A few months ago one of our client’s wanted a solution that would push engaging messages to their customers passes based on their activity. Using the Passkit API<\/a> this is a very straightforward task but I thought it would be good to document the use case in the hopes that it might inspire someone else to utilize the same features.<\/span><\/p>\n

This post won\u2019t go into how our clients CRM system works or the technology we used to handle the processing. I will only be going over the features in Apple Wallet and the Passkit API that allowed the solution to work. Also, this post assumes that you already have the knowledge on how to create and update passes and templates.<\/p>\n

Firstly, for the sake of the demo, I should point out that our client’s customer database had fields that could drive actions. Let\u2019s assume that\u00a0we have a data model for customers that includes a birthday. We can use that to drive meaningful push notifications to our customers.<\/p>\n

\n

Apple Wallet changeMsg<\/strong>
\nApple Wallet extends a very useful field called changeMsg. When changeMsg is updated, a push message notification is sent to the user’s device with a message that you can define.<\/span><\/p>\n

The change message field is defined in your pass template on the back of the pass. More information can be found here<\/a><\/span><\/p>\n

Let\u2019s say that\u00a0we wanted to add the changeMsg to you current pass template, all\u00a0we need to do is update\u00a0our template to include this field to\u00a0the backfields:
\n[javascript]
\n{
\n“back”: [{
\n“defaultValue”: [{
\n“changeMsg”: “%@”,
\n“defaultLabel”: “Latest updates”,
\n“defaultValue”: “#{message}”,
\n“format”: {
\n“type”: “text”,
\n“dateFormat”: “medium”,
\n“numberFormat”: “decimal”
\n}
\n}]
\n}]
\n}
\n[\/javascript]<\/p>\n

Updating\u00a0the template will add a new backfield with the label Latest Updates to\u00a0our pass as seen below<\/p>\n

\"Screen<\/a><\/p>\n

\n

Now that we have updated our template, the next thing to do is update the field with the message that we want.<\/p>\n

Let\u2019s say that\u00a0we decide to run a batch job every day that checks all of your customers to see if it anyone’s birthday if it is, they should receive a personalized push notification on their device.<\/p>\n

To send a push notification to the customer’s device, all\u00a0we have to do is update the message field in the dynamicData of the pass:
\n[javascript]
\n{
\n“dynamicData”: {
\n“message”: “Happy Birthday Jesse! Come in today for a free gift”
\n}
\n}
\n[\/javascript]<\/p>\n

A push message notification will be sent to the user with your specified message<\/p>\n

\"Screen<\/a><\/p>\n

The back of the pass will then be updated with the latest message<\/p>\n

\"Screen<\/a>
\n**The change message filed will only update if the message field is\u00a0different from the one currently there, so be careful not to send duplicate messages, as they will not trigger the lock screen notification**<\/strong><\/p>\n

Please feel free to let us know any other interesting use cases that you have found where the changeMsg\u00a0made a big difference. We love to hear about the cool stuff people are building.<\/p>\n","protected":false},"excerpt":{"rendered":"

A few months ago one of our client’s wanted a solution that would push engaging messages to their customers passes based on their activity. Using the Passkit API this is a very straightforward task but I thought it would be good to document the use case in the hopes that it might inspire someone else […]<\/p>\n","protected":false},"author":14,"featured_media":13754,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12,15,16,31,33,37],"tags":[55,57,58,61,138,163,212,231,249,264,266,274],"class_list":["post-11512","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-apple-wallet","category-blog","category-case-studies","category-mobile-wallet-2","category-passkit-api","category-tech","tag-apple","tag-apple-passbook","tag-apple-pay","tag-apple-wallet","tag-digital-wallet","tag-how-to-use-passkit","tag-mobile-marketing","tag-pass-kit-api","tag-passbook-ideas","tag-passbook-samples","tag-passbook-solutions","tag-passkit"],"_links":{"self":[{"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/posts\/11512","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/comments?post=11512"}],"version-history":[{"count":2,"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/posts\/11512\/revisions"}],"predecessor-version":[{"id":15959,"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/posts\/11512\/revisions\/15959"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/media\/13754"}],"wp:attachment":[{"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/media?parent=11512"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/categories?post=11512"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/passkit.com\/blog\/wp-json\/wp\/v2\/tags?post=11512"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}