01 · Records and state owned
Apps, trackers and campaigns, attribution and events, cohorts, SKAdNetwork data, ad spend and revenue, callbacks, and report definitions.
Adjust
Adjust
A major mobile measurement platform with APIs and SDKs for attribution, campaign data, events, audiences, fraud prevention, and mobile performance operations.
Analytics, SEO & experimentationSystem of intelligenceExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Retrieve aggregated installs, events, revenue, spend, cohorts, SKAdNetwork, event slugs, and other report-service data.
03 · Actions and write paths
Submit server-to-server events and ad revenue, manage supported callbacks and integrations, and automate reporting workflows.
04 · Authentication and permissions
Adjust API tokens, app tokens, package entitlements, and optional S2S security tokens apply to different surfaces.
05 · Monitoring, approval, and recovery
Preserve attribution windows, source definitions, consent, device-identifier handling, revenue currency, and report lineage.
06 · Gaps and implementation limits
No first-party provider MCP was verified. Many surfaces are report-oriented; packages, retention, quotas, and anti-spoofing requirements vary.
First-party access
Documented surfaces
Agent access
MCP and adjacent posture
No first-party provider MCP verified in this snapshotNo first-party provider MCP foundNo first-party provider verified
Role: none_verified
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Adjust ships these experiences.
Single-platform patterns
- Mobile campaign measurement and anomaly cockpit
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- Adjust + warehouse or semantic layer: executive insight brief
- Adjust + CRM or lifecycle platform + work-management system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
3 recorded sources
APIRepresentative source
https://dev.adjust.com/en/api/ ↗First-party API documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party core-access review
HomepageSource inventory
https://www.adjust.com/ ↗Product overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer portalSource inventory
https://dev.adjust.com/ ↗First-party developer documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.