Clarification on Custom Audience Type Mapping Between UI and API

32 views
Skip to first unread message

Amit Tomar

unread,
Jul 24, 2025, 1:51:18 PM7/24/25
to Google Ads API and AdWords API Forum

Hi Team,

I’m working on creating Custom Audiences using the API (CustomAudienceOperation).
I noticed that while creating a custom segment via the UI, there are two options:

  1. People with any of these interests or purchase intentions

  2. People who searched for any of these terms on Google

At the API level, we have the following CustomAudienceType enums:
AUTO, INTEREST, PURCHASE_INTENT, and SEARCH.

Could you please help clarify how these UI options map to the respective enum values in the API?
Also, under what scenarios should each enum type be used?

Thank you

Screenshot from 2025-07-24 23-10-59.png
Screenshot from 2025-07-24 23-09-15.png

Google Ads API Forum Advisor

unread,
Jul 24, 2025, 6:19:30 PM7/24/25
to amittomar...@gmail.com, adwor...@googlegroups.com
Hi,

Thank you for contacting the Google Ads API support team.

I understand you're working with the Google Ads API for Custom Audiences and seeking clarification on how the UI options map the CustomAudienceType enum values.​ The UI option "People with any of these interests or purchase intentions" corresponds to "INTEREST" and "PURCHASE_INTENT" in the API and the option "People who searched for any of these terms on Google" directly corresponds to "SEARCH" enum in the API. Kindly note that for the CustomAudienceType "INTEREST" OR "PURCHASE_INTENT" is not allowed for newly created custom audiences but kept for existing audiences. Hence, I would recommend using  the option "AUTO" and then Google Ads will auto-select the best interpretation at serving time.​

I hope this clarifies your issue. Please feel free to reach out to us for further queries related to Google Ads API.
 

Thanks,
 
Google Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-07-24 22:18:45Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01swhWK:ref" (ADR-00320128)



Reply all
Reply to author
Forward
0 new messages