跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
数据与分析

data-manager-api-audience-ingestion

Guides developers through managing (adding, removing, and clearing) audience members for Google products using the Data Manager API and its associated client libraries. Use this skill when the user wants to upload audience members, remove specific users, or clear/replace an entire audience for Customer Match, mobile device ID audiences, or any other audience use case supported by the Data Manager API. Don't use for uploading events or conversions (use the data-manager-api-event-ingestion skill).

google · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add google/skills --skill data-manager-api-audience-ingestion

技能说明


name: data-manager-api-audience-ingestion description: >- Guides developers through managing (adding, removing, and clearing) audience members for Google products using the Data Manager API and its associated client libraries. Use this skill when the user wants to upload audience members, remove specific users, or clear/replace an entire audience for Customer Match, mobile device ID audiences, or any other audience use case supported by the Data Manager API. Don't use for uploading events or conversions (use the data-manager-api-event-ingestion skill). metadata: version: 1.1 category: GoogleAds

Data Manager API Audience Ingestion

Implementation Workflow

Prerequisites

  • Authentication & Library Installation: If you need to set up access to the Data Manager API or install the client and utility libraries, refer to the data-manager-api-setup skill.
  • Audience Creation (if needed): If the user does not have an existing audience or needs to create a new one, use the Create an Audience reference. This step provides the product_destination_id needed for the ingestion or removal requests.

Step 1: Identify Use Case & Read Documentation

  • Determine Destination Account Type: [CRITICAL] If it's not clear where the data is being sent (e.g., Google Ads, Display & Video 360, etc.), STOP and CLARIFY with the user BEFORE generating any code. Do not assume Google Ads by default. This maps to the account_type field of the operating_account in the Destination.
  • Read the implementation guide: Read the relevant guide for your destination and use case. Do this before answering questions or writing code because each destination has unique payload structures, consent rules, and required fields.
DestinationAudience TypeAccepted Data TypesUpload GuideRemove All/Replace All Guide
Google AdsCustomer Matchcomposite_data.user_data (contact info), mobile_data (device IDs), user_id_data (user IDs)Upload DataRemove All/Replace All
Display & Video 360 (DV360)Customer Matchcomposite_data.user_data (contact info), mobile_data (device IDs)Upload DataRemove All/Replace All

Step 2: Retrieve Code Sample

[!IMPORTANT] If writing or updating an ingestion script, ALWAYS retrieve the relevant code sample to use as a reference:

LanguageSample
Pythoningest_audience_members.py
JavaIngestAudienceMembers.java
PHPingest_audience_members.php
Nodeingest_audience_members.ts
.NETIngestAudienceMembers.cs

Step 3: Retrieve Migration Guides

[!IMPORTANT] If refactoring code to upgrade from another Google API, ALWAYS extract the full contents of the relevant field mapping guide.

Google Ads

Display & Video 360

Step 4: Implementation

Implement the ingestion logic using the following checkpoints:

  • Initialize Client: Instantiate the Data Manager client (IngestionServiceClient).
  • Define Destinations: Build the Destination object using the product_destination_id and the appropriate account configurations: operating_account (target account receiving data), login_account (if authenticating using a manager account or a data partner account), and linked_account (if you're a data partner accessing the account via a partner link to a manager account). STRONGLY RECOMMENDED: Refer to the Configure destinations and headers guide for more details on configuring destinations.
  • Format User Data: If sending an IngestAudienceMembersRequest or RemoveAudienceMembersRequest, refer to Formatting User Data to properly normalize and hash user identifiers using the utility library.
  • Construct Payload: Build the appropriate request payload based on the operation:
    • Add: IngestAudienceMembersRequest
    • Remove: RemoveAudienceMembersRequest
    • Remove All: RemoveAllAudienceMembersRequest
  • Support Validation: Support sending the validate_only boolean option on the payload to allow developers to validate schemas wi
阅读完整来源 ↗