Stood Flows · visits · objects explorer · new

Who opens what, and which objects are worth their storage

Licences say who may use the CRM. Visits says who actually opens it, on which screens, and whether they write anything once there. The Objects explorer turns the same evidence around: every object the org carries, biggest first, with the people, writes and cost attached.

statusVisits · 1.3.0Visited objects and Objects explorer · built after 1.3.2docsVisits: what people look at DML Analysis and ELF LicensingCapability atlas

Visits: from event logs to a population you can act on

Salesforce event log files record page views, searches, reports and logins. Visits picks the event types by measured coverage per population (users seen ÷ users who logged in), so Classic, Lightning and portal orgs all work without configuration, and prints that coverage on every view. A population the sources cannot see reads unobservable, never "no activity".

Visits · how the evidence is builtSTOOD
Salesforce org event log files · read only URI · LightningPageView VisualforceRequest · Report Search · Login DatabaseSave (writes) coverage measured per type daily Sessionise local · raw files deleted after LOGIN_KEY → SESSION_KEY → 30-min gap screen = page type + object paths, session shape, hour × weekday join to DML drill: did this user write? surface: internal / community sums What is kept no record id · no URL · no IP address users, sessions, screens per population, per period every bar split by what the user did with the write side: business DML DML, no business no DML integration not in the drill deactivated periods kept in ui-history for the trend why it matters for licences A seat that logs in, opens three screens a week and never writes is a reader. Readers are served by BI, not by a CRM seat. Visits is the evidence behind the "read-only consumers" rung of the licence cascade.
Shipped in 1.3.0. Requires View Event Log Files on the connected user; withholding it disables every ELF-based analysis, which is the customer's control.

Object exposure: from screens to objects

Each screen keeps its object. The Users card now offers Visited objects: for every object, views, share of all views, users, sessions, records and screens, with custom/standard and profile filters and a CSV export. One click hands that list to the Objects explorer, where a Visits column joins the storage and write evidence.

Objects explorer · every business object, biggest firstSTOOD
OrgObjectTagRecordsDML opsUsersVisitsAPI callsCost / yrLast created
Guest ExperienceGuest_Interaction_Log__ctelemetry25,912,4401,048,900101,048,900$155,475today
Guest ExperienceOpportunitybackbone4,153,111311,2071,21488,41012,004$24,919today
Guest ExperienceGuest_Event_Analytics__ctelemetry3,206,1180000$19,2372023-02
Guest ExperienceContactbackbone2,744,002190,3381,10261,22040,112$16,464today
Revenue & DistributionRate_Sync_Entry__cmanaged · ratesync1,980,440402,11820402,118$11,883today
Guest ExperienceSpa_Waitlist__ccustom412,00900840$2,4722021-11
Operations HubProperty_Audit_UAT__ccustom38,1180000$2292022-06
Events & CateringBanquet_Order__ccustom9,2063,114416,3020$55today

Illustrative — Meridian Hospitality Group. Cost is a storage heuristic: about 2 KB per record and $125 per 500 MB block per month, roughly $6 per 1,000 records per year; swap in the contract rate. Share, history, feed, log and metadata tables are excluded; managed-package objects are flagged, not dropped.
What to look for

Big, written by one user, visited by none

A telemetry table filled by an integration at one row every three seconds, never opened by a human. Ask who reads it, and where. Usually the answer is a warehouse that already has the data.

What to look for

Millions of records, zero DML, last created years ago

Storage paid for monthly for an object nobody writes or opens. The stale-object verdict (12 months idle by default policy) counts it as a stale-object candidate.

What to look for

Object families

Stay, Stay_Log, Stay_Analytics, Guest_Stay_Event. Near-duplicate names are the trace of successive projects. The explorer sorts by name on demand so the family shows up together.

What this means on Monday. Filter the explorer on "No DML" and "Last created 12+ months". Sum the Cost column. That is the storage line of the ROI model, before anyone has qualified a single object.

Where the numbers come from

Records come from the record-count endpoint and one COUNT per non-empty object when the object-volumes step is enabled (off by default; one SOQL per object). DML and API figures come from the same event logs the licence drill uses. Visits come from the aggregates above. All of it is read-only and stays in the workspace folder on the auditor's machine, shared on the customer's own S3 or GitHub if they choose to.

In the app

Captured from the application itself, built from the current source tree and opened read-only on the Meridian demonstration workspace.

Licensing → Visits, Overview: 17 days, 1,822 users, 174,503 pageviews, every figure split by DML category.
Licensing → Visits, Overview: 17 days, 1,822 users, 174,503 pageviews, every figure split by DML category.
Visited objects, exact: views, share, users, sessions, records and screens per object, with the hand-off to the Objects explorer.
Visited objects, exact: views, share, users, sessions, records and screens per object, with the hand-off to the Objects explorer.
Folder dashboard → Objects explorer: every business object across the five orgs, biggest first, with storage cost and last-created date.
Folder dashboard → Objects explorer: every business object across the five orgs, biggest first, with storage cost and last-created date.