mixpanel · Copilot · Aug 18, 2026 · Aug 18, 2026 · Aug 18, 2026 · Aug 20, 2026
@@ -1,5 +1,6 @@
 ---
-title: mParticle
+title: "mParticle: Export Mixpanel Cohorts to mParticle Audiences"
+sidebarTitle: "mParticle"
 ---
 
 ## Overview

@@ -1,5 +1,6 @@
 ---
-title: Segment
+title: "Segment: Export Mixpanel Cohorts to Segment"
+sidebarTitle: "Segment"
 ---
 
 ## Overview

@@ -1,5 +1,6 @@
 ---
-title: Google Cloud Storage
+title: "Google Cloud Storage: Export Mixpanel Data to GCS"
+sidebarTitle: "Google Cloud Storage"
 ---
 
 Mixpanel supports exporting events and people data directly to Google Cloud Storage (GCS) via [Json Pipelines](/docs/data-pipelines).

@@ -1,6 +1,6 @@
 ---
 sidebarTitle: Integrations
-title: Data Pipeline Integrations
+title: "Data Pipeline Integrations (Legacy)"
 ---
 
 <Note>

@@ -1,5 +1,5 @@
 ---
-title: Features
+title: "Mixpanel Features"
 ---
 
 <CardGroup cols={3}>

@@ -1,5 +1,6 @@
 ---
-title: Autocapture
+title: "Autocapture Quickstart"
+sidebarTitle: "Autocapture"
 ---
 
 import { dataItems } from "/snippets/utils/constants.mdx";

@@ -1,5 +1,6 @@
 ---
-title: Track Events
+title: "Track Events Quickstart"
+sidebarTitle: "Track Events"
 ---
 
 import { ExtendedButton } from "/snippets/ExtendedButton/ExtendedButton.jsx";

@@ -1,6 +1,6 @@
 ---
 sidebarTitle: Funnels
-title: "Funnels"
+title: "Funnels Report"
 description: "Measure conversions through a series of events"
 ---
 

@@ -1,5 +1,5 @@
 ---
-title: "Funnels"
+title: "Funnels Overview"
 description: "Measure conversions through a series of events"
 sidebarTitle: Overview
 ---

@@ -1,5 +1,6 @@
 ---
-title: Autocapture
+title: "Autocapture: Automatically Track Frontend Events"
+sidebarTitle: "Autocapture"
 ---
 
 import { dataItems } from "/snippets/utils/constants.mdx";

@@ -1,5 +1,6 @@
 ---
-title: Google Cloud Storage
+title: "Google Cloud Storage: Ingest Events into Mixpanel"
+sidebarTitle: "Google Cloud Storage"
 ---
 
 This guide demonstrates how to set up a serverless ingest pipeline from a Google Cloud Storage bucket into Mixpanel. Once this is set up, you can simply upload files containing events into the designated GCS bucket and the events will be ingested into Mixpanel, both one-time and on a recurring basis. Setup should take ~10 minutes.

@@ -1,5 +1,6 @@
 ---
-title: mParticle
+title: "mParticle: Send Event Data to Mixpanel"
+sidebarTitle: "mParticle"
 ---
 
 ## Overview

@@ -1,5 +1,6 @@
 ---
-title: Segment
+title: "Segment: Send Event Data to Mixpanel"
+sidebarTitle: "Segment"
 ---
 
 ## Overview

@@ -1,5 +1,6 @@
 ---
-title: Features
+title: "Features Guide"
+sidebarTitle: "Features"
 ---
 
 ## AI

@@ -1,5 +1,5 @@
 ---
-title: "Mixpanel Headless"
+title: "Mixpanel Headless: Automate Analysis with the Python SDK"
 description: "Programmatic access to your analytics"
 sidebarTitle: Use Mixpanel Headless
 ---

@@ -1,5 +1,6 @@
 ---
-title: Authentication
+title: "Data Pipelines API Authentication"
+sidebarTitle: "Authentication"
 ---
 
 ## Service Account

@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Feature Flags API Overview"
+sidebarTitle: "Overview"
 ---
 
 Mixpanel's Feature Flagging API's provides an interface for assigning your users to variants for feature flags defined within Mixpanel projects.
@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Feature Flags Management API Overview"
+sidebarTitle: "Overview"
 ---
 
 Use the Feature Flags Management API to create, update, delete, and manage feature flags. Requires Service Account authentication.
@@ -1,6 +1,6 @@
 ---
 openapi: /openapi/query.openapi.yaml GET /funnels
-title: Query Saved Report
+title: "Funnels Query API (Maintenance Mode)"
 ---
 
 > ❗️The Funnels Query API is in maintenance mode. We recommend discontinuing new use of this endpoint. To get funnel data, build a [Funnels report](https://docs.mixpanel.com/docs/reports/funnels) in-app and query it programmatically with the [Insights Query API](https://developer.mixpanel.com/reference/insights-query). For raw event data, see [export methods](https://docs.mixpanel.com/docs/export-methods). If you need help choosing the best method, reach out to [support](https://mixpanel.com/get-support).
@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "GDPR & CCPA API Overview"
+sidebarTitle: "Overview"
 ---
 
 ## GDPR and CCPA API (v3)

@@ -1,5 +1,6 @@
 ---
-title: Authentication
+title: "Ingestion API Authentication"
+sidebarTitle: "Authentication"
 ---
 
 Most of our Ingestion API calls such as [Import Events](/reference/import-events), [Track Events](/reference/track-event), [User Profiles](/reference/profile-set), and [Group Profiles](/reference/group-set-property) only require a [Project Token](/reference/project-token). Because these APIs are often called from our client-side SDKs, we do not want to expose credentials, but we do need to know which project to send data to so we use the Project Token for that purpose. However, a few of the more powerful APIs such as [Lookup Tables](/reference/lookup-tables) **do require authentication**. For these, it's recommended to use a [Service Account](/reference/service-accounts). We also have legacy support for [Project Secret](/reference/project-secret) but suggest any new integrations use a Service Account.
@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Ingestion API Overview"
+sidebarTitle: "Overview"
 ---
 
 Mixpanel's Ingestion APIs allow you to send event or profile data to Mixpanel, which can be analyzed in our reporting interface.

@@ -1,4 +1,4 @@
 ---
 openapi: /openapi/query.openapi.yaml GET /insights
-title: Query Saved Report
+title: "Insights Query API"
 ---
@@ -1,5 +1,6 @@
 ---
-title: Authentication
+title: "Lexicon Schemas API Authentication"
+sidebarTitle: "Authentication"
 ---
 
 ## Service Account

@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Lexicon Schemas API Overview"
+sidebarTitle: "Overview"
 ---
 
 Sync your internal data dictionary or tracking plan with Mixpanel using Schemas. A Schema is used to describe the data you are sending to Mixpanel and represents an individual entry into your data dictionary. Schemas that you upload will be used to populate Lexicon and provide additional context for your data across the query UI. A Schema represents a single entity (usually an event) and is defined with json-schema.

@@ -1,5 +1,6 @@
 ---
-title: Limits
+title: "Group Profiles API Limits"
+sidebarTitle: "Limits"
 ---
 
 The Groups Profile API imposes limits on the total number profile updates that can be sent per request to **2000** as well as limits each individual update in the request to a maximum of **1 MB**. If you are running up against these limits, we suggest breaking your request into smaller batches. Usually, these limits are only hit if you are attempting to do a bulk create/update.
@@ -1,5 +1,6 @@
 ---
-title: Limits
+title: "Lexicon Schemas API Limits"
+sidebarTitle: "Limits"
 ---
 
 The Schemas API has the following limits:

@@ -1,5 +1,5 @@
 ---
-title: Lookup Tables
+title: "Lookup Tables API"
 ---
 
 Lookup Tables are mutable tables that describe non-user entities like accounts, product SKUs, or geographies. These tables can be used to enrich events at query-time. In star schema terms: events are like facts and Lookup Tables are like dimensions.

@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Annotations API Overview"
+sidebarTitle: "Overview"
 ---
 
 The Annotations API lets you manage your annotations programmatically. Annotations are text descriptions tied to a time that will show up in reports such as Insights to let users know something meaningful occurred at that time. You can use this API to get a list of your project's annotations, edit them, create them or delete them.

@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Data Pipelines API Overview (Deprecated)"
+sidebarTitle: "Overview"
 ---
 
 <Note>

@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Mixpanel API Overview"
+sidebarTitle: "Overview"
 ---
 
 Mixpanel supports API endpoints that can query, export, and import data as well as manipulate Mixpanel metadata (such as data definitions).

@@ -1,5 +1,6 @@
 ---
-title: Authentication
+title: "Query API Authentication"
+sidebarTitle: "Authentication"
 ---
 
 ## Service Account

@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Query API Overview"
+sidebarTitle: "Overview"
 ---
 
 The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.

@@ -1,5 +1,6 @@
 ---
-title: Authentication
+title: "Raw Data Export API Authentication"
+sidebarTitle: "Authentication"
 ---
 
 ## Service Account

@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Raw Data Export API Overview"
+sidebarTitle: "Overview"
 ---
 
 The Mixpanel Export Data APIs allow you to export your raw data either manually or through a pipeline.

@@ -1,5 +1,6 @@
 ---
-title: Authentication
+title: "Service Accounts API Authentication"
+sidebarTitle: "Authentication"
 ---
 
 ## Service Account

@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Service Accounts API Overview"
+sidebarTitle: "Overview"
 ---
 
 The Service Accounts API lets you manage your service accounts programmatically. You can get a list of your organizations service accounts, see when they were last used, see when they expire, create new service accounts, delete service accounts, and add/remove service accounts to/from projects. This API is useful for automated key management and rotation.

@@ -1,6 +1,7 @@
 ---
 openapi: /openapi/ingestion.openapi.yaml POST /track
-title: Track Events
+title: "Track Events API (/track)"
+sidebarTitle: "Track Events"
 ---
 
 Track events to Mixpanel from client devices. We recommend using one of our client-side SDKs instead of using /track directly, as our SDKs provide queueing, retrying, batching, and more.

@@ -1,5 +1,6 @@
 ---
-title: Limits
+title: "User Profile API Limits"
+sidebarTitle: "Limits"
 ---
 
 The User Profile API imposes limits on the total number profile updates that can be sent per request to **2000** as well as limit each individual update in the request to a maximum of **1 MB**. If you are running up against these limits, we suggest breaking your request into smaller batches. Usually these limits are only hit if you are attempting to do a bulk create/update.
@@ -1,5 +1,6 @@
 ---
-title: Authentication
+title: "Warehouse Connectors API Authentication"
+sidebarTitle: "Authentication"
 ---
 
 A [service account](/reference/service-accounts) is necessary to authenticate Warehouse Connectors API requests. Once you have created a service account and obtained your user name and secret, you can make a request to trigger a warehouse import.

@@ -1,5 +1,6 @@
 ---
-title: Overview
+title: "Warehouse Connectors API Overview"
+sidebarTitle: "Overview"
 ---
 
 Warehouse Connectors allow you to connect a warehouse of your choice to import events, users, groups, and lookup tables.