[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698X4WCRBW353DWE3EPV3DF":3,"skill-same:01M698X4WCRBW353DWE3EPV3DF":85},{"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":34,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M698X4WCRBW353DWE3EPV3DF","data-manager-api-event-ingestion",null,"Guides developers through implementing event and conversion ingestion to Google products using the Data Manager API \u002Fv1\u002Fevents\u002Fingest endpoint and its associated client libraries. Use this skill when the user wants to upload offline conversions, enhanced conversions for leads, click conversions, Google Analytics web or app events, or any other event ingestion use case supported by the Data Manager API. Don't use for uploading audience members (use the data-manager-api-audience-ingestion skill).","google\u002Fskills","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698WR0H76ENHE587T9EJT89",24122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fads\u002Fdata-manager-api-event-ingestion\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师",[35,36,37,38,39,40,41,9,42,43,44,45,46,47,48,49,50,51,52,53],"data manager api event ingestion","manager","data","event","api","ingestion","when","implementing","leads","guides","events","click","app","conversion","endpoint","google analytics","offline","libraries","analytics","2026-11-10 10:12:30",false,"---\nname: data-manager-api-event-ingestion\ndescription: >-\n  Guides developers through implementing event and conversion ingestion to\n  Google products using the Data Manager API \u002Fv1\u002Fevents\u002Fingest endpoint\n  and its associated client libraries. Use this skill when the user wants to upload\n  offline conversions, enhanced conversions for leads, click conversions, Google\n  Analytics web or app events, or any other event ingestion use case supported by\n  the Data Manager API. Don't use for uploading audience members (use the\n  data-manager-api-audience-ingestion skill).\nmetadata:\n  version: \"1.2.0\"\n  category: GoogleAds\n---\n# Data Manager API Event 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\n### Step 1: Identify Use Case & Read Documentation\n\n-   **Determine Destination Account Type**: [CRITICAL] If it can't be determined\n    from the user's context, consider clarifying which destination events are\n    being ingested to before generating any code. This maps to the\n    `account_type` field of the `operating_account` in the `Destination`,\n    and also determines valid event identifiers and requirements.\n-   **Identify User Intent**:\n    -   **Implementing ingestion code**: Follow the relevant\n        implementation guide for the destination and use case in the\n        **Implementation guide** column below. This is critical to ensure field\n        requirements are met and destinations are correctly configured.\n    -   **Checking request status or inspecting errors**: Refer to the\n        [Error Handling & Troubleshooting](#error-handling-troubleshooting)\n        section below.\n    -   **Migrating from another Google API**: Refer to\n        [Step 3: Retrieve Migration Guides](#step-3-retrieve-migration-guides)\n        below to extract the full contents of the relevant field mapping guide.\n\n| Destination (`operating_account.account_type`) | Use case | Implementation guide |\n| :--- | :--- | :--- |\n| **Google Ads** (`GOOGLE_ADS`) | Offline conversions, enhanced conversions for leads | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Foffline\u002Fsend-events.md.txt) |\n| **Google Ads** (`GOOGLE_ADS`) | Multi-source conversions supplementing the Google tag | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Fonline\u002Fsend-events.md.txt) |\n| **Google Ads** (`GOOGLE_ADS`) | Store sales conversions | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Fstore-sales\u002Fsend-events.md.txt) |\n| **Google Analytics** (`GOOGLE_ANALYTICS_PROPERTY`) | Recommended and custom GA4 events | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fanalytics\u002Frecommended-custom-events\u002Fsend-events.md.txt) |\n| **Google Analytics** (`GOOGLE_ANALYTICS_PROPERTY`) | Multi-source events with a transaction ID | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fanalytics\u002Fonline\u002Fsend-events.md.txt) |\n| **Floodlight** (`FLOODLIGHT_CONFIG`) | Floodlight offline conversions | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fcm360\u002Foffline\u002Fsend-events.md.txt) |\n| **Floodlight** (`FLOODLIGHT_CONFIG`) | Multi-source conversions supplementing the Google or Floodlight tag | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fcm360\u002Fonline\u002Fsend-events.md.txt) |\n\nIf the request doesn't match any row, fetch the\n[Events overview](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents.md.txt)\nto find the right guide rather than guessing.\n\n### Step 2: Retrieve Code Sample\n\n> [!IMPORTANT]\n> 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_events.py`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-python\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.py) |\n| **Java** | [`IngestEvents.java`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-java\u002Fblob\u002Fmain\u002Fdata-manager-samples\u002Fsrc\u002Fmain\u002Fjava\u002Fcom\u002Fgoogle\u002Fads\u002Fdatamanager\u002Fsamples\u002FIngestEvents.java) |\n| **PHP** | [`ingest_events.php`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-php\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.php) |\n| **Node** | [`ingest_events.ts`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-node\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.ts) |\n| **.NET**| [`IngestEvents.cs`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-dotnet\u002Fblob\u002Fmain\u002Fsamples\u002FIngestEvents.cs) |\n\n### Step 3: Retrieve Migration Guides\n\n> [!IMPORTANT]\n> 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*   **Offline conversions, enhanced conversions for leads** (migrating from the Google Ads API):\n    [Google Ads Offline Conversions Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Foffline\u002Fupgrade\u002Ffield-mappings.md.txt)\n*   **Store sales conversions** (migrating from the Google Ads API):\n    [Google Ads Store Sales Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Fstore-sales\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Google Analytics\n\n*   **Recommended and custom GA4 events** (migrating from the Google Analytics Measurement Protocol):\n    [Google Analytics Measurement Protocol Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fanalytics\u002Fmeasurement-protocol\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Floodlight\n\n*   **Floodlight offline conversions** (migrating from the Campaign Manager 360 API):\n    [Campaign Manager 360 Offline Conversions Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fcm360\u002Foffline\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-   [ ] **Prepare Event Data**: Use the utility library helpers to format and\n    normalize user identifiers correctly.\n-   [ ] **Construct Payload**: Build the request payload\n    (`IngestEventsRequest`) containing the destinations, event records, and\n    consent permissions.\n-   [ ] **Support Validation**: Support sending the `validate_only` boolean\n    option on the `IngestEventsRequest` to allow developers to validate schemas\n    without actually uploading data.\n-   [ ] **Send Request**: Execute `ingest_events` and record the returned\n    `request_id` for later diagnostics.\n-   [ ] **Check for Ingestion Warnings**: If any non-required field had a\n    validation failure, the response from `ingest_events` 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\n    successful ingestion response (HTTP 200 OK returning a `request_id`) only\n    indicates the payload was received. To check if the records actually\n    succeeded, partially succeeded, or failed to process, query the\n    `client.retrieve_request_status` endpoint using the `request_id`. Skipping\n    this step is a common user mistake.\n\n## Formatting\n\n*   Fetch the [Format user data](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Fformatting.md.txt)\n    guide and use that as the source of truth for formatting and\n    normalization rules.\n\n*   Use the utility library to format, hash, and encrypt user data\n    (emails, phone numbers, addresses).\n\n    **Python Example:**\n\n    ```python\n    from google.ads.datamanager_util import Formatter\n    from google.ads.datamanager_util.format import Encoding\n\n    formatter: Formatter = Formatter()\n\n    processed_email: str = formatter.process_email_address(\n        email, Encoding.HEX\n    )\n    ```\n\n## Critical Gotchas\n\n*   Format `product_destination_id` as a numeric string. It is NOT a resource\n    name path.\n*   Format `event_timestamp` strictly in RFC 3339 format. Use the SDK's typed\n    timestamp object instead of a raw string where available.\n*   Nest click identifiers (`gclid`, `gbraid`, `wbraid`) inside the\n    `ad_identifiers` block, not directly on the base event payload.\n*   The enum values for `ConsentStatus` are `CONSENT_GRANTED` and\n    `CONSENT_DENIED`. Do not use the values `GRANTED` and `DENIED`.\n*   Note that `consent` can be set globally on the `IngestEventsRequest` or on\n    individual `Event`s.\n*   Verify that `UserIdentifier` uses `email_address` and `phone_number`.\n    Do not use the Google Ads API fields `hashed_email` and\n    `hashed_phone_number`.\n*   Ensure the currency field on the event is named `currency`, not\n    `currency_code`.\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\n30 minutes after sending the `IngestEventsRequest`.\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    *   **Event Record Counts**: Check `events_ingestion_status.record_count`\n        (includes both success and failure).\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*   [REST API Reference](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002Fevents\u002Fingest.md.txt)\n*   [Diagnostics Guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fdiagnostics.md.txt)\n","# Data Manager API Event 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\n### Step 1: Identify Use Case & Read Documentation\n\n-   **Determine Destination Account Type**: [CRITICAL] If it can't be determined\n    from the user's context, consider clarifying which destination events are\n    being ingested to before generating any code. This maps to the\n    `account_type` field of the `operating_account` in the `Destination`,\n    and also determines valid event identifiers and requirements.\n-   **Identify User Intent**:\n    -   **Implementing ingestion code**: Follow the relevant\n        implementation guide for the destination and use case in the\n        **Implementation guide** column below. This is critical to ensure field\n        requirements are met and destinations are correctly configured.\n    -   **Checking request status or inspecting errors**: Refer to the\n        [Error Handling & Troubleshooting](#error-handling-troubleshooting)\n        section below.\n    -   **Migrating from another Google API**: Refer to\n        [Step 3: Retrieve Migration Guides](#step-3-retrieve-migration-guides)\n        below to extract the full contents of the relevant field mapping guide.\n\n| Destination (`operating_account.account_type`) | Use case | Implementation guide |\n| :--- | :--- | :--- |\n| **Google Ads** (`GOOGLE_ADS`) | Offline conversions, enhanced conversions for leads | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Foffline\u002Fsend-events.md.txt) |\n| **Google Ads** (`GOOGLE_ADS`) | Multi-source conversions supplementing the Google tag | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Fonline\u002Fsend-events.md.txt) |\n| **Google Ads** (`GOOGLE_ADS`) | Store sales conversions | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Fstore-sales\u002Fsend-events.md.txt) |\n| **Google Analytics** (`GOOGLE_ANALYTICS_PROPERTY`) | Recommended and custom GA4 events | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fanalytics\u002Frecommended-custom-events\u002Fsend-events.md.txt) |\n| **Google Analytics** (`GOOGLE_ANALYTICS_PROPERTY`) | Multi-source events with a transaction ID | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fanalytics\u002Fonline\u002Fsend-events.md.txt) |\n| **Floodlight** (`FLOODLIGHT_CONFIG`) | Floodlight offline conversions | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fcm360\u002Foffline\u002Fsend-events.md.txt) |\n| **Floodlight** (`FLOODLIGHT_CONFIG`) | Multi-source conversions supplementing the Google or Floodlight tag | [Send events](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fcm360\u002Fonline\u002Fsend-events.md.txt) |\n\nIf the request doesn't match any row, fetch the\n[Events overview](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents.md.txt)\nto find the right guide rather than guessing.\n\n### Step 2: Retrieve Code Sample\n\n> [!IMPORTANT]\n> 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_events.py`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-python\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.py) |\n| **Java** | [`IngestEvents.java`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-java\u002Fblob\u002Fmain\u002Fdata-manager-samples\u002Fsrc\u002Fmain\u002Fjava\u002Fcom\u002Fgoogle\u002Fads\u002Fdatamanager\u002Fsamples\u002FIngestEvents.java) |\n| **PHP** | [`ingest_events.php`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-php\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.php) |\n| **Node** | [`ingest_events.ts`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-node\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.ts) |\n| **.NET**| [`IngestEvents.cs`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-dotnet\u002Fblob\u002Fmain\u002Fsamples\u002FIngestEvents.cs) |\n\n### Step 3: Retrieve Migration Guides\n\n> [!IMPORTANT]\n> 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*   **Offline conversions, enhanced conversions for leads** (migrating from the Google Ads API):\n    [Google Ads Offline Conversions Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Foffline\u002Fupgrade\u002Ffield-mappings.md.txt)\n*   **Store sales conversions** (migrating from the Google Ads API):\n    [Google Ads Store Sales Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Fstore-sales\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Google Analytics\n\n*   **Recommended and custom GA4 events** (migrating from the Google Analytics Measurement Protocol):\n    [Google Analytics Measurement Protocol Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fanalytics\u002Fmeasurement-protocol\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Floodlight\n\n*   **Floodlight offline conversions** (migrating from the Campaign Manager 360 API):\n    [Campaign Manager 360 Offline Conversions Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fcm360\u002Foffline\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-   [ ] **Prepare Event Data**: Use the utility library helpers to format and\n    normalize user identifiers correctly.\n-   [ ] **Construct Payload**: Build the request payload\n    (`IngestEventsRequest`) containing the destinations, event records, and\n    consent permissions.\n-   [ ] **Support Validation**: Support sending the `validate_only` boolean\n    option on the `IngestEventsRequest` to allow developers to validate schemas\n    without actually uploading data.\n-   [ ] **Send Request**: Execute `ingest_events` and record the returned\n    `request_id` for later diagnostics.\n-   [ ] **Check for Ingestion Warnings**: If any non-required field had a\n    validation failure, the response from `ingest_events` 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\n    successful ingestion response (HTTP 200 OK returning a `request_id`) only\n    indicates the payload was received. To check if the records actually\n    succeeded, partially succeeded, or failed to process, query the\n    `client.retrieve_request_status` endpoint using the `request_id`. Skipping\n    this step is a common user mistake.\n\n## Formatting\n\n*   Fetch the [Format user data](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Fformatting.md.txt)\n    guide and use that as the source of truth for formatting and\n    normalization rules.\n\n*   Use the utility library to format, hash, and encrypt user data\n    (emails, phone numbers, addresses).\n\n    **Python Example:**\n\n    ```python\n    from google.ads.datamanager_util import Formatter\n    from google.ads.datamanager_util.format import Encoding\n\n    formatter: Formatter = Formatter()\n\n    processed_email: str = formatter.process_email_address(\n        email, Encoding.HEX\n    )\n    ```\n\n## Critical Gotchas\n\n*   Format `product_destination_id` as a numeric string. It is NOT a resource\n    name path.\n*   Format `event_timestamp` strictly in RFC 3339 format. Use the SDK's typed\n    timestamp object instead of a raw string where available.\n*   Nest click identifiers (`gclid`, `gbraid`, `wbraid`) inside the\n    `ad_identifiers` block, not directly on the base event payload.\n*   The enum values for `ConsentStatus` are `CONSENT_GRANTED` and\n    `CONSENT_DENIED`. Do not use the values `GRANTED` and `DENIED`.\n*   Note that `consent` can be set globally on the `IngestEventsRequest` or on\n    individual `Event`s.\n*   Verify that `UserIdentifier` uses `email_address` and `phone_number`.\n    Do not use the Google Ads API fields `hashed_email` and\n    `hashed_phone_number`.\n*   Ensure the currency field on the event is named `currency`, not\n    `currency_code`.\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\n30 minutes after sending the `IngestEventsRequest`.\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    *   **Event Record Counts**: Check `events_ingestion_status.record_count`\n        (includes both success and failure).\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*   [REST API Reference](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002Fevents\u002Fingest.md.txt)\n*   [Diagnostics Guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fdiagnostics.md.txt)\n",{"name":5,"metadata":59,"description":7},{"version":60,"category":61},"1.2.0","GoogleAds","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fads\u002Fdata-manager-api-event-ingestion",2005,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 01:51:35",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add google\u002Fskills --skill data-manager-api-event-ingestion",{"tool":77,"command":78},"bunx","bunx skills add google\u002Fskills --skill data-manager-api-event-ingestion",{"tool":80,"command":81},"pnpm","pnpm dlx skills add google\u002Fskills --skill data-manager-api-event-ingestion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fads\u002Fdata-manager-api-event-ingestion\u002FSKILL.md",true,[],[86,118,145,173,200,225],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":96,"publishedAt":54},"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",[92,95],{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[9,97,98,99,100,101,102,103,104,105,106,107,108,42,109,110,111,112,113,36,114,115,116,117],"sign in with google web","sign","with","web","android","go","security","google workspace","google cloud","implement","policy","python","react","iam","permissions","buttons","secure","identity","architectures","domain","runtimes",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":54},"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",[124,125,128],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[130,131,9,105,132,133,134,135,136,137,110,138,139,140,141,142,143,114,117,144,41],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","node","token","pair","platform",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":157,"publishedAt":54},"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",[151,152,155,156],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[158,159,160,161,105,162,163,164,165,166,167,168,169,41,170,39,171,110,172,111],"retrieving developer knowledge","knowledge","developer","MCP","mcp server","official","developer documentation","get","search","local","choice","documents","query","across","documentation",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":54},"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",[],[180,181,182,183,184,185,186,187,108,188,189,190,191,192,193,167,194,195,196,41,197,198,171,199],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":209,"publishedAt":54},"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",[206,207,208],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[9,210,211,212,213,144,214,215,216,217,218,134,219,220,221,168,222,223,41,224,39],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","up","decision","use","database","candidate",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":233,"publishedAt":54},"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",[231,232],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},[234,235,36,236,9,161,237,105,162,238,239,240,241,41,242,39,110,243,52,244,245],"workload manager basics","workload","basics","cli","review","vpc","resources","inspect","you","create","server","run"]