[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698X2YVQMTFX9PCB39N165V":3,"skill-same:01M698X2YVQMTFX9PCB39N165V":93},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M698X2YVQMTFX9PCB39N165V","data-manager-api-audience-ingestion",null,"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\u002Freplace 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\u002Fskills","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698WR0H76ENHE587T9EJT89",24044,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fads\u002Fdata-manager-api-audience-ingestion\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[32,33,34,35,36,37,9,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"data manager api audience ingestion","data","api","manager","ingestion","when","entire","for","event","case","users","guides","id","clear","upload","mobile","use","remove","libraries","customer","2026-11-10 10:12:30",false,"---\nname: data-manager-api-audience-ingestion\ndescription: >-\n  Guides developers through managing (adding, removing, and clearing) audience members for Google products using\n  the Data Manager API and its associated client libraries. Use this skill when the user wants to upload audience\n  members, remove specific users, or clear\u002Freplace an entire audience for Customer Match, mobile device ID audiences, or any\n  other audience use case supported by the Data Manager API. Don't use for uploading events or\n  conversions (use the data-manager-api-event-ingestion skill).\nmetadata:\n  version: \"1.1.0\"\n  category: GoogleAds\n---\n\n# Data Manager API Audience Ingestion\n\n## Implementation Workflow\n\n### Prerequisites\n\n-   **Authentication & Library Installation**: If you need to set up access to\n    the Data Manager API or install the client and utility libraries, refer to\n    the `data-manager-api-setup` skill.\n-   **Audience Creation (if needed)**: If the user does not have an existing\n    audience or needs to create a new one, use the\n    [Create an Audience](references\u002Fcreate-audience.md) reference. This step\n    provides the `product_destination_id` needed for the ingestion or removal\n    requests.\n\n### Step 1: Identify Use Case & Read Documentation\n\n-   **Determine Destination Account Type**: [CRITICAL] If it's not clear where\n    the data is being sent (e.g., Google Ads, Display & Video 360, etc.), STOP\n    and CLARIFY with the user BEFORE generating any code. Do not assume Google\n    Ads by default. This maps to the `account_type` field of the\n    `operating_account` in the `Destination`.\n-   **Read the implementation guide**: Read the relevant guide for your\n    destination and use case. Do this before answering questions or writing code\n    because each destination has unique payload structures, consent rules, and\n    required fields.\n\n| Destination | Audience Type | Accepted Data Types | Upload Guide | Remove All\u002FReplace All Guide |\n| :--- | :--- | :--- | :--- | :--- |\n| **Google Ads** | Customer Match | `composite_data.user_data` (contact info), `mobile_data` (device IDs), `user_id_data` (user IDs) | [Upload Data](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fupload-data.md.txt) | [Remove All\u002FReplace All](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fremove-all-members.md.txt) |\n| **Display & Video 360** (DV360) | Customer Match | `composite_data.user_data` (contact info), `mobile_data` (device IDs) | [Upload Data](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\u002Fupload-data.md.txt) | [Remove All\u002FReplace All](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\u002Fremove-all-members.md.txt) |\n\n### Step 2: Retrieve Code Sample\n\n> [!IMPORTANT] If writing or updating an ingestion script, ALWAYS retrieve the\n> relevant code sample to use as a reference:\n\n| Language | Sample |\n| :--- | :--- |\n| **Python** | [`ingest_audience_members.py`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-python\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.py) |\n| **Java** | [`IngestAudienceMembers.java`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-java\u002Fblob\u002Fmain\u002Fdata-manager-samples\u002Fsrc\u002Fmain\u002Fjava\u002Fcom\u002Fgoogle\u002Fads\u002Fdatamanager\u002Fsamples\u002FIngestAudienceMembers.java) |\n| **PHP** | [`ingest_audience_members.php`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-php\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.php) |\n| **Node** | [`ingest_audience_members.ts`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-node\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.ts) |\n| **.NET**| [`IngestAudienceMembers.cs`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-dotnet\u002Fblob\u002Fmain\u002Fsamples\u002FIngestAudienceMembers.cs) |\n\n### Step 3: Retrieve Migration Guides\n\n> [!IMPORTANT] If refactoring code to upgrade from another Google API, ALWAYS\n> extract the full contents of the relevant field mapping guide.\n\n#### Google Ads\n\n*   **Google Ads API Customer Match**: [Google Ads API to Customer Match\n    Migration Field\n    Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Display & Video 360\n\n*   **Display & Video 360 API Customer Match**: [Display & Video 360 API to\n    Customer Match Migration Field\n    Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n### Step 4: Implementation\n\nImplement the ingestion logic using the following checkpoints:\n\n-   [ ] **Initialize Client**: Instantiate the Data Manager client\n    (`IngestionServiceClient`).\n-   [ ] **Define Destinations**: Build the `Destination` object using the\n    `product_destination_id` and the appropriate account configurations:\n    `operating_account` (target account receiving data), `login_account` (if\n    authenticating using a manager account or a data partner account), and\n    `linked_account` (if you're a data partner accessing the account via a\n    partner link to a manager account). **STRONGLY RECOMMENDED**: Refer to the\n    [Configure destinations and headers](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Fdestinations.md.txt)\n    guide for more details on configuring destinations.\n-   [ ] **Format User Data**: If sending an `IngestAudienceMembersRequest` or\n    `RemoveAudienceMembersRequest`, refer to **[Formatting User\n    Data](references\u002Fformatting.md)** to properly normalize and hash user identifiers using\n    the utility library.\n-   [ ] **Construct Payload**: Build the appropriate request payload based on\n    the operation:\n    *   **Add**: `IngestAudienceMembersRequest`\n    *   **Remove**: `RemoveAudienceMembersRequest`\n    *   **Remove All**: `RemoveAllAudienceMembersRequest`\n-   [ ] **Support Validation**: Support sending the `validate_only` boolean\n    option on the payload to allow developers to validate schemas without\n    actually applying changes.\n-   [ ] **Send Request**: Execute the appropriate method and record the returned\n    `request_id` for later diagnostics:\n    *   **Add**: `ingest_audience_members`\n    *   **Remove**: `remove_audience_members`\n    *   **Remove All**: `remove_all_audience_members`\n-   [ ] **Check for Ingestion Warnings**: If any non-required field had a\n    validation failure, the response from `ingest_audience_members` will also\n    include `field_warnings`, a list of `FieldWarning` objects detailing the\n    issues.\n-   [ ] **Retrieve Request Status**: Check the status of the ingestion request\n    using diagnostics. Since request processing is asynchronous, a successful\n    response (HTTP 200 OK returning a `request_id`) only indicates the payload\n    was received. To check if the records actually succeeded, partially\n    succeeded, or failed to process, query `client.retrieve_request_status`\n    using the `request_id`. Skipping this step is a common user mistake.\n\n## Critical Gotchas\n\n*   If sending hashed user identifiers in `user_data` for\n    `ingest_audience_members` or `remove_audience_members`, you must set the\n    `encoding` field on the `IngestAudienceMembersRequest` to `HEX` or `BASE64`.\n*   If *uploading* to a Customer Match audience, the `terms_of_service` field is\n    required on the `IngestAudienceMembersRequest` to indicate the user has\n    accepted the policies.\n*   Only set the `address` field on `UserIdentifier` if all required fields\n    (`postal_code`, `family_name`, `given_name`, `region_code`) are present;\n    incomplete `address` fields will cause the API request to fail.\n*   `product_destination_id` must be a numeric string. It is NOT a resource\n    name.\n*   The enum values for `ConsentStatus` are `CONSENT_GRANTED` and\n    `CONSENT_DENIED`. Do not use the values `GRANTED` and `DENIED`.\n*   Field names on `UserIdentifier` are `email_address` and `phone_number`. Do\n    not use the Google Ads API field names `hashed_email` and\n    `hashed_phone_number`.\n*   Do not call the diagnostics endpoint (`retrieve_request_status`) if\n    `validate_only` is set to `true`.\n\n## Error Handling & Troubleshooting\n\n### Inspecting Error Payloads & Ingestion Warnings\n\n> [!IMPORTANT]\n> Refer to [Understand API Errors](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Funderstand-errors.md.txt)\n> for a detailed guide on how to understand the structure of errors and warnings\n> returned by the API.\n\n### Retrieving Request Status (Diagnostics)\n\nPeriodically poll for status using exponential backoff, starting at least 30\nminutes after sending the request.\n\n1.  Call `client.retrieve_request_status` using\n    `RetrieveRequestStatusRequest(request_id=...)`.\n2.  Loop through `request_status_per_destination` in the response to inspect\n    each target's `request_status`.\n3.  If processing is complete and `request_status` is `SUCCESS`,\n    `PARTIAL_SUCCESS`, or `FAILED`, inspect diagnostic values:\n    *   **Audience Status**: Check the status specific to your request:\n        *   **Ingest**: Check the data-type-specific status nested under\n            `audience_members_ingestion_status` (e.g.,\n            `composite_data_ingestion_status`).\n        *   **Remove Individual Members**: Check the data-type-specific status\n            nested under `audience_members_removal_status` (e.g.,\n            `composite_data_removal_status`).\n        *   **Remove All Members**: There are no nested status fields or record\n            counts available to check for this request type.\n        *   **Record Count**: If applicable (ingest or remove individual\n            members), check `record_count` (nested inside the data-type-specific\n            status object) which includes both success and failure.\n        *   **Identifier Counts**: If applicable (ingest or remove individual\n            members), check the data-type-specific count field nested inside the\n            status object (e.g., `data_type_counts` if uploading or removing\n            composite data, or `mobile_id_count` if uploading or removing\n            mobile IDs). Refer to the [Diagnostics\n            Guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fdiagnostics.md.txt)\n            for other count fields.\n        *   **Match Rate Range**: For uploads of `user_data` and\n            `composite_data`, check `upload_match_rate_range` nested inside the\n            status object.\n    *   **Error Details**: If status is `FAILED` or `PARTIAL_SUCCESS`, inspect\n        each error's `reason` and `record_count` under\n        `error_info.error_counts`.\n    *   **Warning Details**: Inspect each warning's `reason` and `record_count`\n        under `warning_info.warning_counts` (even if the destination status is\n        `SUCCESS`).\n\n## API Reference\n\n*   [Send audience members guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fsend-audience-members.md.txt)\n*   [REST API Reference: Ingest](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002FaudienceMembers\u002Fingest.md.txt)\n*   [REST API Reference: Remove](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002FaudienceMembers\u002Fremove.md.txt)\n*   [REST API Reference: Remove All](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002FaudienceMembers\u002FremoveAll.md.txt)\n","# Data Manager API Audience Ingestion\n\n## Implementation Workflow\n\n### Prerequisites\n\n-   **Authentication & Library Installation**: If you need to set up access to\n    the Data Manager API or install the client and utility libraries, refer to\n    the `data-manager-api-setup` skill.\n-   **Audience Creation (if needed)**: If the user does not have an existing\n    audience or needs to create a new one, use the\n    [Create an Audience](references\u002Fcreate-audience.md) reference. This step\n    provides the `product_destination_id` needed for the ingestion or removal\n    requests.\n\n### Step 1: Identify Use Case & Read Documentation\n\n-   **Determine Destination Account Type**: [CRITICAL] If it's not clear where\n    the data is being sent (e.g., Google Ads, Display & Video 360, etc.), STOP\n    and CLARIFY with the user BEFORE generating any code. Do not assume Google\n    Ads by default. This maps to the `account_type` field of the\n    `operating_account` in the `Destination`.\n-   **Read the implementation guide**: Read the relevant guide for your\n    destination and use case. Do this before answering questions or writing code\n    because each destination has unique payload structures, consent rules, and\n    required fields.\n\n| Destination | Audience Type | Accepted Data Types | Upload Guide | Remove All\u002FReplace All Guide |\n| :--- | :--- | :--- | :--- | :--- |\n| **Google Ads** | Customer Match | `composite_data.user_data` (contact info), `mobile_data` (device IDs), `user_id_data` (user IDs) | [Upload Data](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fupload-data.md.txt) | [Remove All\u002FReplace All](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fremove-all-members.md.txt) |\n| **Display & Video 360** (DV360) | Customer Match | `composite_data.user_data` (contact info), `mobile_data` (device IDs) | [Upload Data](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\u002Fupload-data.md.txt) | [Remove All\u002FReplace All](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\u002Fremove-all-members.md.txt) |\n\n### Step 2: Retrieve Code Sample\n\n> [!IMPORTANT] If writing or updating an ingestion script, ALWAYS retrieve the\n> relevant code sample to use as a reference:\n\n| Language | Sample |\n| :--- | :--- |\n| **Python** | [`ingest_audience_members.py`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-python\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.py) |\n| **Java** | [`IngestAudienceMembers.java`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-java\u002Fblob\u002Fmain\u002Fdata-manager-samples\u002Fsrc\u002Fmain\u002Fjava\u002Fcom\u002Fgoogle\u002Fads\u002Fdatamanager\u002Fsamples\u002FIngestAudienceMembers.java) |\n| **PHP** | [`ingest_audience_members.php`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-php\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.php) |\n| **Node** | [`ingest_audience_members.ts`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-node\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.ts) |\n| **.NET**| [`IngestAudienceMembers.cs`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-dotnet\u002Fblob\u002Fmain\u002Fsamples\u002FIngestAudienceMembers.cs) |\n\n### Step 3: Retrieve Migration Guides\n\n> [!IMPORTANT] If refactoring code to upgrade from another Google API, ALWAYS\n> extract the full contents of the relevant field mapping guide.\n\n#### Google Ads\n\n*   **Google Ads API Customer Match**: [Google Ads API to Customer Match\n    Migration Field\n    Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Display & Video 360\n\n*   **Display & Video 360 API Customer Match**: [Display & Video 360 API to\n    Customer Match Migration Field\n    Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n### Step 4: Implementation\n\nImplement the ingestion logic using the following checkpoints:\n\n-   [ ] **Initialize Client**: Instantiate the Data Manager client\n    (`IngestionServiceClient`).\n-   [ ] **Define Destinations**: Build the `Destination` object using the\n    `product_destination_id` and the appropriate account configurations:\n    `operating_account` (target account receiving data), `login_account` (if\n    authenticating using a manager account or a data partner account), and\n    `linked_account` (if you're a data partner accessing the account via a\n    partner link to a manager account). **STRONGLY RECOMMENDED**: Refer to the\n    [Configure destinations and headers](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Fdestinations.md.txt)\n    guide for more details on configuring destinations.\n-   [ ] **Format User Data**: If sending an `IngestAudienceMembersRequest` or\n    `RemoveAudienceMembersRequest`, refer to **[Formatting User\n    Data](references\u002Fformatting.md)** to properly normalize and hash user identifiers using\n    the utility library.\n-   [ ] **Construct Payload**: Build the appropriate request payload based on\n    the operation:\n    *   **Add**: `IngestAudienceMembersRequest`\n    *   **Remove**: `RemoveAudienceMembersRequest`\n    *   **Remove All**: `RemoveAllAudienceMembersRequest`\n-   [ ] **Support Validation**: Support sending the `validate_only` boolean\n    option on the payload to allow developers to validate schemas without\n    actually applying changes.\n-   [ ] **Send Request**: Execute the appropriate method and record the returned\n    `request_id` for later diagnostics:\n    *   **Add**: `ingest_audience_members`\n    *   **Remove**: `remove_audience_members`\n    *   **Remove All**: `remove_all_audience_members`\n-   [ ] **Check for Ingestion Warnings**: If any non-required field had a\n    validation failure, the response from `ingest_audience_members` will also\n    include `field_warnings`, a list of `FieldWarning` objects detailing the\n    issues.\n-   [ ] **Retrieve Request Status**: Check the status of the ingestion request\n    using diagnostics. Since request processing is asynchronous, a successful\n    response (HTTP 200 OK returning a `request_id`) only indicates the payload\n    was received. To check if the records actually succeeded, partially\n    succeeded, or failed to process, query `client.retrieve_request_status`\n    using the `request_id`. Skipping this step is a common user mistake.\n\n## Critical Gotchas\n\n*   If sending hashed user identifiers in `user_data` for\n    `ingest_audience_members` or `remove_audience_members`, you must set the\n    `encoding` field on the `IngestAudienceMembersRequest` to `HEX` or `BASE64`.\n*   If *uploading* to a Customer Match audience, the `terms_of_service` field is\n    required on the `IngestAudienceMembersRequest` to indicate the user has\n    accepted the policies.\n*   Only set the `address` field on `UserIdentifier` if all required fields\n    (`postal_code`, `family_name`, `given_name`, `region_code`) are present;\n    incomplete `address` fields will cause the API request to fail.\n*   `product_destination_id` must be a numeric string. It is NOT a resource\n    name.\n*   The enum values for `ConsentStatus` are `CONSENT_GRANTED` and\n    `CONSENT_DENIED`. Do not use the values `GRANTED` and `DENIED`.\n*   Field names on `UserIdentifier` are `email_address` and `phone_number`. Do\n    not use the Google Ads API field names `hashed_email` and\n    `hashed_phone_number`.\n*   Do not call the diagnostics endpoint (`retrieve_request_status`) if\n    `validate_only` is set to `true`.\n\n## Error Handling & Troubleshooting\n\n### Inspecting Error Payloads & Ingestion Warnings\n\n> [!IMPORTANT]\n> Refer to [Understand API Errors](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Funderstand-errors.md.txt)\n> for a detailed guide on how to understand the structure of errors and warnings\n> returned by the API.\n\n### Retrieving Request Status (Diagnostics)\n\nPeriodically poll for status using exponential backoff, starting at least 30\nminutes after sending the request.\n\n1.  Call `client.retrieve_request_status` using\n    `RetrieveRequestStatusRequest(request_id=...)`.\n2.  Loop through `request_status_per_destination` in the response to inspect\n    each target's `request_status`.\n3.  If processing is complete and `request_status` is `SUCCESS`,\n    `PARTIAL_SUCCESS`, or `FAILED`, inspect diagnostic values:\n    *   **Audience Status**: Check the status specific to your request:\n        *   **Ingest**: Check the data-type-specific status nested under\n            `audience_members_ingestion_status` (e.g.,\n            `composite_data_ingestion_status`).\n        *   **Remove Individual Members**: Check the data-type-specific status\n            nested under `audience_members_removal_status` (e.g.,\n            `composite_data_removal_status`).\n        *   **Remove All Members**: There are no nested status fields or record\n            counts available to check for this request type.\n        *   **Record Count**: If applicable (ingest or remove individual\n            members), check `record_count` (nested inside the data-type-specific\n            status object) which includes both success and failure.\n        *   **Identifier Counts**: If applicable (ingest or remove individual\n            members), check the data-type-specific count field nested inside the\n            status object (e.g., `data_type_counts` if uploading or removing\n            composite data, or `mobile_id_count` if uploading or removing\n            mobile IDs). Refer to the [Diagnostics\n            Guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fdiagnostics.md.txt)\n            for other count fields.\n        *   **Match Rate Range**: For uploads of `user_data` and\n            `composite_data`, check `upload_match_rate_range` nested inside the\n            status object.\n    *   **Error Details**: If status is `FAILED` or `PARTIAL_SUCCESS`, inspect\n        each error's `reason` and `record_count` under\n        `error_info.error_counts`.\n    *   **Warning Details**: Inspect each warning's `reason` and `record_count`\n        under `warning_info.warning_counts` (even if the destination status is\n        `SUCCESS`).\n\n## API Reference\n\n*   [Send audience members guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fsend-audience-members.md.txt)\n*   [REST API Reference: Ingest](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002FaudienceMembers\u002Fingest.md.txt)\n*   [REST API Reference: Remove](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002FaudienceMembers\u002Fremove.md.txt)\n*   [REST API Reference: Remove All](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002FaudienceMembers\u002FremoveAll.md.txt)\n",{"name":5,"metadata":57,"description":7},{"version":58,"category":59},"1.1.0","GoogleAds","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fads\u002Fdata-manager-api-audience-ingestion",2002,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-13 02:42:47",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add google\u002Fskills --skill data-manager-api-audience-ingestion",{"tool":75,"command":76},"bunx","bunx skills add google\u002Fskills --skill data-manager-api-audience-ingestion",{"tool":78,"command":79},"pnpm","pnpm dlx skills add google\u002Fskills --skill data-manager-api-audience-ingestion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fads\u002Fdata-manager-api-audience-ingestion\u002FSKILL.md",true,[83,89],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fcreate-audience.md","REFERENCE","参考文档",2107,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fads\u002Fdata-manager-api-audience-ingestion\u002Freferences\u002Fcreate-audience.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fformatting.md",633,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fads\u002Fdata-manager-api-audience-ingestion\u002Freferences\u002Fformatting.md",[94,127,154,182,209,233],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":104,"publishedAt":52},"01M6998S2EZKD3GEJ7F943RZTE","sign-in-with-google-web","Implement, configure, and secure Sign In With Google (SiwG) using Google Identity Services (GIS \u002F `https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fclient`) across web architectures. Use when creating Google sign-in buttons, implementing Google One Tap with FedCM, integrating GIS in React\u002FNext.js\u002FAngular\u002FHTML, verifying ID tokens on backend runtimes (Python\u002FNode.js\u002FGo\u002FJava), enforcing Google Workspace domain restrictions (`hd`), securing client-side ID tokens via WebCrypto nonces or encrypted IndexedDB, embedding in cross-origin iframes via the Intermediate Iframe API (`https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fintermediate`), configuring Content Security Policy (CSP), COOP, and Permissions Policy (`identity-credentials-get`) headers, or handling sign-out and revocation. Don't use for legacy Google Sign-In (`gapi.auth2`), Google Cloud IAM service accounts, or Android\u002FiOS native Credential Manager.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fsign-in-with-google-web\u002FSKILL.md",[100,103],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[9,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,35,123,124,125,126],"sign in with google web","sign","with","web","android","go","security","google workspace","google cloud","implement","policy","python","implementing","react","iam","permissions","buttons","secure","identity","architectures","domain","runtimes",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":138,"publishedAt":52},"01M6998PHPDCAD684VW5WRG83D","dpop-adoption","Implement and debug OAuth 2.0 DPoP (RFC 9449) refresh token sender-constraining for WebCrypto, Node.js ES6, and browser runtimes integrating with Google's OAuth platform. Use when configuring non-extractable asymmetric key pairs (P-256), generating DPoP Proof JWTs for authorization code exchange and token refresh, or handling 400 use_dpop_nonce challenge retry loops at oauth2.googleapis.com\u002Ftoken. Don't use for unconstrained OAuth 2.0 flows (where refresh tokens are not bound to a client key pair), or for Google Cloud IAM \u002F service account authentication.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fdpop-adoption\u002FSKILL.md",[133,134,137],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[139,140,9,113,141,142,143,144,145,146,119,147,148,149,150,151,152,123,126,153,37],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","node","token","pair","platform",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":166,"publishedAt":52},"01M6998M72TC73EEAQH4XC7EXW","retrieving-developer-knowledge","Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI\u002FGemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fretrieving-developer-knowledge\u002FSKILL.md",[160,161,164,165],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[167,168,169,170,113,171,172,173,174,175,176,177,178,37,179,34,180,119,181,120],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","choice","documents","query","across","documentation",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":52},"01M6998J2CZEXS9BES9S3WWFKC","migrate-to-rust","Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a modern, high-performance, deterministic, 100% Safe Rust architecture, tracking live telemetry across every task bucket, test failure\u002Ffix cycle, and Profile-Guided Optimization (PGO) stage, and producing a first-person AI storytelling report and interactive HTML infographic. Use when migrating a GitHub repository or local codebase to Rust, porting legacy C++, Fortran, Python, or Java workloads to memory-safe Rust, designing Struct-of-Arrays (SoA) or SIMD Rust architectures, or optimizing Rust ports with LLVM PGO. Don't use for unrelated non-Rust refactoring or single-line syntax questions.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fmigrate-to-rust\u002FSKILL.md",[],[189,190,191,192,193,194,195,196,116,197,198,199,200,201,202,176,203,204,205,37,206,207,180,208],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":218,"publishedAt":52},"01M6998GCC3K29WZ82KXMB9E02","finding-google-skills","Google platform decision and setup guidance, loaded on demand from Google's skill catalog. Use when a developer is choosing or setting up part of their stack, such as where to run a service, a database, storage, messaging, authentication, analytics, ads, or AI model serving, and a Google product is a reasonable candidate - whether or not a vendor is named - or when a request names a Google product or API. Brings in the matching Google skill so the answer can weigh Google options, their trade-offs, and when they are not the right fit. Skip when the stack is already settled on another provider and no Google product is named, or the task involves no platform choice.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Ffinding-google-skills\u002FSKILL.md",[215,216,217],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[9,219,220,221,222,153,223,224,225,226,227,143,228,229,230,177,48,231,37,232,34],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","up","decision","database","candidate",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":241,"publishedAt":52},"01M6998DWNHTH0BS6W1CY8ZXMP","workload-manager-basics","Use this skill to manage Google Cloud Workload Manager evaluations, rules, scanned resources, and validation results by using public client libraries and the REST API. Use when you need to inspect workload best-practice rules, create and run evaluations for Google Cloud general best practices, SAP, SQL Server, or custom organizational rules, review violations, export results to BigQuery, or automate Workload Manager through client libraries because no service-specific public CLI or MCP server is available. Don't use for general Google Compute Engine instance management, VPC configuration, or standard IAM auditing.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fworkload-manager-basics\u002FSKILL.md",[239,240],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":135,"categoryName":136,"taxonomyType":21,"taxonomyTypeDesc":22},[242,243,35,244,9,170,245,113,171,246,247,248,249,37,250,34,119,251,50,252,253],"workload manager basics","workload","basics","cli","review","vpc","resources","inspect","you","create","server","run"]