data-manager-api-event-ingestion

Ingest event and conversion data to Google Ads, Floodlight, and Google Analytics via the Data Manager API.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/wangx7/skills-collection --skill data-manager-api-event-ingestion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-manager-api-event-ingestion
Source: https://github.com/wangx7/skills-collection/tree/main/google-skills/skills/ads/data-manager-api/data-manager-api-event-ingestion
Command: npx skills add https://github.com/wangx7/skills-collection --skill data-manager-api-event-ingestion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually configuring and executing event and conversion uploads to Google products (Google Ads, Floodlight, Google Analytics) is time-consuming, error-prone, and requires deep expertise in API specifications, authentication flows, and strict data formatting rules. This Skill eliminates that friction by providing a structured, guided workflow for implementing compliant ingestion via the Data Manager API.

Core Features & Use Cases

  • End-to-End Guided Workflow: Step-by-step instructions for authentication, client library setup, destination configuration, and payload construction for the Data Manager API /v1/events/ingest endpoint.
  • Multi-Use Case Support: Covers offline conversions, enhanced conversions for leads, click conversions, Google Analytics web/app events, and migration from legacy Google APIs including Google Ads Offline Conversions, Measurement Protocol, and Campaign Manager 360 Offline Conversions.
  • Built-In Guardrails: Includes critical validation rules, formatting requirements, and troubleshooting guidance to avoid common API errors and ensure data compliance.
  • Use Case Example: A marketing operations specialist can use this Skill to upload 5,000 offline in-store purchase conversions to Google Ads without manually handling user data hashing, RFC 3339 timestamp formatting, or API request construction.

Quick Start

Use the data-manager-api-event-ingestion skill to upload your latest batch of offline Google Ads conversions from the Q3 sales CSV file.

Frequently Asked Questions about data-manager-api-event-ingestion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload offline conversions to Google Ads using the Data Manager API?

Uploading offline conversions to Google Ads via the Data Manager API involves configuring authentication, installing client libraries, formatting user data, and sending a valid payload to the /v1/events/ingest endpoint for accurate conversion tracking.

What is the best way to migrate legacy Google Ads conversion uploads to the Data Manager API?

Migrating legacy Google Ads conversion uploads to the Data Manager API requires routing requests through the /v1/events/ingest endpoint, replacing legacy Google Ads Offline Conversions and Campaign Manager 360 APIs with a unified workflow for event ingestion.

How does enhanced conversions for leads data hashing work for Google Analytics event ingestion?

Enhanced conversions for leads data hashing requires formatting user data according to strict API specifications before Google Analytics event ingestion. Proper hashing and RFC 3339 timestamp formatting via the Data Manager API ensure data compliance and prevent common API errors.

Can I use the Data Manager API to ingest both Google Analytics web events and Floodlight click conversions?

Yes, the Data Manager API supports ingesting both Google Analytics web events and Floodlight click conversions through the /v1/events/ingest endpoint, allowing multi-use case event ingestion alongside offline conversion uploads and enhanced conversions for leads.

Why does my Google Ads offline conversion upload fail API validation?

Google Ads offline conversion uploads fail API validation due to incorrect user data formatting, missing authentication setup, or malformed request payloads. Applying built-in validation rules and proper data hashing before event ingestion prevents these common API errors.