Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion integrations/analytics/mixpanel.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,20 @@
```json Analytics options in docs.json
"integrations": {
"mixpanel": {
"projectToken": "YOUR_MIXPANEL_PROJECT_TOKEN"
"projectToken": "YOUR_MIXPANEL_PROJECT_TOKEN",
"region": "eu"
}
}
```

Replace `YOUR_MIXPANEL_PROJECT_TOKEN` with your Mixpanel project token. You can find this in your [Mixpanel project settings](https://mixpanel.com/settings/project).

## Data residency

Use the optional `region` property to send analytics to Mixpanel's regional servers for data residency compliance. Accepted values are `us` (default), `eu`, and `in`. If you omit `region`, analytics are sent to Mixpanel's US servers.

Check warning on line 23 in integrations/analytics/mixpanel.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

integrations/analytics/mixpanel.mdx#L23

In general, use active voice instead of passive voice ('are sent').

Set `region` to match the data residency you configured for your Mixpanel project. A mismatch between this value and your project's region prevents events from being recorded.

Check warning on line 25 in integrations/analytics/mixpanel.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

integrations/analytics/mixpanel.mdx#L25

In general, use active voice instead of passive voice ('being recorded').

## Tracked events

Mintlify automatically tracks the following user interactions:
Expand Down
Loading