01 · Records and state owned
Attribution and performance datasets spanning apps, campaigns, channels, geographies, cohorts, conversions, cost, ROAS and related privacy-governed marketing signals.
AppsFlyer
AppsFlyer
A leading mobile measurement partner with APIs, raw data, reports, audiences, fraud signals, and event streams that connect acquisition activity to downstream customer outcomes.
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
Query live attribution and performance data for reporting, anomaly detection, spend monitoring, cohort analysis and multi-system marketing workflows.
03 · Actions and write paths
The reviewed public material supports analysis and monitoring more clearly than direct mutation. Treat AppsFlyer MCP as read/analysis-first until the current account-specific tool catalog confirms each audience, OneLink or other write action.
04 · Authentication and permissions
Use the authorized AppsFlyer account and token/connection flow; app ownership, account roles, product entitlements, privacy controls, retention and residency govern access.
05 · Monitoring, approval, and recovery
Show attribution definitions, freshness, modeled-versus-observed signals, account/app scope and provenance; place any downstream spend or activation change in the target system behind approval.
06 · Gaps and implementation limits
Public product material does not enumerate every tool. Plan entitlement, data residency, retention, app scope and any audience or OneLink mutation must be verified in the live account.
Agent access
MCP and adjacent posture
Verified first-party provider MCPAppsFlyer-hosted MCP over marketing-measurement APIsCurrent service; launched in beta
Role: provider
Read scope: Live attribution and campaign-performance data, including channel, campaign, geography, cohort, conversion, cost and ROAS context available to the authorized AppsFlyer account.
Write scope: Official materials emphasize analysis, monitoring, reporting and workflow automation; audience or OneLink-related actions may exist, but the exact mutation catalog and plan entitlement must be checked before enabling writes.
Authentication: AppsFlyer MCP connection using the customer account and AppsFlyer token or supported connection flow.
Approval boundary: Consequential writes should require explicit review; use vendor confirmation controls where available.
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 access3
UI extensibility4
Portability3
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that AppsFlyer ships these experiences.
Single-platform patterns
- Mobile acquisition and attribution diagnostic room
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- AppsFlyer + warehouse or semantic layer: executive insight brief
- AppsFlyer + 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.
4 recorded sources
MCP / agent-role validationRepresentative source
https://www.appsflyer.com/products/agentic-ai/mcp/ ↗AppsFlyer materials confirm an official MCP for unified marketing data, attribution, analytics, audiences, and OneLink-related workflows.
- Publisher updated
- Jun 15, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP and platform-access review
HomepageSource inventory
https://www.appsflyer.com/ ↗Product overview.
- Publisher updated
- Jul 8, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://dev.appsflyer.com/hc/docs ↗First-party developer guidance.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
API referenceSource inventory
https://dev.appsflyer.com/hc/reference/overview ↗First-party API reference.
- 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.