![]() ![]() In my case, we have over 6,000 users and about 300 using the app once every few weeks (which having these analytics helped me discover). This isn’t great, depending on the size of your organization and the app. So for every 1,000 actions, you’re consuming a month’s worth of runs for a user. Your tenant gets 2,000 flow runs per user per month. These flows will run each and every time an event needs to be captured. This approach is using 2 flows to capture analytics. Then use a SharePoint Create Item action.I created a flow with the trigger “When a HTTP request is received”.My first one is the connection with Power Apps, and it gets the current user’s profile info, then it calls my second flow: Using Microsoft Power Automate, you can streamline some of your data processes and what fields are truly necessary, what fields could use default values, along with looking up data in other data sources like someone’s job title, department, etc. I could have had Power Apps attach directly to my SharePoint list each and every time I want to write into it, but you’ll find that that brings in more work than it’s worth, also, not sure we could keep it anonymous. UID is a hashed version of the user’s email address, so we can track session based activity without actually seeing who it is.I’m keeping the analytics anonymous (note Created By is generic), but want to capture some basic demographics. Department and Job Title are about the user doing the clicking.Data is a catch-all for anything else I may need to capture.Screen will store what screen the user is on.I decided against a lookup column to the Events list since there is some unnecessary complexity in getting that data into SharePoint from Power Automate. EventID will store the row ID of the event, it’s just a number field.I renamed Title to Activity, this will store a word or two of what activity we just tracked, like View Event or Share Event.Here is an example of an analytics list I created in SharePoint: Ultimately anything the Power Platform (in this case Power Automate specifically) can connect to we can use. ![]() Alternatively, we can use a cloud database or other data store to collect the analytics. There is a view threshold limit on the lists but our reporting will actually be done outside of SharePoint. Traditionally, I have used a SharePoint list because they’re really easy to create and set up and easy to grant permission as needed. Fortunately, due to the asynchronous options in Power Apps, we can add analytics with no impact on the user experience.įirst, we need to create the repository to store the analytics. Capturing Analytics with SharePoint and Power Automate (Flow)Īs users interact with your app they are clicking on buttons, pressing on items in galleries, and managing data. We now want to track the other “stuff” users can do: viewing events, sharing an event with a colleague via email, using filtering, etc. Many of the typical info we’d want to know, like sign-ups, check-ins, feedback, is already being tracked since all that data is being saved. After the event, provide feedback on the event.During the event, check in to share you’re there and see who else from Slalom is there.When signing up, it’s added to your Outlook calendar automatically.Sign up for a networking opp, and see who else is signed up.We are trying to maximize the value of networking and enabling our consultants to attend events in and around Boston. I created a Power App to share networking events for consultants in Slalom Boston to attend. Background on my Power Appīefore we begin, let me explain the app we’re using as the example. In Power Apps, we have a workaround to capture interactions by the users and provide some pretty valuable insights on how our applications are being used. In Power Apps, though it is a web-based application, we cannot integrate with external providers in the same manner. Again, there are solutions available like Adobe Analytics which capture this for a standard web-based application. However, unlike basic webpage analytics, like the number of viewers, applications should be gathering additional insights like click events and other interactive information so it can help us further enhance the product for our users. In the wild, these insights are usually provided through an analytics platform like Google, Adobe or a myriad of others. Shouldn’t we expect the same insights in our Power Apps? As you see certain features being used, or not, you can make pivotal decisions to enable, expand, build on top of or otherwise improve your app. With these insights, you can decide how to mature and grow your product. Modern development practices encourage gathering insights from your users’ interactions within your application. This is a pretty simple concept that can bring tremendous value and insight to you, the creator of a Power App. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |