Associating sharedSet at the MCC level to campaigns in subaccounts

2024-02-26 Thread Amine Achergui
Hi,

I'm trying to share a negative keyword set from my MCC account to campaigns 
in sub-accounts using the Google Ads API. This use case  is doable through 
the UI, but I'm getting an Exception using Java sdk v15. Here is my code :

List resourceNames = new ArrayList<>();

CampaignSharedSet campaignSharedSet = CampaignSharedSet.newBuilder()
.setCampaign(campaignResourceName)
.setSharedSet(sharedSetResourceName)
.build();

CampaignSharedSetOperation campaignSharedSetOperation = 
CampaignSharedSetOperation.newBuilder()
.setCreate(campaignSharedSet)
.build();

try (CampaignSharedSetServiceClient campaignCriterionServiceClient = 
googleAdsClient.getLatestVersion().createCampaignSharedSetServiceClient()) {
MutateCampaignSharedSetsResponse response = 
campaignCriterionServiceClient.mutateCampaignSharedSets(
customerId, ImmutableList.of(campaignSharedSetOperation));
response.getResultsList().forEach(result -> 
resourceNames.add(result.getResourceName()));
}

and I am getting the following error:
Request
---
MethodName: 
google.ads.googleads.v15.services.CampaignSharedSetService/MutateCampaignSharedSets
...
Failure message: errors {
  error_code {
request_error: INVALID_CUSTOMER_ID
  }
  message: "Invalid customer ID 'X'."
}
...
Status: Status{code=INVALID_ARGUMENT, description=Request contains an 
invalid argument., cause=null}.
Where X is my MCC account.
What am I doing wrong? is That use case supported through the API ?

thank you,
Amine

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/3f2b333d-f64e-4ff6-a317-5eae5d7713bcn%40googlegroups.com.


Re: Callout assets visibility in Ads when created at Campaign level vs AdGroup level

2024-02-22 Thread Amine Achergui
Hi,

Thank you for your reply.

Currently, the code I have used is based on that and I have checked that 
the Assets are correctly linked to the AdGroups and the Campaign.
I think there has been a misunderstanding regarding the issue I'm facing. 
It's not about the linking of the assets per se, but rather their 
visibility within the Google Ads interface based on their level of 
association (campaign vs. ad group).

   - When the asset is linked to the campaign, in the Edit page of an Ad of 
   that campaign, the Asset is visible in the section More asset types.
   - When the asset is linked to the AdGroup, the Asset is not visible in 
   the in the section More asset types in the Edit page of an Ad within that 
   AdGroup.

I replicated this scenario using the Google Ads UI by creating two assets: 
one linked to an ad group and the other to a campaign. In line with my API 
experience, only the campaign-level asset was visible in the "More asset 
types" section on the ad edit page; the ad group-level asset was missing.


Thanks,

Amine

On Wednesday, February 21, 2024 at 6:00:56 PM UTC+1 Amine Achergui wrote:

> Hi team,
>
> I've encountered a puzzling situation with callout extensions not 
> consistently appearing in ad previews, and possibly affecting live ads as 
> well. I created a callout extension at the Campaign-Level, and 
> interestingly, even though it's still under review, it's visible in ad 
> previews for ads within its campaign's ad groups.
>
> However, when I introduce callout extensions at the Ad Group level. 
> Despite being correctly associated and sharing the same review status as 
> the campaign-level callout, these ad group-level callouts are absent in the 
> ad previews for ads within the same ad group.
>
> This discrepancy is concerning, especially since it could potentially 
> impact the performance of my ad extensions and overall ad results. I'm 
> curious to know why the campaign-level callout assets are visible, but the 
> ad group ones are not. my ad is of type ResponsiveSearchAd and I am using 
> the Java sdk v15.
> Thank you,
>
> Amine
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/6652541a-d9b8-402e-a44f-21962721d7c9n%40googlegroups.com.


Re: Callout assets visibility in Ads when created at Campaign level vs AdGroup level

2024-02-21 Thread Amine Achergui
Hi,

The problem also exists for other types of Assets like structured snippets .

Regards,
Amine

On Wednesday, February 21, 2024 at 6:00:56 PM UTC+1 Amine Achergui wrote:

> Hi team,
>
> I've encountered a puzzling situation with callout extensions not 
> consistently appearing in ad previews, and possibly affecting live ads as 
> well. I created a callout extension at the Campaign-Level, and 
> interestingly, even though it's still under review, it's visible in ad 
> previews for ads within its campaign's ad groups.
>
> However, when I introduce callout extensions at the Ad Group level. 
> Despite being correctly associated and sharing the same review status as 
> the campaign-level callout, these ad group-level callouts are absent in the 
> ad previews for ads within the same ad group.
>
> This discrepancy is concerning, especially since it could potentially 
> impact the performance of my ad extensions and overall ad results. I'm 
> curious to know why the campaign-level callout assets are visible, but the 
> ad group ones are not. my ad is of type ResponsiveSearchAd and I am using 
> the Java sdk v15.
> Thank you,
>
> Amine
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/f830772a-774b-475d-9089-fe42eea67092n%40googlegroups.com.


Callout assets visibility in Ads when created at Campaign level vs AdGroup level

2024-02-21 Thread Amine Achergui


Hi team,

I've encountered a puzzling situation with callout extensions not 
consistently appearing in ad previews, and possibly affecting live ads as 
well. I created a callout extension at the Campaign-Level, and 
interestingly, even though it's still under review, it's visible in ad 
previews for ads within its campaign's ad groups.

However, when I introduce callout extensions at the Ad Group level. Despite 
being correctly associated and sharing the same review status as the 
campaign-level callout, these ad group-level callouts are absent in the ad 
previews for ads within the same ad group.

This discrepancy is concerning, especially since it could potentially 
impact the performance of my ad extensions and overall ad results. I'm 
curious to know why the campaign-level callout assets are visible, but the 
ad group ones are not. my ad is of type ResponsiveSearchAd and I am using 
the Java sdk v15.
Thank you,

Amine

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/1e06a0ff-a390-4aa2-8023-12c5584146afn%40googlegroups.com.


Re: 429 errors are getting ridiculous

2023-12-26 Thread Amine Achergui
Hi Team,
Thank you for your answer.
With regards to  API Limits and Quotas
 I
haven't exceeded the daily limit any time but if there is a rate limit that
is expressed in terms of  requests per second or per minute, where can I
find it in the documentation?
Regards,
Amine

On Tue, Dec 26, 2023 at 9:40 PM Google Ads API Forum Advisor
 wrote:

> Hi,
>
> Thank you for getting back to us.
>
> By reviewing your query, I understand that you are getting the error "
> RESOURCE_EXHAUSTED
> ",
> it means that a system frequency limit has been exceeded. Kindly prevent
> sending too many requests in a short period of time and also ensure to set
> up short delays between requests or combine more operations in fewer
> requests. Also, please check this sample code for how to Handle a Rate
> Exceeded Error
> 
>  for
> more information.
>
> Additionally, we also have daily API operation limits where requests that
> violate these limits are rejected with the error: RESOURCE_EXHAUSTED. You
> may check out API Limits and Quotas
>  for
> more information.
>
> If you are still encountering an error, kindly provide us with the
> complete API logs (request
> 
>  and response
> 
>  with request-id
> 
>  and request header
> )
> generated at your end to assist you better.
>
> If you are using a client library and haven't enabled the logging yet, I
> would request you to enable logging for the specific client library that
> you are using. You can refer to the guides Java
> 
> , .Net
> 
> , PHP
> 
> , Python
> 
> , Ruby
> 
>  or Perl
>  
> to
> enable logging at your end. For REST interface requests, you can enable
> logging via the curl command by using the -i flag.
>
> You can send the details via *Reply privately to the author option*, or 
> *direct
> private reply* to this email.
>
>
> This message is in relation to case "ref:!00D1U01174p.!5004Q02r1p1V:ref"
>
> Thanks,
>
> [image: Google Logo] Google Ads API Team
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/CACpJVMTrC84hxeznpwrbZHij%3DQOwKR8165cicxiZ5qiuPOs9Gg%40mail.gmail.com.


Re: 429 errors are getting ridiculous

2023-12-26 Thread Amine Achergui
Hi Team,

Thank you for answer.

Here is an excerpt of the logs that produced 429.

Regards,

Amine

On Tuesday, December 26, 2023 at 5:27:59 AM UTC+1 Google Ads API Forum 
Advisor wrote:

Hi Amine,

Thank you for getting back to us.

I would like to inform you that the logs which you have provided are not in 
the correct format and are incomplete. In order to investigate further, 
kindly provide us with the updated complete API logs in .txt format (request 

 and response 

 with request-id 

 and request header 
)
 
generated at your end to assist you better.


If you are using a client library and haven't enabled the logging yet, I 
would request you to enable logging for the specific client library that 
you are using. You can refer to the guides Java 
, 
.Net 

, PHP 

, Python 

, Ruby 

 or Perl 
 to 
enable logging at your end. For REST interface requests, you can enable 
logging via the curl command by using the -i flag.

You can send the details via *Reply privately to the author option*, or *direct 
private reply* to this email.
  
This message is in relation to case "ref:!00D1U01174p.!5004Q02r1p1V:ref"

Thanks,
  [image: Google Logo] Google Ads API Team 

 

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/f101839e-ffbd-4b3d-97ab-af39da4830een%40googlegroups.com.
Request
---
MethodName: 
google.ads.googleads.v15.services.KeywordPlanIdeaService/GenerateKeywordIdeas
Endpoint: googleads.googleapis.com:443
Headers: {developer-token=REDACTED, login-customer-id=9386216798, 
x-goog-api-client=gl-java/17.0.6 gccl/28.0.0 gapic/28.0.0 gax/2.32.0 
grpc/1.56.1}
Body: customer_id: "9386216798"
url_seed {
  url: "https://redcapnow.com/electrical/co2-monitors;
}
keyword_plan_network: GOOGLE_SEARCH_AND_PARTNERS
language: "languageConstants/1000"
geo_target_constants: "geoTargetConstants/1023191"
keyword_annotation: KEYWORD_CONCEPT


Response

Headers: 
Metadata(content-type=application/grpc,request-id=ZTorUMG95WuNrtqGuV5aeQ,date=Mon,
 25 Dec 2023 16:59:17 GMT,alt-svc=h3=":443"; ma=2592000,h3-29=":443"; 
ma=2592000)
Body: null
Failure message: errors {
  error_code {
quota_error: RESOURCE_EXHAUSTED
  }
  message: "Too many requests. Retry in 1390 seconds."
  details {
quota_error_details {
  rate_scope: DEVELOPER
  rate_name: "Number of operations for basic access"
  retry_delay {
seconds: 1390
  }
}
  }
}
request_id: "ZTorUMG95WuNrtqGuV5aeQ"

Status: Status{code=RESOURCE_EXHAUSTED, description=Resource has been exhausted 
(e.g. check quota)., cause=null}.
2023-12-25 11:59:17.773 ERROR 235088 --- [ForkJoinPool.commonPool-worker-59] 
c.s.k.service.GoogleAdsKeywordService: Google Integration exception: 
Request ID - ZTorUMG95WuNrtqGuV5aeQ

com.google.ads.googleads.v15.errors.GoogleAdsException: errors {
  error_code {
quota_error: RESOURCE_EXHAUSTED
  }
  message: "Too many requests. Retry in 1390 seconds."
  details {
quota_error_details {
  rate_scope: DEVELOPER
  rate_name: "Number of operations for basic access"
  retry_delay {
seconds: 1390
  }
}
  }
}
request_id: "ZTorUMG95WuNrtqGuV5aeQ"