The ADAPT
Protocol
How ADAPT would connect data sources, manage permissions, and send records to approved tools.
Artist data lives
in separate systems
Ticket sales, streams, purchases, and email signups sit in separate systems. Artists and their teams often need separate exports and manual work to compare them.
ADAPT proposes common data formats and access rules so artists can use records from those sources together.
One connection
A shared data format
The hub and the standard ADAPT is building a neutral hub where platforms can exchange data through one connection. Artists and authorized teams choose where permitted records go. The standard defines formats, permissions, and transfer rules. ADAPT plans to run the hub, not replace the receiving CRM or require permanent storage.
Think DDEX for shared standards, with a Plaid-like connection experience for fan data. This describes the intended approach, not an affiliation or a claim that integrations are live.
The data model Artist, fan, release, event, transaction, and campaign records use shared fields and retain their source identifiers. Tools can use totals and unmatched records without identifying every fan across platforms.
Connect sources
Keep the context
The proposed connectors would use supported APIs to import authorized data from ticketing, commerce, email, streaming, and social accounts. Fields would map to the shared schema without losing their source identifiers.
Access depends on the source Each platform determines which records and aggregates its API exposes and under what terms. ADAPT cannot grant access the source does not provide.
Those records would go to the artist’s chosen CRM, analytics tool, or distributor dashboard.
Authorize The artist or authorized team approves each connection through the source platform. The connector requests only the permissions needed for the selected data.
Sync Import available records and totals. Keep the source and update time with each record.
Normalize Map fields to the shared schema and keep original identifiers. A listener and a follower remain separate unless evidence and permission support a link.
Take it with you Portability is a design goal: export permitted data in documented formats and use it in other tools. Export scope and source restrictions will be defined in the specification.
Why platforms might participate Shared formats could reduce the work required to exchange artist data. The proof of concept should test that with participating platforms.
What the protocol covers
The proposal covers four areas: source data, processing rules, connections to other tools, and access controls. The proof of concept will test how they work together.
DATA
Import permitted source records and aggregates. Keep source identifiers and timestamps alongside fields mapped to the shared schema.
LOGIC
Define how fields are validated and transformed. Document calculations so downstream tools can interpret the results.
ACTION
Send approved data to CRMs, analytics tools, and advertising systems. The proof of concept will determine which connections to build first.
SECURITY
Define access by role, record, and field. Artist permissions must also respect source restrictions and the rights of people in the data.
The objects
These are the proposed record types. Each includes fields, source identifiers, access rules, and links to related records.
SOURCE RECORD
Audience information supplied by an authorized source: identifiers, consent details, and activity where available. Records from different sources can stay separate. Whether ADAPT or a receiving CRM should link identities remains undecided.
THE ARTIST IDENTITY
The person or brand associated with a catalog, accounts, and team. This identity is distinct from legal entities and representatives. Access grants would identify the parties authorized to act, their scope, and the relevant records.
THE WORK
A track, album, video, or other published work. Source identifiers can link it to reported activity and revenue where that data is available.
THE MOMENT
A show, livestream, listening party, or meet-and-greet. Fields can include venue, date, capacity, ticket sales, and permitted attendance records.
THE EXCHANGE
A purchase, ticket sale, tip, or subscription payment. Keep the amount, currency, date, and source transaction identifier where provided.
THE ACTION
An email, advertisement, presale, or other campaign. Store the channel, dates, and results the source provides, with links to permitted audience records.
The relationships
A ticket transaction can link to an event through its source identifier; the event can link to an artist. Each link should keep the evidence behind it.
Linking people is a separate task Treating two records as the same person requires suitable identifiers, permission, and a defined matching method. The white paper will address where that work belongs.
Still to decide We have not decided whether relationships need their own layer in the data model. The diagram groups records around the artist without assuming a single identity for each fan.
Source records, shared fields, and access rules
Source records and aggregate cohorts
Channels, goals, and source segments
Amounts and source attribution
Venues, dates, and ticketing
Tracks, albums, and content
Amounts, sources, and types
The actions
The proposed interfaces let approved tools query records, receive updates, and export data. CRMs and campaign tools can then use those records within the supplied permissions.
What to test first Exports, webhooks, and a small set of integrations are candidates for the proof of concept. The white paper will define that scope and which actions belong in connected tools.
SEGMENT
Supply approved source data to tools that build audiences. Cross-source segments depend on available identifiers, permissions, and the matching method those tools use.
ACTIVATE
Send permitted records to an approved CRM, email tool, or advertising platform through a supported connector.
TRIGGER
Explore notifications when source data meets a defined condition, such as ticket sales reaching a target. The white paper will address whether these rules belong in ADAPT or connected tools.
EXPORT
The proposed standard would support documented exports of permitted records and aggregates, including source context and applicable access restrictions.
BUILD
Define an API so developers can query approved fields and build integrations against documented schemas.
Who can access what
Identify who can grant access An artist’s identity is separate from their legal entities and representatives. Each grant needs to name the authorized party and the records they can read, export, or change.
Authority or consent may involve an individual, an entity, or several parties. How to verify that authority and handle changes still needs legal and technical review.
A copy is not exclusive ownership Sources can retain their records while sharing permitted copies. Receiving or hosting data does not grant unrestricted use or transfer rights.
These roles are examples, not automatic access rights. Access depends on source restrictions, permissions, and who has authority to grant it.
| Role | Access Level | Example |
|---|---|---|
| Artist | Manage access to permitted artist data. | Review available records, export permitted fields, and grant access to collaborators. |
| Manager | Operational access as granted by the artist. | Build segments, activate campaigns, view fan-level data, manage team permissions. |
| Label | Aggregate insights. No individual fan records unless explicitly shared. | Roster performance dashboards, market-level growth trends, release impact analysis. |
| Developer | Scoped API access to approved objects and properties. | Build apps on the ontology with permissioned read/write to specific data. |
| Publisher | Artist-approved catalog and performance data. | Reporting on relevant works. |
| Platform | Scoped data exchange with source permissions. | Supply records and receive approved updates. |
| Promoter | Approved event and market aggregates. | Plan shows without unrestricted fan access. |
Fan rights
Artist control must respect the rights of the people represented in the data. The technical design must establish what personal data is needed, how permission is recorded, and how access and deletion requests are handled.
One place to opt out Fans should be able to manage opt-outs across participating services in one place. This service is not live. The specification must define how each request is verified, sent to connected tools, confirmed, and enforced, including any required retention.
Source permissions, retention, deletion, and any identity matching still need review. Artist authorization alone is not permission for every downstream use.
Choose a host
Keep the context
Choose the destination ADAPT plans to operate the connection hub. A CRM, label, distributor, or independent provider may host the receiving database. Participation does not require a competitor’s hosting.
What moves? The specification must list exportable records, schema versions, source history, and permission evidence. Application features and derived outputs are not automatically included.
Changing providers Before a transfer, check who authorized it, which records can move, and whether the receiving host imported them correctly. The previous host must follow the agreed retention and access terms. Moving data does not erase every existing copy.
Clear terms
for data exchange
Shared formats and standard agreement templates could reduce the work of transferring data in and out. They would complement technical access controls, not override source restrictions or establish permission by themselves.
What the terms must cover Allowed uses, further transfers, retention, deletion, withdrawal of access, source history, and each party’s responsibilities when providers change. The technical controls must enforce those terms.
Open questions We still need legal and technical review of who can authorize access, when several parties must consent, how identities are matched, and the legal basis for each use. The white paper and proof of concept must address these questions.
An open
protocol
The specification The proposed specification will describe record types, relationships, permissions, and interfaces. Documented export formats are part of that work.
The operating model ADAPT is building the neutral hub and open standard. Data routing, any temporary storage, security responsibilities, and retention limits must be specified and tested before launch. Compatible destination providers can offer their own storage and services.
Participation We are building ADAPT as a nonprofit. Our goal is to never put a pay gate between artists and access to their data. A platform membership fee is under consideration; third-party services may charge separately.
Current status This is a working technical proposal, not a completed specification or compliance guarantee. Schemas, API interfaces, legal arrangements, and versioning rules remain in development.