data-manager-api-event-ingestion
Guides developers through implementing event and conversion ingestion to Google products using the Data Manager API /v1/events/ingest 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 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add google/skills --skill data-manager-api-event-ingestion技能说明
name: data-manager-api-event-ingestion description: >- Guides developers through implementing event and conversion ingestion to Google products using the Data Manager API /v1/events/ingest 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). metadata: version: 1.1 category: GoogleAds
Data Manager API Event 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-setupskill.
Step 1: Identify Use Case & Read Documentation
- Determine Destination Account Type: [CRITICAL] If it's not
explicitly stated, STOP and CLARIFY with the user where the data is being
sent (e.g., Google Ads, Floodlight, Google Analytics)
BEFORE generating any code. Do not assume Google Ads by default. This maps
to the
account_typefield of theoperating_accountin theDestination, and also determines valid event identifiers and requirements. - Read Documentation: [CRITICAL] Follow the Send events guide to implement the integration, as steps for configuring and sending the request may vary between destinations.
Step 2: Retrieve Code Sample
[!IMPORTANT] If writing or updating an ingestion script, ALWAYS retrieve the relevant code sample to use as a reference:
| Language | Sample |
|---|---|
| Python | ingest_events.py |
| Java | IngestEvents.java |
| PHP | ingest_events.php |
| Node | ingest_events.ts |
| .NET | IngestEvents.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
- Google Ads API Offline Conversions: Google Ads Offline Conversions Migration Field Mappings
- Google Ads API Store Sales: Google Ads Store Sales Migration Field Mappings
Google Analytics
- Measurement Protocol (Google Analytics): Google Analytics Measurement Protocol Migration Field Mappings
Campaign Manager 360 (CM360)
- Campaign Manager 360 API Offline Conversions: Campaign Manager 360 Offline Conversions Migration Field Mappings
Step 4: Implementation
Implement the ingestion logic using the following checkpoints:
- Initialize Client: Instantiate the Data Manager client
(
IngestionServiceClient). - Define Destinations: Build the
Destinationobject using theproduct_destination_idand the appropriate account configurations:operating_account(target account receiving data),login_account(if authenticating using a manager account or a data partner account), andlinked_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. - Prepare Event Data: Use the utility library helpers to format and normalize user identifiers correctly.
- Construct Payload: Build the request payload
(
IngestEventsRequest) containing the destinations, event records, and consent permissions. - Support Validation: Support sending the
validate_onlyboolean option on theIngestEventsRequestto allow developers to validate schemas without actually uploading data. - Send Request: Execute
ingest_eventsand record the returnedrequest_idfor later diagnostics. - Check for Ingestion Warnings: If any non-required field had a
validation failure, the response from
ingest_eventswill also includefield_warnings, a list ofFieldWarningobjects detailing the issues. - Retrieve Request Status: Check the status of the ingestion request
using diagnostics. Since request processing is asynchronous, a
successful ingestion response (HTTP 200 OK returning a
request_id) only indicates the payload was received. To check if the records actually succeeded, partially succeeded, or failed to process, query theclient.retrieve_request_statusendpoint using therequest_id. Skipping this step is a common user mistake.
Formatting
- Fetch the Format user data guide and use th