data-manager-api-audience-ingestion
Guides developers through uploading audience members to Google products using the Data Manager API /v1/audienceMembers/ingest endpoint and its associated client libraries. Use this skill when the user wants to upload audience members 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).
- License 许可
- MIT
- 最近更新
- 2026-10-17
- Stars
- ★ 8
- Forks
- 1
01 前言 Front Matter
- name
- data-manager-api-audience-ingestion
- metadata
- { "version": 1.1, "category": "GoogleAds" }
- description
- Guides developers through uploading audience members to Google products using the Data Manager API /v1/audienceMembers/ingest endpoint and its associated client libraries. Use this skill when the user wants to upload audience members 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).
03 SKILL.md 正文
Data Manager API Audience 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, Display & Video 360, etc.) BEFORE generating any
code. Do not assume Google Ads by default. This maps to the
account_typefield of theoperating_accountin theDestination. - Read Documentation: [CRITICAL] Follow the upload guide for
your destination to implement the integration, as steps for configuring
and sending the request may vary between destinations:
- Google Ads Customer Match: Upload members to an audience
- DV360 Customer Match: Upload members to an audience
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_audience_members.py |
| Java | IngestAudienceMembers.java |
| PHP | ingest_audience_members.php |
| Node | ingest_audience_members.ts |
| .NET | IngestAudienceMembers.cs |
Step 3: Retrieve Migration Guides
[!CRITICAL] 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 Customer Match: Google Ads API to Customer Match Migration Field Mappings
Display & Video 360
- Display & Video 360 API Customer Match: Display & Video 360 API to Customer Match 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. - [ ] Format User Data: Use the utility library helpers to normalize and hash user identifiers correctly.
- [ ] Construct Payload: Build the request payload
(
IngestAudienceMembersRequest) containing the destinations, formatted members, and consent permissions. - [ ] Support Validation: Support sending the
validate_onlyboolean option on theIngestAudienceMembersRequestto allow developers to validate schemas without actually uploading data. - [ ] Send Request: Execute
ingest_audience_membersand record the returned request ID for logging/troubleshooting. - [ ] 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, queryclient.retrieve_request_statususing therequest_id. Skipping this step is a common user mistake.
Formatting
-
Fetch the Format user data guide and use that as the source of truth for formatting and normalization rules.
-
Use the utility library to format, hash, and encrypt user data (emails, phone numbers, addresses).
Python Example:
from google.ads.datamanager_util import Formatter from google.ads.datamanager_util.format import Encoding formatter: Formatter = Formatter() processed_email: str = formatter.process_email_address( email, Encoding.HEX )
Critical Gotchas
- Only set the
addressfield onUserIdentifierif all required fields (postal_code,family_name,given_name,region_code) are present; incompleteaddressfields will cause the API request to fail. product_destination_idmust be a numeric string. It is NOT a resource name.- The enum values for
ConsentStatusareCONSENT_GRANTEDandCONSENT_DENIED. Do not use the valuesGRANTEDandDENIED. - Field names on
UserIdentifierareemail_addressandphone_number. Do not use the Google Ads API field nameshashed_emailandhashed_phone_number. - Do not call the diagnostics endpoint (
retrieve_request_status) ifvalidate_onlyis set totrue.
Error Handling & Troubleshooting
Inspecting Error Payloads
[!IMPORTANT] Refer to Understand API Errors for a detailed guide on how to understand the structure of errors returned by the API.
Retrieving Request Status (Diagnostics)
Periodically poll for status using exponential backoff, starting at least
30 minutes after sending the IngestAudienceMembersRequest.
- Call
client.retrieve_request_statususingRetrieveRequestStatusRequest(request_id=...). - Loop through
request_status_per_destinationin the response to inspect each target'srequest_status. - If processing is complete and
request_statusisSUCCESS,PARTIAL_SUCCESS, orFAILED, inspect diagnostic values:- Audience Ingestion Status: Check the data-type-specific status
nested under
audience_members_ingestion_status(for example,composite_data_ingestion_status).- Record Count: Check
record_count(includes both success and failure). - Identifier Counts: Check the data-type-specific count field
(e.g.,
data_type_countsforcomposite_data_ingestion_statusoruser_identifier_countforuser_data_ingestion_status; see the Diagnostics Guide for other status types). - Match Rate Range: For
user_dataandcomposite_datauploads, checkupload_match_rate_range.
- Record Count: Check
- Error Details: If status is
FAILEDorPARTIAL_SUCCESS, inspect each error'sreasonandrecord_countundererror_info.error_counts. - Warning Details: Inspect each warning's
reasonandrecord_countunderwarning_info.warning_counts(even if the destination status isSUCCESS).
- Audience Ingestion Status: Check the data-type-specific status
nested under
API Reference
04 同仓库更多 Skills
security-audit
Comprehensive security guidance, source code audit, vulnerability assessment, and penetration test review for codebases, APIs, microservices, CLI tools, libraries, and LLM-backed applications. Triggers on requests to audit a codebase, conduct security reviews, find vulnerabilities or flaws, pen-test source code, or when the user asks in Arabic (فحص أمني، تدقيق الكود أمنياً، مراجعة الثغرات، فحص أمان المشروع). Supports Guidance mode (focused review) and Full Audit mode (deterministic 6-phase harness).
malware-analysis-reversing
Production malware analysis workflows, reverse engineering methodologies, isolated sandbox triage, static/dynamic binary analysis, memory forensics, and YARA detection rule authoring.
application-security-pentesting
Production Application Security (AppSec) standards, OWASP Top 10 vulnerability remediation, SAST/DAST pipeline integration, secure code review, threat modeling, and defensive security posture.
oauth2-oidc-security-flows
Implement enterprise OAuth 2.1 and OpenID Connect (OIDC) authorization code flow with Proof Key for Code Exchange (PKCE), state and nonce verification, refresh token rotation, token revocation, and centralized IdP federation (Keycloak, Auth0, Okta). Trigger when building secure authentication, single sign-on (SSO), or third-party delegated authorization.
jwt-session-management-hardening
Harden JWT-based authentication and session lifecycles using asymmetric signing (RS256/EdDSA), JWKS rotation, strict claims validation, Redis-backed sliding window sessions, revocation lists, and secure HttpOnly cookie storage. Trigger when implementing token validation, session revocation, or hardening API authentication.
soc2-compliance-automation
Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege, or CI/CD security gates.