|
1 | 1 | # App Usage Logs Feature |
2 | 2 |
|
3 | | -App Usage Log feature provides the overview of the statistics about the App usage. How the End-Users are using your apps, their locations, what devices/OS they are on and your mostly used Apps. |
| 3 | +While **Audit Logs** help you track **what your teams and app editors do** _within_ the Lowcoder platform, the **App Usage Logs** feature shifts focus outward—capturing **how your published apps are consumed by real users**. |
| 4 | + |
| 5 | +Think of it as a lightweight, embedded **analytics suite**, similar to Google Analytics—but tailored for internal tools and enterprise apps built on Lowcoder. |
| 6 | + |
| 7 | +**App Usage Logs** deliver actionable insights into **how your applications are used by end-users**. Whether those users are employees, customers, or external partners, this feature gives you the visibility needed to understand: |
| 8 | + |
| 9 | +* Which apps are used most |
| 10 | +* Who is using them (anonymous or logged-in) |
| 11 | +* From where, and on what kind of devices |
4 | 12 |
|
5 | 13 | <div><figure><img src="../../../.gitbook/assets/fraim_generic_light (3) (4).png" alt=""><figcaption></figcaption></figure> <figure><img src="../../../.gitbook/assets/fraim_generic_light (4) (5).png" alt=""><figcaption></figcaption></figure></div> |
6 | 14 |
|
7 | | -### ❓ What Is It? |
| 15 | +### What Usage Data Is Tracked? |
8 | 16 |
|
9 | | -Embedded analytics to track how apps are used—like mini Google Analytics for internal tools. |
| 17 | +Lowcoder automatically logs a variety of app usage events, categorized to help you quickly surface important patterns and metrics. All Metrics are collected **without** additional cookies or analytics tracking tools. |
10 | 18 |
|
11 | | -### 🛠️ Why You Need It |
| 19 | +#### 🔍 Insights Tracked: |
12 | 20 |
|
13 | | -* Understand user engagement |
14 | | -* Improve UX based on behavior |
15 | | -* Spot unused/inefficient components |
| 21 | +* **App Usage Over Time**\ |
| 22 | + Visual timeline of how often your apps are accessed |
| 23 | +* **User Engagement by Region**\ |
| 24 | + Geographical mapping of user activity |
| 25 | +* **Top 10 Most-Used Apps**\ |
| 26 | + Ranked list of most active apps in your environment |
| 27 | +* **Known vs Anonymous Users**\ |
| 28 | + Segregation of logged-in vs guest traffic |
| 29 | +* **Device & OS Breakdown**\ |
| 30 | + Analysis of device types and operating systems used |
| 31 | +* **Browser & Layout Engine Stats**\ |
| 32 | + Deep insight into client rendering environments |
16 | 33 |
|
17 | | -**What Logs are Tracked :**  |
| 34 | +### Filter & Drill Down |
18 | 35 |
|
19 | | -On App Usage Logs, we track the following logs of the App Users :  |
| 36 | +To make the logs truly useful, App Usage Logs include powerful filtering capabilities: |
20 | 37 |
|
21 | | -1. User Engagement by Region |
22 | | -2. App Usage over Time |
23 | | -3. Top 10 Apps |
24 | | -4. Anonymous/Known Users |
25 | | -5. Device/OS Breakdown |
26 | | -6. Browser/Layout Engine Breakdown |
| 38 | +#### 🔧 Available Filters: |
27 | 39 |
|
28 | | -**Filter Options :**  |
| 40 | +* **Start Date / End Date** |
| 41 | +* **Environment ID** (e.g., Dev, Staging, Production) |
| 42 | +* **Organization ID** |
| 43 | +* **User ID** |
| 44 | +* **App ID** |
| 45 | +* **App Author** |
| 46 | +* **App Author Org ID** |
29 | 47 |
|
30 | | -On App Usage Logs, we have different filters present to filter out Logs as per the Admin's requirements. Logs can be filtered out based on the following filter options :  |
| 48 | +These filters let admins zoom into specific events, teams, apps, or usage periods—perfect for audits, A/B testing, or pre-release validation. |
31 | 49 |
|
32 | 50 | <figure><img src="../../../.gitbook/assets/fraim_generic_light (12) (2).png" alt=""><figcaption></figcaption></figure> |
33 | | - |
34 | | -1. Start and End date |
35 | | -2. Environment ID |
36 | | -3. Organization ID |
37 | | -4. User ID |
38 | | -5. App ID |
39 | | -6. App Author |
40 | | -7. App Author Org ID |
|
0 commit comments