Document mobile Autocapture support (SDK-164) - #243
Open
rahul-mixpanel wants to merge 1 commit into
Open
Conversation
Autocapture is no longer web-only: Android (v8.10.0), iOS (v6.6.0), and React Native (v3.7.0) ship screen view and click autocapture. Update the Availability section to say so and link to each SDK's Autocapture section. Click events are noted as beta and off by default. SDK-164
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
 |
rahul-mixpanel
requested review from
mbocianski and
russell-loube-mixpanel
and removed request for
rssebastian-mp
September 11, 2026 07:46
mbocianski
approved these changes
Sep 11, 2026
russell-loube-mixpanel
requested changes
Sep 11, 2026
|
|
||
| On web, Autocapture is available via Mixpanel’s [JavaScript SDK](/docs/tracking-methods/sdks/javascript). To turn it on, ensure you have the config `{autocapture: true}` set in the SDK. | ||
|
|
||
| Autocapture is also available on mobile via the [Android](/docs/tracking-methods/sdks/android#autocapture) (v8.10.0 or later), [iOS](/docs/tracking-methods/sdks/swift#autocapture) (v6.6.0 or later), and [React Native](/docs/tracking-methods/sdks/react-native#autocapture) (v3.7.0 or later) SDKs. These SDKs capture screen views, clicks, dead clicks, and rage clicks. Click events are in beta and are turned off by default — see each SDK’s Autocapture section to set them up. |
Contributor
There was a problem hiding this comment.
Let's add a note that screen views are supported in Flutter and that clicks/dead clicks/ rage clicks are coming soon.
I think you could just add Flutter in the list, and add note like this:
"These SDKs capture screen views, clicks, dead clicks, and rage clicks (only screen views are currently available for Flutter)"
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Autocapture page still said Autocapture was "available for web only". That is no longer true — Android, iOS, and React Native have all shipped it. This updates the Availability section to say so and links to each SDK's Autocapture section.
Links point at the parent
#autocapturesection on each SDK page, which covers both Screen View & Screen Leave and Click Events. Click events are called out as beta and off by default, matching the per-SDK docs added in #213 and #227.Closes SDK-164.
Not included
Kept the diff to the Availability section. Worth follow-ups:
## Autocapture eventslist plus the Dead Clicks / Rage Clicks sections describe webpage behavior and JS SDK thresholds only. The mobile thresholds happen to match (500 ms dead click; 4 taps / 1000 ms / 44 dp rage click), but the prose says "webpage".docs/quickstart/capture-events/autocapture.mdxis still JS-only.