Data Manager API Event Ingestion Guide
Helps developers implement Google event and conversion uploads through the Data Manager API.
The skill requires confirming the destination account type, describes destinations, authentication accounts, linked accounts, consent, validate_only, and asynchronous diagnostics, and directs users to format, hash, and encrypt user data. The main data-flow risks are therefore visible. Points are deducted because it does not explicitly require user confirmation before a real upload, nor explain retention, access control, revocation, rollback, external side effects, or dependency security in sufficient detail.
The workflow, field-specific gotchas, validate_only branch, request-status polling, and error diagnostics are reasonably coherent and provide some abnormal-result feedback. Points are deducted because there are no tests or executable key-path artifacts, only one short Python example, and behavior depends on external documentation and client versions; input-boundary and failure handling remain incomplete. Static calibration caps this at 10.
The scope clearly covers offline conversions, enhanced conversions, click conversions, Analytics events, and related ingestion cases, while excluding audience ingestion. It requires clarification when the destination is unspecified and lists sample entry points for several languages. Points are deducted because input/output contracts and non-fit boundaries remain brief, Chinese-language support is not stated, and the supplied material cannot establish reachability of core Google services and documentation from mainland-China networks.
The document is layered across prerequisites, use-case identification, samples, migration, implementation, formatting, gotchas, and troubleshooting. It includes version 1.1, Apache-2.0 licensing, official organizational provenance, installation context, and an issue-reporting path. Points are deducted for lacking a changelog, explicit maintenance owner or update commitment, FAQ coverage, complete examples, and for relying on another setup skill and external pages.
The skill can help developers structure a Data Manager API event-ingestion implementation and covers account configuration, request construction, validation, diagnostics, and common field errors. Points are deducted because it provides no end-to-end directly usable implementation or representative verified output; users must consult multiple external guides, choose a language, and supply business-specific and failure-handling logic. Static calibration caps this at 7.
The material names specific API references, migration, formatting, diagnostics, and error guides, links to official client samples, and supplies a fixed repository revision, creating useful audit trails. Points are deducted because no committed test suite, CI result, or third-party execution evidence is provided, and key claims depend on external documents not included in the source material. Static calibration caps this at 5.
- A real upload creates external data effects; before generating or running a non-validate_only request, confirm the target account, authorization scope, consent state, and data-processing responsibility.
- Correctness depends on current external Google documentation, client libraries, and utility libraries; verify version compatibility, field definitions, privacy compliance, and mainland-China network reachability before implementation.
- Rollback, duplicate-upload protection, secret management, retention, and end-to-end testing are not documented.
What does this skill do, and when should you use it?
This skill is for developers integrating the Data Manager API `/v1/events/ingest` endpoint for event and conversion ingestion. It covers offline conversions, enhanced conversions for leads, click conversions, and supported Google Analytics web or app events. The workflow starts by identifying the destination account type, then uses official documentation and language-specific samples to build the integration. It also covers data formatting, consent, validation-only requests, asynchronous diagnostics, and common payload mistakes.
It guides users to identify destinations such as Google Ads, Floodlight, or Google Analytics; retrieve the official event, formatting, error, and migration documentation; select a Python, Java, PHP, Node, or .NET sample; initialize IngestionServiceClient; construct Destination and IngestEventsRequest objects; format user identifiers; set consent and validate_only; call ingest_events and capture the request ID; then poll retrieve_request_status after at least 30 minutes to inspect success, partial success, failure, errors, and warnings.
- A developer migrating Google Ads offline conversion uploads to the Data Manager API.
- An advertising technology team sending enhanced lead conversions or click conversion events.
- An integration developer sending supported Google Analytics web or app events.
- An engineer migrating from Google Ads, Google Analytics Measurement Protocol, or Campaign Manager 360 APIs.
- A developer validating event schemas before uploading production data.
What are this skill's strengths and limitations?
- Covers multiple event and conversion ingestion scenarios while explicitly excluding audience-member uploads.
- Links official samples for Python, Java, PHP, Node, and .NET.
- Highlights asynchronous request diagnostics so HTTP 200 is not mistaken for processing success.
- Documents concrete pitfalls involving field names, timestamps, click identifiers, and consent enums.
- Relies on external official documentation, samples, and client or utility libraries; it does not include a complete runnable implementation.
- The source does not document costs, detailed permission setup, or every destination-specific event requirement.
- No test suite, scripts, or local validation environment is provided.
- Diagnostics are asynchronous and the guide recommends waiting at least 30 minutes before polling.
How do you install this skill?
Run npx skills add google/skills in a terminal, then select Data Manager API Event Ingestion from the repository. The source does not document additional parameters for installing only this skill or provide a separate runtime installation command.
How do you use this skill?
Ask an agent: "Help me ingest Google Ads offline conversion events with the Data Manager API. First confirm the destination account type, then implement it using the Python sample." If the destination is unspecified, the skill requires clarification before code generation. Authentication and client-library setup should be handled using the data-manager-api-setup skill.
How does this skill compare with similar options?
Compared with the repository's Data Manager API Audience Ingestion skill, this skill handles event and conversion records rather than audience-member uploads. Authentication and client-library installation are delegated to the Data Manager API Setup skill.