Agent skill · software engineering · google

data-manager-api-setup

Guides developers through client library installation and authentication setup steps for the Data Manager API. Use this skill when a user is getting started with the Data Manager API and needs to setup their local environment, install the client library, or setup access to the API. Don't use for implementing audience or event ingestion logic (use the data-manager-api-audience-ingestion or data-manager-api-event-ingestion skills instead).

Why this skill is useful

Provides specific installation and authentication steps for the Data Manager API client libraries that the AI wouldn't reliably generate on its own.

What it needs

Requires gcloud installed locally. Requires googlecloud account access. About 3k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

Data Manager API Setup Setup Authentication Refer to Set up API access for more details. 1. Enable the API Prerequisites: A Google Cloud project, the Google Cloud CLI (gcloud), and a Google Account with a project role that can enable APIs, such as Owner, Editor, or Service Usage Admin. Always tell the user about the required role. If gcloud isn't installed, prompt the user to install it first. 2. Generate Application Default Credentials (ADC) Choose the method that matches the user's scenario: User account (API calls are made as the user's own Google Account): The Data Manager API scopes are sensitive, so the user must first configure their project's Google Auth Platform: 1. Data Access page: Add the Data Manager API scopes. 2. Audience page: Set Publishing status to Testing. Use the Internal user type for a Google Workspace organization, or External with the user's account added as a Test user. 3. Create (or reuse) a Desktop app OAuth client and download its JSON configuration file. 4. The user runs the following command, which opens a browser login: Unverified app screen: This warning appears because the Data Manager API scopes are sensitive. During Testing, External test users still see it and can continue past it. Before other users can sign in, the app must complete OAuth app verification. Service accounts don't need verification. Service account (API calls are made as an app identity instead of a person): For local development, use service account impersonation rather than a service account key, since keys are a security risk if not managed carefully. Grant the Service Account the Service Usage Consumer IAM role (roles/serviceusage.serviceUsageConsumer) on the project. Grant the user executing gcloud the Token Creator role (roles/iam.serviceAccountTokenCreator) on that Service Account. Run: Data partner creating partner links in advertiser accounts: Read Partner Links. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/data-manager-api-setup

View the source on GitHub

Browse the @skills marketplace