As more and more Australian companies are bringing out quality mobile apps that add real value to the consumer experience, the app usage data that is collected is becoming more and more valuable both for customer experience and retention gains as well as insights and segmentation.
The likes of Myer and co who have intelligently created smartphone apps whereby they collect customer and purchase data at Point-Of-Sale (POS) and have communications triggered off the back of it are closing the business intelligence loop between what they are selling and who is it that is buying. This is really important as they can use marketing automation to keep the flame alive in 'hot leads' whilst provide some fantastic reporting on who really is buying what.
A bit about App data
App data is great because there is a lot you can capture that can tell you a great deal about the person that is using it such as the device type, the operating system, the carrier, their telephone number, what they've spent with you, usage logs and much more provided you have their permission of course. However, app data is a bit like a bank transaction account, it gets used a lot and so there's a lot of data - huge amounts of it.
Getting bogged down in storage
Many companies with this in mind spend quite a bit of time integrating this data into their data warehouse and coping with the huge volumes coming in. So when it comes to use cases, generally speaking it may be that the business will chose something simple such as - "Okay, let's just send out a trigger communication (an email) to anyone who has used the app in the last day or so with generic messaging about the latest offers." In that way they can achieve a use case quickly and efficiently (without spending too much time devising complicated models whilst at the same time not using too much server load running the procedure).
What more could you be doing?
Generally speaking, the app usage data is like every single one of your customers having a conversation with you. When they exit out of the app in less than 5 seconds they are saying maybe the app is buggy or perhaps they've logged in and realised there wasn't really much interesting in there and so they will move on to something else. However, it might only be with certain segments of your customers that they do this such as a young age group or gender. Being able to drill down and build models on this data could mean the success or failure of your app. It could mean the success or failure of your customer retention strategy. Or it could mean the success or failure of your businesses attempt to stay ahead of the curve in the digital age.
Either way, my advice is that if you have app data, delve a bit more deeply into it. And if you don't have the skills in-house, get them! Private message me if you would like to get someone in to your business today.
The likes of Myer and co who have intelligently created smartphone apps whereby they collect customer and purchase data at Point-Of-Sale (POS) and have communications triggered off the back of it are closing the business intelligence loop between what they are selling and who is it that is buying. This is really important as they can use marketing automation to keep the flame alive in 'hot leads' whilst provide some fantastic reporting on who really is buying what.
A bit about App data
App data is great because there is a lot you can capture that can tell you a great deal about the person that is using it such as the device type, the operating system, the carrier, their telephone number, what they've spent with you, usage logs and much more provided you have their permission of course. However, app data is a bit like a bank transaction account, it gets used a lot and so there's a lot of data - huge amounts of it.
Getting bogged down in storage
Many companies with this in mind spend quite a bit of time integrating this data into their data warehouse and coping with the huge volumes coming in. So when it comes to use cases, generally speaking it may be that the business will chose something simple such as - "Okay, let's just send out a trigger communication (an email) to anyone who has used the app in the last day or so with generic messaging about the latest offers." In that way they can achieve a use case quickly and efficiently (without spending too much time devising complicated models whilst at the same time not using too much server load running the procedure).
What more could you be doing?
Generally speaking, the app usage data is like every single one of your customers having a conversation with you. When they exit out of the app in less than 5 seconds they are saying maybe the app is buggy or perhaps they've logged in and realised there wasn't really much interesting in there and so they will move on to something else. However, it might only be with certain segments of your customers that they do this such as a young age group or gender. Being able to drill down and build models on this data could mean the success or failure of your app. It could mean the success or failure of your customer retention strategy. Or it could mean the success or failure of your businesses attempt to stay ahead of the curve in the digital age.
Either way, my advice is that if you have app data, delve a bit more deeply into it. And if you don't have the skills in-house, get them! Private message me if you would like to get someone in to your business today.
No comments:
Post a Comment