What we're asking for: two related things on Google - (a) create and read conversion actions, and (b) create remarketing or customer-match user lists and target them on Search and Display campaigns.
Why this matters to us: without a conversion action there is no meaningful "website conversions" objective. We can only optimise campaigns forclicks, which means telling a customer that their campaign can't be optimised forthe thing they actually care about - form submissions and quote requests. Remarketing is the other half of the same
problem: re-reaching people who already visited is often the cheapest win available to a small advertiser, and we can't offer it.
What happens today: neither conversion actions nor user lists are exposed through your API, as far as we can tell. The Google Ads API provides both (ConversionActionService and UserListService, including customer-match lists with hashed identifiers).
What "done" looks like forus:
- create a conversion action and read its status, so we can tell the customer whether measurement is actually live
- create a remarketing or customer-match list and reference it in campaign targeting
- read back which audiences a campaign is targeting
All three capabilities from this request are now live on the API:
Conversion actions - Already fully working:
GET /v1/accounts/{accountId}/conversion-destinations to list conversion actions
POST /v1/accounts/{accountId}/conversion-destinations to create new ones
POST /v1/ads/conversions to send offline conversion events (up to 2K per batch)
POST /v1/ads/conversions/adjustments for retractions/restatements/enhancements
Customer-match audiences - Full lifecycle:
POST /v1/ads/audiences to create a customer-match list
GET /v1/ads/audiences to list all audiences
POST /v1/ads/audiences/{id}/users to upload emails (SHA256 hashed, 10K batch)
GET /v1/ads/audiences/{id} to read a single audience (live data from Google, including match rate and size)
PUT /v1/ads/audiences/{id} to update name, description, or membership status
DELETE /v1/ads/audiences/{id} to remove an audience
Campaign targeting with audiences - audienceInclude and audienceExclude now work for Google on create and update, so you can target or exclude your remarketing lists at the campaign level.
Log in to comment and vote
Comments1
Miquel Palet López
Sep 3
All three capabilities from this request are now live on the API:
Conversion actions - Already fully working:
GET /v1/accounts/{accountId}/conversion-destinationsto list conversion actionsPOST /v1/accounts/{accountId}/conversion-destinationsto create new onesPOST /v1/ads/conversionsto send offline conversion events (up to 2K per batch)POST /v1/ads/conversions/adjustmentsfor retractions/restatements/enhancementsCustomer-match audiences - Full lifecycle:
POST /v1/ads/audiencesto create a customer-match listGET /v1/ads/audiencesto list all audiencesPOST /v1/ads/audiences/{id}/usersto upload emails (SHA256 hashed, 10K batch)GET /v1/ads/audiences/{id}to read a single audience (live data from Google, including match rate and size)PUT /v1/ads/audiences/{id}to update name, description, or membership statusDELETE /v1/ads/audiences/{id}to remove an audienceCampaign targeting with audiences -
audienceIncludeandaudienceExcludenow work for Google on create and update, so you can target or exclude your remarketing lists at the campaign level.