Usage counts are off unless you turn them on. When they're on, Lanyard sends a small batch about once a day to api.lanyard.mobile. This page lists everything a batch can contain. Every property is a choice from a fixed list, a yes/no, or a range: never free text, names, notes or anything you captured. Our server refuses a batch with any key or value that isn't on its list.
On every batch
A random install ID that changes every day, the app version, the iOS major version, your iPhone family (for example "iPhone 16 Pro", never the exact model, a serial number or any hardware identifier), your plan (trial, pass or pro) and the date (no time).
Events
| Event | What it counts |
|---|---|
onboarding_done | Onboarding finished |
event_created | An event workspace was created (manual or from calendar), whether it is the install's first, second or a later event, and months since the previous one, bucketed |
first_capture | First capture in an install, by type |
first_review_done | First evening review completed |
review_done | An evening review was completed (every time, not only the first), on the event's first day or a later one |
report_generated | A report was generated, by lens and length |
report_delivered | A report was delivered, by destination (Send to an AI assistant counts as aiAssistant, apart from other shares) and time since the event ended, bucketed |
capture_created | A capture was made, by type and duration bucket |
capture_entry | Which entry point started a capture |
report_rerendered | A report was re-rendered through another lens |
report_edited | Share of a report the user edited, bucketed |
section_removed | Sections removed in preview, bucketed count |
followups_exported | Follow-ups exported to Reminders: bucketed count, how many were for A-priority people (bucketed), and time since the event ended, bucketed |
event_day_summary | Once per finished event day: first day or later, captures that day (bucketed), and whether that day was reviewed |
destination_connected | A destination was connected, by mode |
destination_disconnected | A destination was disconnected |
delivery_result | Outcome of a send and its error class |
report_rated | In-app report rating, 1–5 |
summary_vote | Thumbs up or down on a summary, by capture type |
merge_suggestion | A people-merge suggestion was accepted or rejected |
lead_score_overridden | The user overrode a lead score |
paywall_viewed | Paywall shown, by trigger |
purchase_started | A purchase was started, by product |
job_completed | A pipeline job finished, by type and duration bucket |
model_load_failed | A model failed to load, by kind |
job_failed | A processing job gave up after its retries, by type |
app_exits | From Apple's MetricKit daily report: how many times the app ended in a day, by reason (normal, crash type, killed by the system for memory, CPU, watchdog or a held file lock), on screen or in the background, bucketed. No crash logs or call stacks |
hang_time | From MetricKit: how many times the app froze in a day, by how long it froze, bucketed |
launch_time | From MetricKit: how many launches or resumes in a day took how long, bucketed (cold, prewarmed or resume) |
report_footer_kept | Whether the report footer was kept |
Settings › See what we send in the app shows the exact batch that would be sent next.