Skip to main content
Agent skill

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).

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Data Manager Api Setup when an AI agent needs a reusable SKILL.md workflow for this job: 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).

When not to use it

Skip Data Manager Api Setup when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/data-manager-api-setup
# Save SKILL.md to ~/.claude/skills/data-manager-api-setup/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/data-manager-api-setup/SKILL.md. For a shared project, commit the folder at .claude/skills/data-manager-api-setup/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Data Manager Api Setup skill for this task: Use Data Manager Api Setup when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Data Manager API Setup

## Setup Authentication

Refer to [Set up API access](https://developers.google.com/data-manager/api/devguides/quickstart/set-up-access.md.txt) 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.

```shell gcloud services enable datamanager.googleapis.com --project={project_id} gcloud services list --enabled --project=PROJECT_ID --filter="datamanager.googleapis.com" ```

### 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:

```shell gcloud auth application-default login \ --scopes="https://www.googleapis.com/auth/datamanager,https://www.googleapis.com/auth/cloud-platform" \ --client-id-file="{client_id_file_path}" ```

**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](https://developers.google.com/data-manager/api/devguides/concepts/oauth-verification.md.txt). 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:

```shell gcloud auth application-default login \ --impersonate-service-account={service_account_email} \ --scopes="https://www.googleapis.com/auth/datamanager,https://www.googleapis.com/auth/cloud-platform" ``` * **Data partner creating partner links** in advertiser accounts: Read [Partner Links](references/partner-links.md).

**Multiple APIs**: To use the same credentials for other APIs, append their scopes to the `--scopes` list in the commands above (e.g., `https://www.googleapis.com/auth/adwords` for the Google Ads API or `https://www.googleapis.com/auth/display-video` for the Display & Video 360 API).

**Verify**: `gcloud auth application-default print-access-token` prints an access token when credentials are set up correctly.

**Troubleshooting `PERMISSION_DENIED` with a valid token**: Add the user or service account to the destination account (for example, the Google Ads account or its manager account). For service accounts, also confirm the `Service Usage Consumer` role on the Cloud project.

**Production**: For production authentication (workloads in or outside Google Cloud, apps that act on behalf of other users, or partner links), see [Deploy to production](https://developers.google.com/data-manager/api/devguides/concepts/deploy.md.txt).

## Install Client & Utility Libraries

Refer to [Install a client library](https://developers.google.com/data-manager/api/devguides/quickstart/install-library.md.txt) for more details.

The companion utility libraries provide pre-built helper classes and functions to correctly format, hash, and encrypt user identifiers (such as emails, phone numbers, and physical addresses) prior to API ingestion. Use of these libraries is highly recommended to ensure that user identifier formatting matches the API's specifications.

Select the language-specific installation guide below:

* [Python Setup Reference](references/python.md) (packages: `google-ads-datamanager` and `google-ads-datamanager-util`) * [Java Setup Reference](references/java.md) (packages: `com.google.api-ads:data-manager` and `com.google.api-ads:data-manager-util`) * [Node Setup Reference](references/node.md) (packages: `@google-ads/datamanager` and `@google-ads/datamanager-util`) * [PHP Setup Reference](references/php.md) (packages: `googleads/data-manager` and `googleads/data-manager-util`) * [.NET Setup Reference](references/dotnet.md) (packages: `Google.Ads.DataManager.V1` and `Google.Ads.DataManager.Util`)

Intended uses

  • Use Data Manager Api Setup when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.