How do you track a user's approximate last active time in Adalo?
Update a User Date/Time property from selected screen actions to record the last screen the logged-in user entered.
Short answer
Add a Last Active Date/Time property to Users, then add a screen action on each important logged-in screen that updates Logged-in User > Last Active to Current Time. Treat the value as the user's latest tracked screen entry, not an exact logout, swipe, tab-close, or idle timestamp.
The intended outcome
Each tracked user record contains an approximate timestamp for the most recent important screen the user entered.
Use screen entry as a practical activity signal. A screen action updates the logged-in user's Last Active Date/Time to Current Time whenever the user reaches a selected authenticated screen. The value is intentionally approximate. It tells you which tracked entry happened most recently, but it cannot detect an exact tab close, app background event, swipe, or idle timeout. Track meaningful screens, protect the timestamp as user activity data, and label the result accurately wherever it appears.
Requirements
- A Last Active Date/Time property in the Users collection
- Screens that users reach only after logging in
- Permission to update the Logged-in User record
- A clear retention and visibility policy for activity timestamps
Step by step
Step 1: Add the activity field
Open the Users collection and add a Date/Time property named Last Active. Do not use a Text property because the saved value should remain sortable and date-aware.
Step 2: Choose meaningful screens
Track screens that represent real activity, such as Home, Dashboard, Messages, or a main work screen. Avoid adding the write to every minor modal unless that precision is worth the extra database updates.
Step 3: Add the screen action
Select the screen title, open its Actions section, add an Update action, and choose Logged-in User as the record to update.
Step 4: Save Current Time
Set Logged-in User > Last Active to Current Time. Repeat the same action on each selected logged-in screen.
Step 5: Display and protect the value
Show Last Active as a relative or Date/Time value where needed, and restrict who can view or edit the User property through collection permissions.
The underlying logic
Adalo screen actions run automatically when a user lands on a screen, so each tracked screen entry overwrites the previous Last Active timestamp.
The newest saved timestamp identifies the latest tracked screen entry. It does not prove that the app remained open, that the user interacted after landing, or when the browser tab closed.
Tracking only meaningful screens reduces unnecessary writes while still providing a useful coarse activity signal.
Data model
| Collection | Important properties | Relationships |
|---|---|---|
| Users | Last Active Date/Time plus the standard user fields | No additional relationship is required; each logged-in user updates their own record |
What still needs checking?
- This is a forum-native Answer with no original Adalocado video. The accepted workflow was confirmed by the source author in January 2026, and current official documentation was reviewed in August 2026.
Common failure modes
Confirm the screen is reached after login, the action updates Logged-in User, and the Last Active property is included in that Update action.
Open the screen's Actions section and verify the mapped value is Current Time. Then publish the latest app changes and test with a fresh screen entry.
Remove the action from minor screens and keep it on navigation points that represent meaningful activity. Screen actions run each time the screen loads.
Use the update only on authenticated screens where Logged-in User exists. Do not attach it to Welcome, Signup, or Login screens.
Testing checklist
0 of 8 checked on this device
Current limitations
- This records screen entry, not swipe activity, backgrounding, tab closure, logout, or true inactivity. Adalo does not provide a reliable close-event timestamp through this forum workflow.
- Screen actions run every time a screen loads. Tracking too many screens increases database writes and can make the value noisier than the app needs.
- A Last Active field is activity data. Limit who can view or edit it and disclose its use when appropriate.
- Adalocado did not reproduce the workflow in a current builder project.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts, not endorsements or independently reproduced results.
Lastactivity Time, community source 1
The accepted reply recommends a Last Active Date/Time User property updated to Current Time from screen actions.
Boundary: The reply explicitly describes the result as the last screen entered, not a reliable signal for when the user stopped using the app.
Victor · January 2026
Lastactivity Time, community source 2
The source author confirmed that the screen-action method worked in the app.
Boundary: The confirmation does not measure write volume, background behavior, or precision across native and web apps.
bhaveshsood · January 2026
Sources and status
This page was last reviewed on Aug 25, 2026. Its current status is Documented from current sources.
Verification owner: Adalocado daily AI publisher after full-topic and current-documentation review. Next review: Oct 25, 2026.
Changelog
Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.
Automatically organized and maintained by the Adalocado editorial team under the editorial and verification policy.
Report this answer.
Automated Answers still pass evidence and publication checks, but they can be wrong, outdated, unclear, or missing an important boundary. Send the exact correction and the editor will check the live page.
Did this solve your problem?
One-click check
We’ll handle the tech. You can exhale.
Bugs fixed. Updates shipped. Publishing handled.
$97/mo for your first 3 months.
Cancel anytime. That’s about 90% off the usual cost. 🤯
- Bug fixes and troubleshooting
- App updates and integrations
- Publishing and store releases
Bring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
