Skip to content

Commit 9d13868

Browse files
Update autocapture.mdx (#2133)
mp-track was only a theoretical prefix when developing Autocapture. Confirmed by Ted in this thread that this is not accurate. https://mixpanel.slack.com/archives/C07RFLTQZ0D/p1759262296336549 Co-authored-by: myronkaifung <[email protected]>
1 parent 9b68188 commit 9d13868

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

pages/docs/tracking-methods/autocapture.mdx

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,6 @@ Autocapture's default settings also include the following privacy and security c
7676
- Sensitive elements — such as end user text inputs, selects, and textarea elements, are default-excluded from tracking. [You can view our default configurations and options here](https://docs.mixpanel.com/docs/tracking-methods/sdks/javascript).
7777
- By default, Autocapture will not collect sensitive input fields like passwords or form fields — it will only capture a limited set of HTML attributes like class, name, aria-label, role, title, and type attribute values. No content populated by an end user will be collected.
7878
- By default, Autocapture will not capture the text that your website or app displays (`textContent` and its children).
79-
- The exception to these attribute collection rules is when an element has an explicit attribute added with the prefix “mp-track-”. This allows data in these attributes to be intentionally passed back to Mixpanel.
8079
- Mixpanel also provides flexibility to define the classes pages of your website for which you configure Autocapture by using and `block_selectors` and `block_url_regexes`.
8180

8281
To change these default settings, you can customize what is collected through your [SDK configuration](https://docs.mixpanel.com/docs/tracking-methods/sdks/javascript).

0 commit comments

Comments
 (0)