|
Open in ChatGPTClaudePerplexity

Measurement partners

Affiliate networks, dashboard tools, and analytics platforms can read OA telemetry data on behalf of content owners who grant them access. No proprietary integration - you query the same API publishers use.

How it works

text 
Content owner                    Measurement partner
     |                                  |
     |  1. Grants delegation            |
     |  (dashboard or API)              |
     |                                  |
     |                                  |  2. Queries publisher endpoints
     |                                  |     ?delegated_from={owner_org_id}
     |                                  |
     |           OA gateway             |
     |      checks delegation table     |
     |      returns owner's data        |
     |                                  |

The content owner grants you telemetry:read access via the OA dashboard or API. You authenticate with your own API key and pass delegated_from on publisher endpoints to access their data.

Getting started

1. Register your organisation

Sign up at openattribution.org and create an API key with telemetry:read scope.

2. Content owners grant access

The content owner goes to Measurement partners in their OA dashboard and enters your organisation ID. This creates a delegation - immediately active, revocable at any time.

Alternatively, they can use the API:

json 
POST /api/v1/identity/delegations
{
  "grantee_org_id": "your-org-id",
  "scopes": ["telemetry:read"]
}

3. Query their telemetry

Use the same publisher endpoints, adding your authentication and the delegated_from parameter:

text 
GET /api/v1/telemetry/publisher/summary?delegated_from={owner_org_id}&since=2026-03-01
X-API-Key: oa_yourkey...

You get the same response a content owner would see - total events, agent breakdown, top URLs. All three publisher endpoints support delegation: /publisher/summary, /publisher/events, and /publisher/urls.

What you can build

AI traffic dashboards

Show publishers which AI agents are fetching their content, how often, and which URLs. Net-new data that doesn't exist in any affiliate dashboard today.

Attribution models

When citation and outcome data flows, build multi-touch attribution across the content influence chain. Which content was retrieved, cited, and led to a purchase.

Aggregated reporting

Query across all content owners who have granted you access. Build network-wide views of AI agent activity.

Data isolation
Each delegation is a separate grant. You can only access data for content owners who have explicitly granted you access. No cross-publisher aggregation happens on the OA side - you aggregate across your own delegations.

Managing delegations

List your delegations

text 
GET /api/v1/identity/delegations?role=grantee
X-API-Key: oa_yourkey...
json 
[
  {
    "id": "...",
    "grantor_org_id": "...",
    "grantee_org_id": "your-org-id",
    "grantor_name": "Wirecutter",
    "grantee_name": "Your Network",
    "scopes": ["telemetry:read"],
    "created_at": "2026-03-24T...",
    "revoked_at": null
  }
]

Use the grantor_org_id from each delegation as the delegated_from parameter when querying publisher endpoints.

On the roadmap
Webhook delivery (OA pushes events as they arrive) and bulk delegation APIs for onboarding large publisher bases are next on the roadmap.