Skip to main content
Read audience evidence from the connected Google Ads account:
The equivalent REST request is:
MCP exposes erdo_list_paid_media_audiences with provider and customer_id. The native Google Ads action is get_google_ads_audience_readiness with customer_id. Omit the customer ID to use the connection’s selected operating account. A manager connection requires an accessible client customer ID. google_ads is the default and currently the only supported provider. All surfaces use the same provider reader. They do not create audiences, attach lists, change targeting, enable campaigns or increase spend.

​
Reading the result

Sizes, lifespan and eligibility can be null: an unknown estimate is not zero, and unknown eligibility is not false. population_state is collecting when Google reports prepopulation REQUESTED, populated when either reported size is positive, open_empty when both are zero on an open list, closed for a closed list, and unknown otherwise. An open empty list does not establish that new visits are reaching it. Membership lifespan is the provider field; rule-based list membership also depends on its rules. A GA4 tag on a page does not prove that a Google Ads retargeting list exists or is receiving visitors. Observation does not restrict reach to the audience. Even an enabled targeting attachment does not prove impressions were delivered: list eligibility, campaign configuration and actual delivery are separate facts. This read does not apply a universal audience-size serving threshold. The attachment inventory covers campaign and ad-group USER_LIST criteria, including exclusions. It does not inventory Performance Max audience signals, combined audiences or other criterion types. none is scoped to this inventory. The entire read has a 45-second budget, with at most 10 seconds per provider resource read. Partial failures remain in the response instead of turning into an empty successful inventory. Connection or account-resolution failures return an API error; inspect both the HTTP result and the response’s status/reads.

​
Shared-account privacy

The selected connection still controls which Google Ads customers can be read. Within a shared customer account, attachment queries are restricted to this organization’s owned campaigns. Account-wide user lists and recommendations are withheld because Erdo cannot prove audience ownership there. The result reports list_presence: unknown, never missing. List references on owned campaigns can be returned, but other tenants’ list names, sizes and eligibility are not fetched.

​
Customer Match capabilities

Google Ads v25 does not expose a customer field for the conversion-based customer-list opt-in or general Customer Match eligibility. Accepted customer data terms and per-list eligibility are different facts. This read cannot enable or verify the opt-in. Google documents the setting in the Google Ads interface: Admin → Account settings → Customer match → Conversion-based customer lists. See Google’s setup instructions and the v25 customer field reference. Google recommends Data Manager API for new Customer Match integrations. Its accountTypes.accounts.userLists.create creates the list, and audienceMembers.ingest uploads members to the destination list. These are separate operations, requiring the Data Manager OAuth scope and appropriate account access. Contact-based lists use ingestedUserListInfo with uploadKeyTypes: ["CONTACT_ID"] and first-party contactIdInfo; uploads carry consent, accepted Customer Match terms and correctly normalized/hashed identifiers. See Google’s recommendation, list creation, member ingestion, and Customer Match field mappings. Erdo’s existing native audience creator builds rule-based website lists. Its Data Manager integration handles conversion events, not Customer Match list creation or member ingestion. Those two approval-governed capabilities are not implemented by this read endpoint. There is no automatic opt-in toggle, Customer Match upload or audience attachment hidden in the readiness call.