Docs

Scopes and roles

Scopes are the same strings for secret keys, OAuth tokens (MCP connectors) and dashboard users (derived from the member's role). Write scopes do not imply read scopes, except conversions:write (includes conversions:read) and org:admin (includes project:create).

Scopes

ScopeAllows
analytics:readRead analytics: overview, breakdowns, sessions, pages, videos, funnels, relevance, events, SQL
leads:readRead leads and identify data (personal data)
leads:writeCreate, update and erase leads
events:writeSend server-side events
conversions:readList conversions and their upload status
conversions:writeMark, retry and update conversions (uploads to ad platforms)
ads:readRead ad cost and performance data
ads:writeConnect ad accounts, trigger syncs, edit UTM mappings
config:writeEdit goals, funnels, relevance model, event schemas, questionnaires
project:adminProject settings, tracking config, publishable keys, conversion destinations
project:createCreate projects (a narrowed key or grant gains access to the projects it creates)
org:adminProjects, secret keys, members of the organization
ingest:proxyFirst-party proxy: trusted client IP/country headers on ingest

Roles

Dashboard members get the scopes of their role. leads:read and leads:write additionally need the member's personal-data permission (pii); owners always have it. Owners and admins may also put ingest:proxy on keys they create.

Scopeowneradminanalystviewer
analytics:readyesyesyesyes
leads:readyesyesyes–
leads:writeyesyes––
events:writeyesyes––
conversions:read––yes–
conversions:writeyesyes––
ads:readyesyesyesyes
ads:writeyesyes––
config:writeyesyesyes–
project:adminyesyes––
project:createyesyes––
org:adminyesyes––
ingest:proxy––––
  • Read only: analytics:read, conversions:read, ads:read.
  • Read and write (default): analytics:read, conversions:read, ads:read, events:write, conversions:write, ads:write, config:write, project:admin, project:create, ingest:proxy.
  • Opt-in checkboxes, unchecked by default: org:admin, leads:read, leads:write (personal-data scopes are only offered to members with the pii permission).

A grant never exceeds what the user can do in the organization right now: every request intersects the granted scopes with the member's live role.