Autocapture is analytics tracking that records taps, screen views and other interface actions automatically once the SDK is installed, while manual tracking records only the events your code names. Autocapture gets you data on day one; manual events give you cleaner funnels. Choose by the question you need answered.
What is autocapture?
Autocapture is a switch in an analytics SDK that collects a predefined set of events without a line of tracking code per event. Mixpanel's autocapture documentation is a good worked example. On mobile, each Mixpanel SDK captures screen views, clicks, dead clicks and rage clicks.
Two of those need a definition:
- Dead click: a click on an interactive element that produces no visible response within a set time. Mixpanel's web default is 0.5 seconds.
- Rage click: repeated clicks on the same spot, because the user expects something to happen and nothing does. Mixpanel's web default is 4 clicks within a second, 30 pixels apart.
Those thresholds are the defaults of the web JavaScript SDK, so treat them as web numbers.
On Mixpanel, click events are off by default and are turned on with an options object at initialization. Autocaptured events start with $mp_ and show an [Auto] prefix, which separates them from events you send yourself. Mixpanel describes autocapture as the best option for getting started quickly.
What is manual event tracking?
Manual tracking means you decide which actions matter and call the SDK at that point in your code, with an event name and properties. If you never call it, nothing is recorded.
ActivationPal works this way. Its SDK records first_open once per install and app_open on each new session by itself. Onboarding, paywall and custom events are sent by your code. ActivationPal does not autocapture taps.
ActivationPal.onboardingStep(2, id: "weekly_schedule", answer: "3_days")
ActivationPal.paywallShown("onboarding")
ActivationPal.track("workout_logged", ["type": "run"])
The funnel and paywall cards in ActivationPal match on the fixed event names, so each onboarding step becomes one row ordered by its index. Every funnel stage counts unique devices from the install cohort, so no stage can exceed 100% of installs. The full list is in the events docs.
Autocapture vs manual tracking at a glance
| Question | Autocapture | Manual events |
|---|
| Setup effort | Turn it on, add a navigation hook for screens | Write a call for each event you want |
| Data on day one | Yes, for the events it captures | Only for the calls already shipped |
| Event volume | High, most of it unused | As low as your event list |
| After a UI change | Names and targets can shift with the interface | Named events stay the same |
| Sensitive data | Depends on defaults and exclusions | You choose every property |
| Funnel steps | You assemble them from raw taps and screens | Each step is an event you defined |
| Best for | Exploring, rage and dead click hunting | Funnels and weekly metrics |
Autocapture trade-offs on mobile
Noise and volume. Every tap is a candidate event, and most taps belong to no funnel. Mixpanel recommends monitoring event volume as you change the configuration and testing autocapture in a sandbox project before rolling it out. You can restrict clicks to chosen elements or turn click capture off and keep the rest. If your plan is priced by events, a noisy capture setting is a cost as well as a clutter problem.
Sensitive data. Mixpanel's defaults exclude text inputs and the text your app displays, and it does not recommend autocapture where highly sensitive data such as PHI is involved. Compliance with privacy law stays the customer's responsibility. With explicit events you choose each property, so nothing is sent that you did not write. ActivationPal sends the events you choose plus device and session context; see privacy and security.
Names tied to the interface. An autocaptured tap is identified by what it was attached to. Rename a button or move a screen and one behaviour can split into two series and the history of the chart stops at the release. A named event such as onboarding_completed stays the same across redesigns. The naming rule here is snake_case, past tense, and a renamed event is a new event, so keep the set small and stable.
Screen views need a hook. Mixpanel's screen views require a one-time hook into your app's navigation. Autocapture on mobile is therefore not zero setup.
When explicit events are better
Pick explicit events when:
- You have a funnel with defined steps, such as onboarding, paywall and purchase. The onboarding funnel is only readable when each step is one named event.
- The team reports the same metrics every week and the definitions must not drift.
- The app handles private information and you want to decide each property.
- You pay by event and want the volume to match the questions you ask.
- You want a shared tracking plan. Write the list first with the free mobile app tracking plan template, then instrument it.
Money events need no tap capture at all. Purchases, trials, renewals and churn arrive on the server side from RevenueCat or Superwall webhooks.
When autocapture is enough
Autocapture fits when you are exploring a product you do not know yet, when much of the surface is web, or when you want rage and dead clicks to point you at broken screens. Mixpanel notes it can coexist with precise tracking, so you can run both.
If tap-level behaviour is what you need, use a tool that autocaptures. ActivationPal's scope is the install, session, onboarding, paywall and purchase funnel.