What should you count for a new app feature?
Choose one named action and send it when the result actually occurs. For a reading app, count a completed bookmark save when the app confirms it. A tap can fail and repeated taps can inflate your total. Aptabase adds context such as app version to the event.
Can you tell whether the same person comes back next month?
Aptabase does not use a persistent person identifier. Its documentation describes a short-lived session ID and a daily-rotated hash on the server. Use it for counts by time or app version. Choose a different measurement design if your main question is whether the same person returns next month.
You choose the event details. Keep names, contact details and the text someone writes out of custom properties. A label such as bookmark_saved is enough for a count.
What happens if you reach the monthly event limit?
The hosted Free plan lists 20,000 events a month. Each call to track an event counts once. Aptabase says it pauses analytics until an upgrade or the next month if you exceed the limit, without an overage fee. Decide which counts matter before sending an event for every interaction.
How can you check and keep the counts?
Use the dashboard’s Debug and Release views to check which build sent the events. Verify the selected view before comparing totals. The dashboard supports CSV export for work outside Aptabase.
How many bookmark saves should your paper test count?
Write down three fictional attempts. One saves, one fails and one repeats the tap on the same pending save. Expect a count of one when the app reports a completed save only once.
- Choose the exact momentPut the event beside the completed save, after the app has stored the bookmark.
- Check both viewsMark the expected test count under Debug and leave Release empty.
- Keep the details smallInclude the action name and the app version available from the SDK. Leave book titles and reader information out of the event.