Included as a mobile measurement control surface whose official APIs separate aggregated reporting, server-to-server measurement ingestion, and template-driven app configuration across attribution, events, revenue, partners, callbacks, fraud controls, and SKAdNetwork settings.
Concrete capability record
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.
Apps and app settings; event definitions and tokens; trackers and partner configurations; attribution windows; callbacks; SDK signatures and secrets; installs, sessions, events, revenue, spend, cohorts, retention, SKAdNetwork metrics, and report dimensions.
Query aggregated reporting data in Parquet, CSV, JSON, or pivot JSON; discover valid filters, metrics, and event slugs; inspect app settings and asynchronous migration status where App Automation is enabled.
Send custom events, sessions, and ad-revenue records through S2S endpoints. On accounts with App Automation enabled, create or update apps from a template, migrate selected configuration sections, manage event definitions and SDK signatures or secrets, and track background jobs. Settings migration updates or creates values but does not delete settings absent from the template.
Report Service and App Automation use a user-profile Adjust API token as a bearer credential; resetting it invalidates the prior token. App Automation additionally requires Admin or Editor permission, account enablement, and a template app. S2S requests use app and event tokens and can be protected by an administrator-created S2S security token scoped to events, sessions, ad revenue, or GDPR operations.
Record the app token, event token or alias, reporting dimensions and metrics, attribution window, currency, timestamp, source IP, and App Automation ticket outcome. Treat S2S security activation as a staged change: it is off by default, should be tested, and Adjust instructs customers to coordinate validation before enabling it.
Report Service is limited to 50 requests per second per source IP with a burst allowance of 100; clients behind one NAT or proxy share that allowance. App Automation is feature-gated and template-based. S2S event submissions older than 58 days are rejected, and S2S security is incompatible with Google Tag Manager event measurement.
First-party access
Agent access
Support: No official MCP server located
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: A customer-built agent adapter would authenticate separately to each Adjust surface: bearer Adjust API token for Report Service or enabled App Automation, and app/event identifiers plus optional scoped S2S security token for measurement ingestion. No provider MCP authentication model is asserted.
Approval boundary: Require confirmation before enabling S2S security, migrating template settings into an existing app, changing attribution or privacy sections, revoking or reactivating SDK secrets, or sending backdated measurement. Show the target apps, migrated sections, and resulting ticket before execution.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Adjust ships them.
Evidence and dates
“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.
First-party API documentation.
Targeted first-party core-access review
First-party developer documentation.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Product overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
