Google Ads REST Interfaces struggle us so much.
zhang john
We're developing one Ads application based on Google Ads API.
Due to some technical reasons, it's difficult for us to use the Google Ads Client Library,
so we had to implement it by using the Google Ads REST interface.
Currently,we managed to mutate and search Campaign/Budget/AdGroup/Account via its REST Interface.
However, there are still some big questions struggling us.
1.Which fields are basic and required to create a common and simple Ads?
2.Which endpoint is provided to set the specific Audience-Dimension(Age/Gender/Area/Interest etc).
Great appreciate if someone could help us on them.
Google Ads API Forum Advisor
Hi John,
Thank you for reaching out to Google Ads API Forum. Please see responses to your questions below.
Which fields are basic and required to create a common and simple Ads?
- You may refer to this method (https://developers.google.com/google-ads/api/rest/reference/rest/v14/customers.adGroupAds/mutate) for creating ads in an ad group using the REST interface. This guide (https://developers.google.com/google-ads/api/rest/reference/rest/v14/AdGroupAd) contains the fields you may include in your request. Kindly utilize the API Explorer (https://developers.google.com/google-ads/api/rest/reference/rest/v14/customers.adGroupAds/mutate?apix=true) when customizing and validating your request body.
Which endpoint is provided to set the specific Audience-Dimension(Age/Gender/Area/Interest etc).
- You may check this guide (https://developers.google.com/google-ads/api/rest/reference/rest/v14/customers.audiences/mutate) for the endpoint when creating or updating audiences. Please check the JSON representation that can be found here (https://developers.google.com/google-ads/api/rest/reference/rest/v14/Audience) for the AudienceDimension object. For additional reference on audience management, you may check this API documentation (https://developers.google.com/google-ads/api/docs/remarketing/overview).
Please let us know if you have further questions.
Thanks,
 |
Google Ads API Team |
zhang john
2.I managed to create a basic Audience (that only contains Age/Gender/Household Income/Parental Status) customers/3869257274/audiences/89957000
How to create one advanced Audience that contains AudienceSegment?
Google Ads API Forum Advisor
Hi John,
For your first concern, I'm afraid that it would depend on your use-case as well as which type of campaign you're using. Kindly note that audience targeting is supported for performance max and discovery campaigns:
- Performance Max campaigns use an AssetGroupSignal <https://developers.google.com/google-ads/api/reference/rpc/v14/AssetGroupSignal> to target audiences.
- Discovery campaigns support adding audience ad group criterion with this process. This campaign uses AdGroupCriterion <https://developers.google.com/google-ads/api/reference/rpc/v14/AdGroupCriterion> to target audiences.
For creating an audience with audience segments, you would need to use the AudienceService <https://developers.google.com/google-ads/api/reference/rpc/v14/AudienceService> and specify your AudienceDimension <https://developers.google.com/google-ads/api/reference/rpc/v14/AudienceDimension> into AudienceSegmentDimension <https://developers.google.com/google-ads/api/reference/rpc/v14/AudienceSegmentDimension> with segments[] <https://developers.google.com/google-ads/api/reference/rpc/v14/AudienceSegment>.
Let us know if you have any clarifications.
zhang john
However, it got errors when I try to attach 'USER_INTEREST' and 'GENDER' to it.
Please check this two error responses from REST API.
--------------------------
{ "error": { "code": 400, "message": "Request contains an invalid argument.", "status": "INVALID_ARGUMENT", "details": [ { "@type": "type.googleapis.com/google.ads.googleads.v14.errors.GoogleAdsFailure", "errors": [ { "errorCode": { "criterionError": "INVALID_USER_INTEREST" }, "message": "Invalid user interest criterion.", "trigger": { "int64Value": "259" }, "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 }, { "fieldName": "create" }, { "fieldName": "user_interest" }, { "fieldName": "user_interest_category" } ] } } ], "requestId": "A_POyf23iGnRt6UMkWIpew" } ] } }
{ "error": { "code": 400, "message": "Request contains an invalid argument.", "status": "INVALID_ARGUMENT", "details": [ { "@type": "type.googleapis.com/google.ads.googleads.v14.errors.GoogleAdsFailure", "errors": [ { "errorCode": { "criterionError": "FIELD_INCOMPATIBLE_WITH_NEGATIVE_TARGETING" }, "message": "The field is not allowed to be set when the negative field is set to true, for example, we don't allow bids in negative ad group or campaign criteria.", "location": { "fieldPathElements": [ { "fieldName": "operations", "index": 0 }, { "fieldName": "create" }, { "fieldName": "gender" } ] } } ], "requestId": "KN8B8oZZ-M5KeeoE8J5ESQ" } ] } }
--------------------------
Best regards,
John
Google Ads API Forum Advisor
Hi John,
Thank you for getting back to us.
It appears that you have encountered criterion errors. With regards to "INVALID_USER_INTEREST" error, please note that as stated in this guide (see UserInterestInfo), when retrieving UserInterest to set in UserInterestInfo, verify the availabilities[] are compatible with the campaign type. Some UserInterest options are only available for specific campaign types. With this, kindly consider this recommendation before setting the USER_INTEREST.
Additionally, regarding the "FIELD_INCOMPATIBLE_WITH_NEGATIVE_TARGETING", this error indicates that the field is not allowed to be set when the negative field is set to true, for example, we don't allow bids in negative ad group or campaign criteria.
That said, could you provide us with the complete API logs (request and response with request-id and request header) generated on your end? This is so we could further investigate and provide more appropriate guidance.
If you haven't enabled the logging yet, for REST interface requests, you can enable logging via the curl command by using the -i flag.
Reference Links:
- request - https://developers.google.com/google-ads/api/docs/concepts/field-service#request
- response - https://developers.google.com/google-ads/api/docs/concepts/field-service#response
- request ID - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request-id
- request header - https://developers.google.com/google-ads/api/docs/concepts/call-structure#request_headers
zhang john
The request-id was already provided in my previous message. You can get it so easily if you read it carefully.
Best regards,
Google Ads API Forum Advisor
Hi John,
Thanks for getting back to us.
However, aside from the request-id, kindly note we will be needing the complete API logs (request and response with request-id and request header) in this format in order for us to check if there were any issues from your API request that caused the errors you encountered.
Reference links included in this email:
YETIC SAS
Google Ads API Forum Advisor
Hi,
Thank you for coming back to us and for providing additional information. I hope you are doing well today.
As mentioned before the error, FIELD_INCOMPATIBLE_WITH_NEGATIVE_TARGETING means that the field is not allowed to be set when the negative field is set to true, for example, we don't allow bids in negative ad group or campaign criteria. That being said, please note that if the ‘negative’ field is set as ‘false’, we are creating positive / standard keywords. Refer to the KeywordsInfo section in the Campaign Criteria documentation, which states you can only exclude keywords at the campaign level.
Thus, the API request call worked and created a negative keyword when the negative field was set to ‘TRUE’ and you received an error when the negative field was set to ‘FALSE’. The field is not allowed to be set when the negative field is set to true, e.g. we don't allow bids in negative Adgroup or campaigns like what I said earlier. Let me know if you have further questions.
In your case, since you didn’t set any, kindly note that if you are using the gender or userlist it needs to explicitly set "negative" to true. With that, could you please try to add “negative”: “true” on your query, like shown below?
"operations": [
{
"create": {
"campaign": "customers/9115134537/campaigns/20532740378",
“negative”: “true”,
"bid_modifier": 1,
"gender": {
"type": "MALE"
}
}
}
]
}
Let us know how it goes on your end.
Have a great day.