Solved on the forum

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.

Documented from current sourcesBeginnerReviewed Aug 25, 2026
THE 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.

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.

Completeness85%
Index decisionIndex now
Evidence basisAccepted January 2026 forum solution corroborated by current Screens, Actions, Database, and Update Logged In User documentation; no hands-on reproduction
WHAT YOU’LL HAVE 🎯

The intended outcome

Each tracked user record contains an approximate timestamp for the most recent important screen the user entered.

BEFORE YOU START 🧰

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
BUILD IT 🛠️

Step by step

  1. 01

    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.

  2. 02

    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.

  3. 03

    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.

  4. 04

    Save Current Time

    Set Logged-in User > Last Active to Current Time. Repeat the same action on each selected logged-in screen.

  5. 05

    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.

WHY IT WORKS 🧠

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.

COLLECTIONS AND RELATIONSHIPS 🗃️

Data model

CollectionImportant propertiesRelationships
UsersLast Active Date/Time plus the standard user fieldsNo additional relationship is required; each logged-in user updates their own record
EVIDENCE CONTEXT 🔎

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.
IF IT DOESN’T WORK 🧯

Common failure modes

Last Active stays empty

Confirm the screen is reached after login, the action updates Logged-in User, and the Last Active property is included in that Update action.

The timestamp does not change on a tracked screen

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.

The timestamp updates too often

Remove the action from minor screens and keep it on navigation points that represent meaningful activity. Screen actions run each time the screen loads.

A logged-out visitor causes the action to fail

Use the update only on authenticated screens where Logged-in User exists. Do not attach it to Welcome, Signup, or Login screens.

BEFORE YOU MOVE ON ✅

Testing checklist

0 of 8 checked on this device

BOUNDARIES 🚧

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.
BUILDER REPORTS 🗣️

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
VERSION NOTES 📝

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.

VERSION HISTORY 🕰️

Changelog

  1. Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.

SPOT SOMETHING FUNNY? 🕵️

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.

Report a problem
MONTHLY APP MANAGEMENT · BY REHOST

Rehost becomes the monthly team behind your app. Fixes, releases, integrations, and ongoing changes have an owner.

See monthly management
FixesHandled
ReleasesHandled
Next changesHandled
YOUR PROBLEM IS DIFFERENT? 🤔

Bring us the messy version.

Describe what you expected, what happened instead, and what you already tried.

Ask Adalocado 💬