OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Raw Event Export streams JSONL for selected event dates, with event-name and where filters. Validate the complete response and scope before treating the extraction as finished.
Mixpanel raw event export ↗
Date/event/where filters and JSONL response · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Raw Event Export streams JSONL for selected event dates, with event-name and where filters. Validate the complete response and scope before treating the extraction as finished.
Mixpanel raw event export ↗
Date/event/where filters and JSONL response · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Date ranges, event lists and expression filters narrow exported events. This route does not expose joined SQL across the live product database.
Mixpanel raw event export ↗
Date/event/where filters and JSONL response · Checked 2026-10-16
Access cost barrier -
-
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Raw export and service-account technical documentation do not establish the complete minimum-plan and fixed-access conditions; managed warehouse pipelines are a separate purchasable route.
Mixpanel API rate limits ↗
Raw Data Export versus Query and Ingestion quotas · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Mixpanel recommends service accounts for authenticated APIs; roles and project membership constrain access. Ingestion can use different project-token credentials and regional hosts must match the project.
Mixpanel authentication methods ↗
Service accounts, project membership and ingestion credentials · Checked 2026-10-16
Downstream permission -
-
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
Mixpanel authentication methods ↗
Service accounts, project membership and ingestion credentials · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Import Events ingests structured events subject to project authorization, validation and insert-ID deduplication rules. It does not establish general editing of every historical event.
Mixpanel Import Events operation ↗
Event ingestion, validation and deduplication · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Customers can build or choose applications using the documented API and the disclosed authorization route.
Mixpanel authentication methods ↗
Service accounts, project membership and ingestion credentials · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Repeat event-date extraction with an explicit overlap policy for late ingestion. Event timestamps and processing timestamps are different; no general tombstone or retained cursor feed is established.
Mixpanel raw export date windows ↗
from_date, to_date and event timestamps · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Raw Data Export allows 60 queries/hour, three/second and up to 100 concurrent queries. Query API and ingestion limits are separate and cannot be substituted for this export budget.
Mixpanel API rate limits ↗
Raw Data Export versus Query and Ingestion quotas · Checked 2026-10-16
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Date-window event exports can be reconciled where retained. Native update/deletion identities and completeness for events outside the reread window remain unresolved.
Mixpanel raw export date windows ↗
from_date, to_date and event timestamps · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Retained date windows can be re-exported, with deduplication and late-arrival handling. This is a fresh extraction, not historical ordered replay from a durable provider checkpoint.
Mixpanel raw export date windows ↗
from_date, to_date and event timestamps · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Exported JSONL provides portable retained event records. Profiles, reports, cohorts, governance rules, deleted records and complete project reconstruction require separate inventories.
Mixpanel raw JSONL download ↗
Download data response and scope · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
Mixpanel raw JSONL download ↗
Download data response and scope · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Exported JSONL provides portable retained event records. Profiles, reports, cohorts, governance rules, deleted records and complete project reconstruction require separate inventories.
Mixpanel raw JSONL download ↗
Download data response and scope · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Mixpanel authentication methods ↗
Service accounts, project membership and ingestion credentials · Checked 2026-10-16
Rights to custom logic -
-
Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
Mixpanel authentication methods ↗
Service accounts, project membership and ingestion credentials · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Mixpanel recommends service accounts for authenticated APIs; roles and project membership constrain access. Ingestion can use different project-token credentials and regional hosts must match the project.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Raw Event Export streams JSONL for selected event dates, with event-name and where filters. Validate the complete response and scope before treating the extraction as finished. Date ranges, event lists and expression filters narrow exported events. This route does not expose joined SQL across the live product database.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | HTTP Basic | Customer | No | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Raw export and service-account technical documentation do not establish the complete minimum-plan and fixed-access conditions; managed warehouse pipelines are a separate purchasable route.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Import Events ingests structured events subject to project authorization, validation and insert-ID deduplication rules. It does not establish general editing of every historical event.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Repeat event-date extraction with an explicit overlap policy for late ingestion. Event timestamps and processing timestamps are different; no general tombstone or retained cursor feed is established. Raw Data Export allows 60 queries/hour, three/second and up to 100 concurrent queries. Query API and ingestion limits are separate and cannot be substituted for this export budget.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Date-window event exports can be reconciled where retained. Native update/deletion identities and completeness for events outside the reread window remain unresolved. | Mixpanel raw export date windows ↗from_date, to_date and event timestampsChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Retained date windows can be re-exported, with deduplication and late-arrival handling. This is a fresh extraction, not historical ordered replay from a durable provider checkpoint. | Mixpanel raw export date windows ↗from_date, to_date and event timestampsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Exported JSONL provides portable retained event records. Profiles, reports, cohorts, governance rules, deleted records and complete project reconstruction require separate inventories.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Raw Event Export streams JSONL for selected event dates, with event-name and where filters. Validate the complete response and scope before treating the extraction as finished. | Mixpanel raw event export ↗Date/event/where filters and JSONL responseChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Raw Event Export streams JSONL for selected event dates, with event-name and where filters. Validate the complete response and scope before treating the extraction as finished. | Mixpanel raw event export ↗Date/event/where filters and JSONL responseChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Date ranges, event lists and expression filters narrow exported events. This route does not expose joined SQL across the live product database. | Mixpanel raw event export ↗Date/event/where filters and JSONL responseChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Mixpanel recommends service accounts for authenticated APIs; roles and project membership constrain access. Ingestion can use different project-token credentials and regional hosts must match the project. | Mixpanel authentication methods ↗Service accounts, project membership and ingestion credentialsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Raw export and service-account technical documentation do not establish the complete minimum-plan and fixed-access conditions; managed warehouse pipelines are a separate purchasable route. | Mixpanel API rate limits ↗Raw Data Export versus Query and Ingestion quotasChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | Mixpanel authentication methods ↗Service accounts, project membership and ingestion credentialsChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Import Events ingests structured events subject to project authorization, validation and insert-ID deduplication rules. It does not establish general editing of every historical event. | Mixpanel Import Events operation ↗Event ingestion, validation and deduplicationChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Customers can build or choose applications using the documented API and the disclosed authorization route. | Mixpanel authentication methods ↗Service accounts, project membership and ingestion credentialsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Repeat event-date extraction with an explicit overlap policy for late ingestion. Event timestamps and processing timestamps are different; no general tombstone or retained cursor feed is established. | Mixpanel raw export date windows ↗from_date, to_date and event timestampsChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Raw Data Export allows 60 queries/hour, three/second and up to 100 concurrent queries. Query API and ingestion limits are separate and cannot be substituted for this export budget. | Mixpanel API rate limits ↗Raw Data Export versus Query and Ingestion quotasChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Exported JSONL provides portable retained event records. Profiles, reports, cohorts, governance rules, deleted records and complete project reconstruction require separate inventories. | Mixpanel raw JSONL download ↗Download data response and scopeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | Mixpanel raw JSONL download ↗Download data response and scopeChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | Mixpanel authentication methods ↗Service accounts, project membership and ingestion credentialsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Mixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Native workflow ownership, reusable export and independent execution rights remain unresolved. | Mixpanel authentication methods ↗Service accounts, project membership and ingestion credentialsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedMixpanel / customer project/service-account raw Event Export API and Import Events; reporting, profiles, warehouse pipelines and full project configuration have separate contracts. Exported JSONL provides portable retained event records. Profiles, reports, cohorts, governance rules, deleted records and complete project reconstruction require separate inventories. | Mixpanel raw JSONL download ↗Download data response and scopeChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Applicable downstream processing and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.