Re: how to get household income data

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

HI Hari,

Could you kindly respond to this thread privately and share with me one or 
more campaign IDs so I can take a look?

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Thursday, December 13, 2018 at 12:33:55 AM UTC-5, Harisankar Mohanty 
wrote:
>
> Hello Sir,
>
> But in our cases criteria are set for age range , income range etc .. 
> still then we are not getting info using criteraType as 'AGE_RANGE', 
> 'INCOME_RANGE' in campaigncriterionservice ..
>
> On Thu, 13 Dec 2018 at 4:57 AM 'Anash P. Oommen (AdWords API Team)' via 
> AdWords API and Google Ads API Forum  wrote:
>
>> Hi Harisankar,
>>
>> Demographic criteria like INCOME_RANGE, AGE_RANGE, GENDER are criteria 
>> that are enabled by default for all audience, so we don't explicitly add 
>> these criteria in a campaign. These criteria appear in a campaign only when 
>> you explicitly do something with those critieria (e.g. add a negative age 
>> range criteria, or apply a bid adjustment to a specific gender).
>>
>> E.g. if you can't retrieve Gender criteria for a campaign, you should 
>> interpret it as "there's no special gender criteria for this campaign, so 
>> it is serving to GENDER_MALE, GENDER_FEMALE and GENDER_UNDETERMINED).
>>
>> Hope this helps? Let me know if you have more questions.
>>
>> Cheers
>> Anash P. Oommen,
>> AdWords API Advisor.
>>
>> On Saturday, December 8, 2018 at 4:07:12 PM UTC-5, Harisankar Mohanty 
>> wrote:
>>>
>>> Hello API Team,
>>>
>>> I am using Google Adwords API version : v201806 (PHP) to develop a web 
>>> app.
>>>
>>> I am struck somewhere to retrieve Household Income Tier for a particular 
>>> Campaign. Though I am getting info for criteria type 'LOCATION' but other 
>>> criteria type does not work for me like 'INCOME_RANGE' or 'AGE_RANGE' etc. 
>>> I have posted my code below. Can you please check and let me know why I am 
>>> not getting data for Household Income Tier when I use criteria type 
>>> 'INCOME_RANGE' ?
>>>
>>> public static function runExample (
>>> AdWordsServices $adWordsServices,
>>> //AdWordsSession $session
>>> AdWordsSessionBuilder $sessionBuilder,
>>> $customerId, $campaignId = null, $locationIds = null, 
>>> $criteriaType = null
>>> ) {
>>> 
>>> $session = 
>>> $sessionBuilder->withClientCustomerId($customerId)->build();
>>> $campaignCriterionService = $adWordsServices->get($session, 
>>> CampaignCriterionService::class);
>>>
>>> $selector = new Selector();
>>> 
>>> $selector->setFields(array('Id','CampaignId','MatchingFunction','LocationName','Address'));
>>> $predicates[] = new Predicate('CampaignId', 
>>> PredicateOperator::IN, array($campaignId));
>>> //$predicates[] = new Predicate('CriteriaType', 
>>> PredicateOperator::IN,  array('AD_GROUPS'));
>>> $predicates[] = new Predicate('CriteriaType', PredicateOperator::IN,  
>>> array($criteriaType));
>>> 
>>> $selector->setPredicates($predicates);
>>> 
>>> $startIndex = 0;
>>> 
>>> $selector->setPaging(new Paging($startIndex, 10));
>>> echo "";
>>> print_r($selector);
>>> 
>>> do {
>>> // Make the get request.
>>> $page = $campaignCriterionService->get($selector);
>>> 
>>> echo "";
>>> print_r($page);
>>> die();
>>>
>>> // Display results.
>>> if (!empty($page->getEntries())) {
>>> //return $page->entries;
>>> $return['data'] = $page->getEntries();
>>> 
>>> 
>>> 
>>>   foreach ($page->getEntries() as $campaignCriterion) {  
>>>   
>>> 
>>> if(in_array($campaignCriterion->getCriterion()->matchingFunction->rhsOperand[0]->locations[0],
>>>  
>>> $locationIds)) {
>>> 
>>> $locations[$campaignCriterion->criterion->id]['location'] = 
>>> $campaignCriterion->criterion->matchingFunction->rhsOperand[0]->locations[0];
>>> 
>>> $locations[$campaignCriterion->criterion->id][

Re: ClickAssistedConversionValue and ImpressionAssistedConversionValue now contain "--"?!

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Alexander, Zwitze,

This is a planned change from our end, see our blog post about this 
change: 
https://ads-developers.googleblog.com/2018/08/deprecation-of-assisted-conversions.html

Let me know if you have more questions regarding this change.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Wednesday, December 12, 2018 at 1:58:13 PM UTC-5, Alexander wrote:
>
> Same problem. We quick fixed it yesterday on our end to interpret "--" as 
> zero. 
>
> Is it sufficient to click the "Me too!" button in a forum thread? Or is it 
> better to post a message?
>
> On Wednesday, December 12, 2018 at 10:29:52 AM UTC+1, Zweitze wrote:
>>
>> I also want to add that this morning, over 50% of our jobs failed - all 
>> on this error.
>>
>>
>>
>> On Wednesday, December 12, 2018 at 9:21:07 AM UTC+1, Zweitze wrote:
>>>
>>> Indeed, my concern is that those fields now contain '--'.
>>> That change breaks our software.
>>>
>>>
>>> On Tuesday, December 11, 2018 at 6:18:24 PM UTC+1, Teja Makani wrote:

 Hello,

 Could you confirm whether your concern is regarding the '--' values of 
 those fields? If your concern is different please elaborate.

 Regards,
 Sai Teja, AdWords API Team

 On Tuesday, December 11, 2018 at 5:39:36 AM UTC-5, Zweitze wrote:
>
> Hello,
>
> This morning about 10% of the reporting jobs failed. The failure was 
> always on CAMPAIGN_PERFORMANCE_REPORT. This is the report definition:
> 
> 
>https://adwords.google.com/api/adwords/cm/v201802
> ">
>CampaignId
>Date
>AdNetworkType2
>ClickAssistedConversions
>ClickAssistedConversionValue
>ImpressionAssistedConversions
>ImpressionAssistedConversionValue
>
>CampaignStatus
>IN
>ENABLED
>PAUSED
>REMOVED
>
>
>20180827
>20181211
>
>
>https://adwords.google.com/api/adwords/cm/v201802;> 
> CampaignAssistedConversion 27-08-2018...11-12-2018
>https://adwords.google.com/api/adwords/cm/v201802
> ">CAMPAIGN_PERFORMANCE_REPORT
>https://adwords.google.com/api/adwords/cm/v201802
> ">CUSTOM_DATE
>https://adwords.google.com/api/adwords/cm/v201802
> ">GZIPPED_XML
> 
>
> The three rows in the returned XML:
>  networkWithSearchPartners='Google search' clickAssistedConv='0' 
> clickAssistedConvValue='--' imprAssistedConv='0' 
> imprAssistedConvValue='--'/>
>  networkWithSearchPartners='Google search' clickAssistedConv='0' 
> clickAssistedConvValue='--' imprAssistedConv='0' 
> imprAssistedConvValue='--'/>
>  networkWithSearchPartners='Google search' clickAssistedConv='0' 
> clickAssistedConvValue='--' imprAssistedConv='0' 
> imprAssistedConvValue='--'/>
>
> Note the values on clickAssistedConvValue and imprAssistedConvValue.
>
> I would like to stress that this has never happened in the previous 
> months when we used v201802, nor it happened in previous versions of 
> AdWords API. This appears to be new behavior, breaking some of our 
> operations.
>
>
> Was this an error in the API?
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/a62a8076-3af9-47bb-adf9-53d18856b9fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to get household income data

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Harisankar,

Demographic criteria like INCOME_RANGE, AGE_RANGE, GENDER are criteria that 
are enabled by default for all audience, so we don't explicitly add these 
criteria in a campaign. These criteria appear in a campaign only when you 
explicitly do something with those critieria (e.g. add a negative age range 
criteria, or apply a bid adjustment to a specific gender).

E.g. if you can't retrieve Gender criteria for a campaign, you should 
interpret it as "there's no special gender criteria for this campaign, so 
it is serving to GENDER_MALE, GENDER_FEMALE and GENDER_UNDETERMINED).

Hope this helps? Let me know if you have more questions.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Saturday, December 8, 2018 at 4:07:12 PM UTC-5, Harisankar Mohanty wrote:
>
> Hello API Team,
>
> I am using Google Adwords API version : v201806 (PHP) to develop a web app.
>
> I am struck somewhere to retrieve Household Income Tier for a particular 
> Campaign. Though I am getting info for criteria type 'LOCATION' but other 
> criteria type does not work for me like 'INCOME_RANGE' or 'AGE_RANGE' etc. 
> I have posted my code below. Can you please check and let me know why I am 
> not getting data for Household Income Tier when I use criteria type 
> 'INCOME_RANGE' ?
>
> public static function runExample (
> AdWordsServices $adWordsServices,
> //AdWordsSession $session
> AdWordsSessionBuilder $sessionBuilder,
> $customerId, $campaignId = null, $locationIds = null, 
> $criteriaType = null
> ) {
> 
> $session = 
> $sessionBuilder->withClientCustomerId($customerId)->build();
> $campaignCriterionService = $adWordsServices->get($session, 
> CampaignCriterionService::class);
>
> $selector = new Selector();
> 
> $selector->setFields(array('Id','CampaignId','MatchingFunction','LocationName','Address'));
> $predicates[] = new Predicate('CampaignId', PredicateOperator::IN, 
> array($campaignId));
> //$predicates[] = new Predicate('CriteriaType', 
> PredicateOperator::IN,  array('AD_GROUPS'));
> $predicates[] = new Predicate('CriteriaType', PredicateOperator::IN,  
> array($criteriaType));
> 
> $selector->setPredicates($predicates);
> 
> $startIndex = 0;
> 
> $selector->setPaging(new Paging($startIndex, 10));
> echo "";
> print_r($selector);
> 
> do {
> // Make the get request.
> $page = $campaignCriterionService->get($selector);
> 
> echo "";
> print_r($page);
> die();
>
> // Display results.
> if (!empty($page->getEntries())) {
> //return $page->entries;
> $return['data'] = $page->getEntries();
> 
> 
> 
>   foreach ($page->getEntries() as $campaignCriterion) {
> 
> 
> if(in_array($campaignCriterion->getCriterion()->matchingFunction->rhsOperand[0]->locations[0],
>  
> $locationIds)) {
> 
> $locations[$campaignCriterion->criterion->id]['location'] = 
> $campaignCriterion->criterion->matchingFunction->rhsOperand[0]->locations[0];
> 
> $locations[$campaignCriterion->criterion->id]['tier'] = 
> $campaignCriterion->criterion->matchingFunction->lhsOperand[0]->tier;
> }
>   }
>   
> } else {
>   //print "No campaign targeting criteria were found.\n";
>   $locations = false;
> }
> //$return['locations'] = array_unique($locations);
> //return $locations;
> 
> // Advance the paging index.
> $startIndex += 10;
> $selector->getPaging()->setStartIndex($startIndex);
> } while ($page->totalNumEntries > $selector->getPaging()->getStartIndex());
> 
>return $locations;
>
> 
> }
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0ae9894b-fc57-4df3-a6ca-888a289ac01d%40googlegroups.com.
For more 

Re: Disk Quota for Batch Jobs is a negative number and doesn't seem to be recovering

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Sanjay,

We did another spot check yesterday and no longer see this issue for any 
accounts. Feel free to reopen this thread if you see more issues.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Friday, September 14, 2018 at 3:30:34 PM UTC-4, Anash P. Oommen (AdWords 
API Team) wrote:
>
> Hi Sanjay,
>
> We are investigating. I haven't seen additional reports though. Is this 
> issue still present?
>
> Thanks,
> Anash P. Oommen,
> AdWords API Advisor.
>
> On Friday, September 14, 2018 at 5:33:45 AM UTC-4, san...@goshift.com 
> wrote:
>>
>> Thanks for confirming that. 
>>
>> I don't believe the BatchJobService has fully recovered though, as some 
>> of your batch jobs are still taking a age to process which is causing our 
>> test build to take much longer then usual. 
>>
>> Also is there a status page we can go to, to view the health of the 
>> various adwords api services?
>>
>> Thanks
>> Sanjay
>>
>> On Thursday, September 13, 2018 at 8:05:22 PM UTC+1, Anash P. Oommen 
>> (AdWords API Team) wrote:
>>>
>>> Hi Sanjay,
>>>
>>> I can confirm that this was related to the issues we were having with 
>>> BatchJobService earlier today. This issue should be fixed now. Let me know 
>>> if you continue seeing negative values for diskQuotaUsageBalance.
>>>
>>> Cheers
>>> Anash P. Oommen,
>>> AdWords API Advisor.
>>>
>>> On Thursday, September 13, 2018 at 10:16:13 AM UTC-4, Sreelakshmi 
>>> Sasidharan (AdWords API Team) wrote:

 Hi Sanjay, 

 Thanks for the details. I am checking with the team and will keep you 
 updated as soon as I hear from them. 

 Thanks,
 Sreelakshmi, AdWords 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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/2814ba92-67d7-4992-934f-519dc997fe7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disk Quota for Batch Jobs is a negative number and doesn't seem to be recovering

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Sanjay,

We are investigating. I haven't seen additional reports though. Is this 
issue still present?

Thanks,
Anash P. Oommen,
AdWords API Advisor.

On Friday, September 14, 2018 at 5:33:45 AM UTC-4, san...@goshift.com wrote:
>
> Thanks for confirming that. 
>
> I don't believe the BatchJobService has fully recovered though, as some of 
> your batch jobs are still taking a age to process which is causing our test 
> build to take much longer then usual. 
>
> Also is there a status page we can go to, to view the health of the 
> various adwords api services?
>
> Thanks
> Sanjay
>
> On Thursday, September 13, 2018 at 8:05:22 PM UTC+1, Anash P. Oommen 
> (AdWords API Team) wrote:
>>
>> Hi Sanjay,
>>
>> I can confirm that this was related to the issues we were having with 
>> BatchJobService earlier today. This issue should be fixed now. Let me know 
>> if you continue seeing negative values for diskQuotaUsageBalance.
>>
>> Cheers
>> Anash P. Oommen,
>> AdWords API Advisor.
>>
>> On Thursday, September 13, 2018 at 10:16:13 AM UTC-4, Sreelakshmi 
>> Sasidharan (AdWords API Team) wrote:
>>>
>>> Hi Sanjay, 
>>>
>>> Thanks for the details. I am checking with the team and will keep you 
>>> updated as soon as I hear from them. 
>>>
>>> Thanks,
>>> Sreelakshmi, AdWords 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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/408aa446-7cec-4b58-bc7e-87dfc6e0b388%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disk Quota for Batch Jobs is a negative number and doesn't seem to be recovering

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Sanjay,

I can confirm that this was related to the issues we were having with 
BatchJobService earlier today. This issue should be fixed now. Let me know 
if you continue seeing negative values for diskQuotaUsageBalance.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Thursday, September 13, 2018 at 10:16:13 AM UTC-4, Sreelakshmi 
Sasidharan (AdWords API Team) wrote:
>
> Hi Sanjay, 
>
> Thanks for the details. I am checking with the team and will keep you 
> updated as soon as I hear from them. 
>
> Thanks,
> Sreelakshmi, AdWords 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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/9fcf418b-19aa-41b4-99e7-ef612f1abb30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: BatchJobs - Huge processing times since last night

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Thorsten,

I can confirm that the issue has been fixed at our end, and we are seeing 
normal throughput for BatchJobs. Feel free to ping this thread if you 
continue seeing issues.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Thursday, September 13, 2018 at 2:13:33 PM UTC-4, Thorsten Merz wrote:
>
> I can confirm that for the moment batch jobs are running at the normal 
> speed.
>
> Thanks for the support and solving the issue.
>
> --
>
> On Thursday, September 13, 2018 at 7:08:53 PM UTC+2, Jan wrote:
>>
>> Seems our problems with the BatchJobService are solved.
>>
>> BatchJobService times are back to seconds instead of hours.
>>
>> Thanks for solving it!
>>
>>
>>
>>
>> On Thursday, September 13, 2018 at 6:09:13 PM UTC+2, 
>> stanislav...@stylelounge.de wrote:
>>>
>>> We are still experiencing a similar issue too. A small batch job of less 
>>> than a thousand operations never gets beyond zero in numOperationsExecuted 
>>> and estimatedPercentExecuted.
>>>
>>> On Thursday, September 13, 2018 at 3:23:40 PM UTC+2, Anash P. Oommen 
>>> (AdWords API Team) wrote:

 Folks,

 We had an ongoing issue that caused these delays. The issue should be 
 fixed now, but if you continue to see delays, feel free to update this 
 thread and I'll investigate.

 Cheers
 Anash P. Oommen,
 AdWords API Advisor.

 On Thursday, September 13, 2018 at 3:49:53 AM UTC-4, Thorsten Merz 
 wrote:
>
> Hey there,
>
> since last night (8 hours ago) we started to have increasing 
> processing times on our batch job executions up to a point where the job 
> takes longer than 2000 seconds to finish (if at all). Our usual average 
> normally is around 15 seconds.
>
> Examples are attached incl. batch job IDs
>
> Some fix for this would be appreciated.
>
> Regards
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/fb33c4d7-9ac9-4ab3-9fb0-83e4867ebc1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: BatchJobs - Huge processing times since last night

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Thorsten,

Thanks for reporting. Looks like batch jobs are still having issues. We are 
investigating...

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Thursday, September 13, 2018 at 9:38:57 AM UTC-4, Thorsten Merz wrote:
>
> Thanks for the info... sadly we are still experiencing the same issue.
>
> Find attached a list of our latest batch job ids.
>
> --
>
> On Thursday, September 13, 2018 at 3:23:40 PM UTC+2, Anash P. Oommen 
> (AdWords API Team) wrote:
>>
>> Folks,
>>
>> We had an ongoing issue that caused these delays. The issue should be 
>> fixed now, but if you continue to see delays, feel free to update this 
>> thread and I'll investigate.
>>
>> Cheers
>> Anash P. Oommen,
>> AdWords API Advisor.
>>
>> On Thursday, September 13, 2018 at 3:49:53 AM UTC-4, Thorsten Merz wrote:
>>>
>>> Hey there,
>>>
>>> since last night (8 hours ago) we started to have increasing processing 
>>> times on our batch job executions up to a point where the job takes longer 
>>> than 2000 seconds to finish (if at all). Our usual average normally is 
>>> around 15 seconds.
>>>
>>> Examples are attached incl. batch job IDs
>>>
>>> Some fix for this would be appreciated.
>>>
>>> Regards
>>>
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/73a7f5ab-6fa2-41d0-9fc9-9395ce0de2cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: BatchJobs - Huge processing times since last night

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Folks,

We had an ongoing issue that caused these delays. The issue should be fixed 
now, but if you continue to see delays, feel free to update this thread and 
I'll investigate.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Thursday, September 13, 2018 at 3:49:53 AM UTC-4, Thorsten Merz wrote:
>
> Hey there,
>
> since last night (8 hours ago) we started to have increasing processing 
> times on our batch job executions up to a point where the job takes longer 
> than 2000 seconds to finish (if at all). Our usual average normally is 
> around 15 seconds.
>
> Examples are attached incl. batch job IDs
>
> Some fix for this would be appreciated.
>
> Regards
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/1436e600-1509-43bd-9d73-1751f864b92e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: When creating UAC ads, create them separately through the AdWords API and the AdWords UI, and see the results in the AdWords UI for a different display.

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Jia,

Apologies for the delay. Images uploaded through MediaService doesn't show 
up in the UI under Creative Assets. That page only lists the items created 
using AssetService, as far as I know.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Monday, August 13, 2018 at 2:45:02 AM UTC-4, jia zheng wrote:
>
> Can you help analyze this phenomenon as soon as possible?
>
> 在 2018年8月8日星期三 UTC+8上午11:06:28，Peter Oliquino (AdWords API Team)写道：
>>
>> Hi Jia,
>>
>> Could you confirm if you have seen my previous private response? I would 
>> recommend that you remove the YoutubeVideoMediaIds in your request since 
>> passing them is currently not supported via the AdWords API.
>>
>> Thanks and regards,
>> Peter
>> AdWords API Team
>>
>> On Wednesday, August 8, 2018 at 10:17:37 AM UTC+8, jia zheng wrote:
>>>
>>>
>>> Hi, can you see my private letter to you? Where can I see your reply?
>>> 在 2018年8月6日星期一 UTC+8下午2:22:35，Peter Oliquino (AdWords API Team)写道：

 Hi Jia,

 So I can better investigate the issue, could you provide to me the 
 complete SOAP request and response and your clientCustomerId? You may 
 reply 
 to me using the *Reply privately to author* option.

 Thanks and regards,
 Peter
 AdWords API Team

 On Monday, August 6, 2018 at 11:53:13 AM UTC+8, jia zheng wrote:
>
> Create UAC ads from the AdWords UI and display all the material on the 
> CREATIVE ASSETS page. For UAC ads created through the AdWords API, you 
> will 
> see any donate on the CREATIVE ASSETS page.
> why? 
> The screenshots are attached as above (UACtest1 is created by the 
> AdWords UI and Here is the series name 6 created by the AdWords API).
>
> The xml log is as follows:
>
> 
> 
> ADD
> 
> Here is the series name 6
> PAUSED
> 
> ***
> 
> https://adwords.google.com/api/adwords/cm/v201802; 
> xsi:type="ns2:UniversalAppCampaignSetting">
> com.globalegrow.app.gearbest
> VENDOR_GOOGLE_MARKET
> Shopping
> GearBest
> Online Shopping
> Internet Shopping
> ***
> **
>
> OPTIMIZE_FOR_INSTALL_CONVERSION_VOLUME
> 
> MULTI_CHANNEL
>
> UNIVERSAL_APP_CAMPAIGN
> 
> TARGET_CPA
> https://adwords.google.com/api/adwords/cm/v201802; 
> xsi:type="ns2:TargetCpaBiddingScheme">
> 
> 10
> 
> 
> 
> 
> 
> 
>


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/accd33f9-5a99-4019-ad69-342751acc81a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to add dummy data to my test account

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

No, this feature request is not yet supported in AdWords API.

Anash P. Oommen,
AdWords API Advisor.

On Monday, August 6, 2018 at 3:15:25 AM UTC-4, mymanagerforg...@gmail.com 
wrote:
>
> Any Update on this ?
>
> On Monday, April 15, 2013 at 8:29:21 PM UTC+5:30, Kevin Winter (AdWords 
> API Team) wrote:
>>
>> We're working on a mini-guide explaining how to approach this.  In the 
>> meantime, here's a draft:
>>
>> Test accounts will not serve impressions, therefore they will not have 
>> any metrics.  It is still possible to download structural reports 
>>  
>> - but you will only see zero-impression rows, which means that segments 
>> will not work.  To get around this limitation, we suggest displaying fake 
>> data.  The Token Review team needs to see that your application can 
>> interact with and display report data.  By mocking out the report call 
>> (i.e. pretending the report call succeeded and using a locally stored file 
>> containing fake report data), you can work with report data without 
>> actually having such data come back from the API.
>>
>> The reports come back in a predictable format.  Let's say you wanted to 
>> run a Campaign Performance Report pulling Date, Campaign Name, Id, 
>> Impressions, Clicks, Cost. An example file could look like this:
>>
>> "CAMPAIGN_PERFORMANCE_REPORT (Mar 20, 2013-Mar 23, 2013)"
>> Day,Campaign,Campaign ID,Impressions,Clicks,Cost
>> 20130320,Widgets,123,1211,19,14.92
>> 20130320,Sprockets,456,300,4,2.92
>> 20130321,Widgets,123,901,12,9.86
>> 20130321,Sprockets,456,340,5,3.86
>> 20130322,Widgets,123,1065,16,11.23
>> 20130322,Sprockets,456,509,6,5.23
>> 20130323,Widgets,123,1005,15,10.12
>> 20130323,Sprockets,456,287,3,1.12
>>
>> By constructing such a file and storing it locally, you could have your 
>> application mock the call to the API - when the report is requested, return 
>> the stored file and process that rather than making an actual API call. 
>>  You can create one file like this for each report you’d like to display.
>>
>> - Kevin Winter
>> AdWords API Team
>>
>> On Wednesday, April 10, 2013 9:08:45 AM UTC-4, William Rufino wrote:
>>>
>>> Can anyone give me an idea how to test report api without data?
>>>
>>> Em segunda-feira, 8 de abril de 2013 11h17min19s UTC-3, William Rufino 
>>> escreveu:

 How do we test the api if we can't have data in it?

 Does anyone can help with that?

 Em sexta-feira, 5 de abril de 2013 11h04min22s UTC-3, Paul Matthews 
 (AdWords API Team) escreveu:
>
> Hi Jonathan,
>
> There is currently no way to add test data to your test account. We 
> are aware of this feature request and we're looking into it.
>
> Regards,
>
> - Paul, AdWords API Team.
>
> On Monday, 25 March 2013 03:15:41 UTC, Jonathan Sosa wrote:
>>
>> Hi
>>
>> I'm trying to get the Campaign Performance Report for my test 
>> account, but it returns no rows.
>>
>> I think the reason is adding the required segment field ClickType. 
>> (All my test campaigns have no clicks)
>>
>> Is there a way to add dummy data Clicks/Impressions/etc to my test 
>> campaigns?
>>
>> Best
>> Jonathan
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0a085a34-c0e7-4fc6-bb4f-214323be9a46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Policy violations - v201710 vs 201706

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Greg,

Since Josh is not available, I'll answer your questions instead.

1. Yes, ETA won't produce any PolicyViolationError. Let me know if you see 
any behaviour otherwise, and we will investigate on priority.
2. PolicyFindingErrors (and policies in general) are a lot dependent on the 
account in which the ad serves, the geographies for which the ad serves, 
the network, whether we've seen a lot of these errors (and violations) in 
the past, etc. The test accounts are meant for minimal replication of 
policy errors; it doesn't support all combinations of PolicyViolationErrors 
you'd see in production accounts. My suggestion is to design your 
application such that you can test and verify for minimal 
PolicyViolationErrors against test accounts, and be able to specify 
additional policies as runtime-configurable.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Friday, July 27, 2018 at 12:24:14 PM UTC-4, GregT wrote:
>
> Hey, Josh.
>
> Thanks for looking into this and for the information. I'd just like to 
> clarify some things.  
>
> 1 - Are you saying that creating expanded text ads will now *never* produce 
> a PolicyViolationError, and we should only be looking for 
> PolicyFindingErrors? It seems pretty clear that that's what you (& the 
> documentation you pasted) are saying, but I just want to double check, as 
> it seems like that means for expanded text ads, there's really not 
> exemptable vs. non-exemptable anymore, and there's just a single type of 
> "exemptable but your request will be denied" violation.
>
> 2 - As I mentioned in my original July 3 post, I tried to produce (in the 
> sandbox with v201806) policy violations by using things that are direct 
> violations of what's given in the advertising policies page you mentioned 
> (like "work @home", "big big SALE", "FR33 ShiPPiNG", "buy hunting rifle", 
> various brand names that produce trademark violations in production, etc.), 
> and these are accepted by the sandbox without issue, although production 
> v201802 produces policy violations. As I mentioned, the only thing I can 
> get to produce a policy violation (the new PolicyFindingError) in the 
> sandbox for v201806 expanded text ads is multiple exclamation points in a 
> row. Is this expected (it seems like it wouldn't be, considering you 
> pointed to the advertising policies page for examples of ad text that 
> should trigger errors)? I guess, in reality, if the answer to #1 above is 
> yes, then since I can produce that error with multiple exclamation points, 
> this question is irrelevant, although it seems odd. 
>
> Thanks,
> Greg
>
> On Thursday, July 26, 2018 at 4:35:39 PM UTC-5, Josh Radcliff (AdWords API 
> Team) wrote:
>>
>> Hi Greg,
>>
>> I ran some tests and spoke with my colleagues today. Starting with 
>> v201806, some ad types will return a *PolicyFindingError* *instead of* a 
>> *PolicyViolationError* when there are policy issues. Here's the note we 
>> added to the Policy Exemption Requests guide 
>>  
>> for 
>> the v201806 release (yellow highlights mine):
>>
>> *Note:* Starting in v201806, some ad types (including ExpandedTextAd 
>> )
>>  
>> will fail with a PolicyFindingError 
>> 
>>  instead. This new type of error indicates that the ad will certainly 
>> fail review again even if an exemption is requested. You can save these ads 
>> anyway by using the ignorablePolicyTopicIds 
>> 
>>  field. 
>> They will fail review, but could be approved later if you fix the 
>> underlying issue, for example by getting the correct certificate.
>>
>> Therefore, if you're looking to handle errors specifically for 
>> *ExpandedTextAds*, you'll want to:
>>
>>1. Modify your error handling to instead check for 
>>*PolicyFindingError*.
>>2. If you want to resubmit an operation even though it's likely to 
>>wind up with policy errors, collect all of the policyTopicIds 
>>
>> 
>>  from 
>>the error's policyTopicEntries 
>>
>> ,
>>  
>>add those IDs to the operation's ignorablePolicyTopicIds 
>>
>> ,
>>  
>>then resubmit the operation.
>>
>> You can see examples of ad text that will trigger these errors in this 
>> Advertising Policies Help page 
>> 

Re: Ads API operations limits

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Don,

Google Ads API has the same operation limits as AdWords API. If the rate 
exceeds, you will get a QuotaError.RESOURCE_EXHAUSTED 

 
error. So overall, the rate limit guide from WebApi 
 applies 
for Google Ads API too, except you get a different error.

Hope this helps? Let me know if you have more questions.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Friday, July 20, 2018 at 5:18:13 PM UTC-4, Don Mitchell wrote:
>
> I can't find doc on the operations limits for the Ads API 
> 
>  (beta). 
> Does anyone know is it per service or universal? Is it a the same over all 
> customers? Can they point me to the doc or tell me the answer?
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/818a7e00-feb5-46ea-8912-5e0f1d42e873%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot add beta API to Google Developer Console project

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Zweitze,

That's strange indeed. I suspect this is an issue with the Google Developer 
Console. There should be an option to enter feedback in the UI, which can 
be used to report a bug too. If that doesn't work, reply to me privately 
with the screenshot + Browser version details and I'll file it on your 
behalf.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Tuesday, July 3, 2018 at 7:27:25 AM UTC-4, Zweitze wrote:
>
> It turned out that you cannot use Firefox to enable Google Ads API. When 
> you select Ads API from the search results you get an error in Firefox, but 
> in Chrome this works.
> Can I submit this bug report like this?
>
>
>
> On Thursday, June 28, 2018 at 6:46:12 PM UTC+2, Teja Makani wrote:
>>
>> Hello Zweitze,
>>
>> Could you try to enable the Google Ads API using the incognito mode of 
>> Google Chrome and use the credentials that the project was created with 
>> while logging into developer's console? If the issue persists, could you 
>> please provide your MCC ID and the email address you are using while 
>> enabling the Google Ads API in developer's console to investigate further? 
>> You could *reply privately to the author* while sharing the details.
>>
>> Regards,
>> Sai Teja, AdWords 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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/299bc75d-b725-4ad8-845a-206813e94da5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Limits issue: ProductPartitionTree .createAdGroupTree generates API request

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Yep, your code should work.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Tuesday, July 3, 2018 at 11:06:09 AM UTC-4, Константин Латыпов wrote:
>
> Thank you.
>
> this code fixed issue:
>   
> productAdGroupCriterion.setBiddingStrategyConfiguration(adGroup.getBiddingStrategyConfiguration());
>   
> emptyAdGroupCriterion.setBiddingStrategyConfiguration(adGroup.getBiddingStrategyConfiguration());
>
> But there is last issue (I hope)
> How can I create exculuded partition?
>
> Something like this code for PartitionNode:
>   partitionNode
> .addChild(emptyDimensionType)
> .asExcludedUnit();
>
>
> Best regards
>
>
> понедельник, 2 июля 2018 г., 19:24:45 UTC+3 пользователь Anash P. Oommen 
> (AdWords API Team) написал:
>>
>> Hi,
>>
>> Could you try a few things?
>>
>> 1. You are missing a biddingStrategyConfiguration node in couple of 
>> operands, could you add them?
>> 2. Could you make sure the root node appears before the child nodes in 
>> the operations list?
>>
>> Let me know if that doesn't address the issues.
>>
>> Cheers
>> Anash P. Oommen,
>> AdWords API Team.
>>
>> On Monday, July 2, 2018 at 10:39:16 AM UTC-4, Константин Латыпов wrote:
>>>
>>> Hi, Dannison
>>>
>>> I sent you info via "Reply privately to author" at friday. If you will 
>>> need any additional info I will be glad to provide it.
>>>
>>> Best regards
>>>
>>> пятница, 29 июня 2018 г., 10:52:30 UTC+3 пользователь Dannison Yao 
>>> (AdWords API Team) написал:

 Hi,

 My apologies for the back and forth. Could you send me your complete 
 SOAP request and response logs that was generated when you used this code 
 you sent in your previous response along with your clientCustomerId so I 
 could further investigate this? You may send this via *Reply privately 
 to author*. Could you also set your SOAP XML logger to *DEBUG* mode?

 Regards,
 Dannison
 AdWords 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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/d460f92e-f6df-451f-9e39-03b952baffc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Limits issue: ProductPartitionTree .createAdGroupTree generates API request

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

Could you try a few things?

1. You are missing a biddingStrategyConfiguration node in couple of 
operands, could you add them?
2. Could you make sure the root node appears before the child nodes in the 
operations list?

Let me know if that doesn't address the issues.

Cheers
Anash P. Oommen,
AdWords API Team.

On Monday, July 2, 2018 at 10:39:16 AM UTC-4, Константин Латыпов wrote:
>
> Hi, Dannison
>
> I sent you info via "Reply privately to author" at friday. If you will 
> need any additional info I will be glad to provide it.
>
> Best regards
>
> пятница, 29 июня 2018 г., 10:52:30 UTC+3 пользователь Dannison Yao 
> (AdWords API Team) написал:
>>
>> Hi,
>>
>> My apologies for the back and forth. Could you send me your complete SOAP 
>> request and response logs that was generated when you used this code you 
>> sent in your previous response along with your clientCustomerId so I could 
>> further investigate this? You may send this via *Reply privately to 
>> author*. Could you also set your SOAP XML logger to *DEBUG* mode?
>>
>> Regards,
>> Dannison
>> AdWords 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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/b844598e-dfea-40cb-aca3-0b78cb7c1914%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adwords negative cross device conversions

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Folks,

Making a post for the benefit of future readers. We had an issue at an our 
end that occasionally caused conversions to show up as negative numbers. 
This should be fixed out our end now. If you continue seeing issues. open a 
new thread since this thread is dated.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Monday, September 19, 2016 at 12:11:31 AM UTC-4, Thu Nguyen wrote:
>
> We have an adwords account (2800990872), with negative cross device 
> conversions (Conversions is higher than AllConversions). This is happening 
> for both the Geo Performance and Search Query Performance reports. 
>
> date of query 8/31/2016
>
> Device Date CountryCriteriaId RegionCriteriaId CityCriteriaId Clicks 
> ConversionValue ViewThroughConversions Conversions CrossDeviceConversions 
> AllConversions Interactions VideoViews
> Mobile devices with full browsers 
> 2356 20462 1007788 0 -5 0
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/9ca42a57-b4bf-42c8-a5d7-8da4167750aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can ads disappear after they have been removed?

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Zweitze,

The "disappeared ads" seems to be an issue at our end. The case you 
mentioned is another possibility, but doesn't seem to be the root cause of 
this issue as far as I can tell. I've pinged the team for updates, and will 
share them as I hear back.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Wednesday, June 13, 2018 at 1:59:52 PM UTC-4, Zweitze wrote:
>
> Hey Nadine,
>
> Any updates?
> I think I have an explanation - it's due to the possibility that now most 
> ad properties can be changed (until a few months ago only status could be 
> changed - for other changes you had to set the status to deleted and 
> created a new ad with the desired properties).
> Our software always assumed this would not change, at least not in the API 
> version it was operating on.
>
> But exactly that seems to happen: when you request (using an older API 
> version) an ad after it was changed, you will get an ad with the same ad id 
> and its new properties. I must say, I did not expect such behavior change.
>
> Can you confirm this is the case? (All software using older API versions 
> should now be aware that most properties are no longer immutable). Was this 
> announced anywhere?
>
> Thanks in advance!
>
>
> On Tuesday, May 22, 2018 at 11:27:57 PM UTC+2, Nadine Sundquist (AdWords 
> API Team) wrote:
>>
>> Hi Zweitze,
>>
>> As always, it's nice to hear from you! I hope you are doing well. You've 
>> given me the present of yet another strange puzzle. I wasn't aware that ads 
>> could just disappear. Like you, I'm only aware of other entities that could 
>> be removed permanently, but I didn't think ads were one of them. Thanks for 
>> providing all that information. I'll look into it, and I'll get back to you.
>>
>> Best,
>> Nadine, AdWords API Team
>>
>> On Tuesday, May 22, 2018 at 7:46:04 AM UTC-4, Zweitze wrote:
>>>
>>> Hi all,
>>>
>>> When an ad is removed, according to the documentation its status is 
>>> changed to "removed" and it becomes read-only, so it will never be enabled 
>>> again. But, you can still request it, and you will get all its properties.
>>>
>>> However, I find more and more examples of ads that stop existing. I 
>>> mean, they can no longer be requested. The ad seems to have disappeared. 
>>> This sounds incredible but starting this year I started to witness 
>>> "disappeared" ads. And I never witnessed this behaviour in the previous ten 
>>> years or so.
>>> I have some sample ids (pairs of adgroupid+adid):
>>> 51500212996266833925427
>>> 51500212996266833925430
>>> 51500213716266833925481
>>> 51500213716266833925484
>>> 51500214436266833925655
>>> 51500214436266833925658
>>> 51500215396266833925727
>>> 51500215396266833925730
>>> So, these ads did appear in ad reports earlier this year, but they no 
>>> longer appear. We learned of its existance with reporting in AdWords API, 
>>> the report type was AD_PERFORMANCE_REPORT. But if you request the same 
>>> report now, they no longer exist.
>>>
>>> Note: I do know of similar behavior with keywords: they may actually 
>>> disappear, this happens when a keyword was deleted, and never had any 
>>> impression. But that was only keywords.
>>>
>>> Can this policy have been extended to ads as well? Is it also introduced 
>>> in other AdWords API objects, like managed placements, or ad extensions, or 
>>> groups? Under what conditions do ads disappear? Maybe a link to a blog 
>>> article is helpful.
>>>
>>> If ads can actually disappear as I noticed, is it possible that its ID 
>>> will be reused within the same group? In other words, can later a different 
>>> ad (with different headlines, description, final URLs etc.etc.) appear 
>>> using the same adid?
>>>
>>> Note: I realize this is actually a product question, but it's hard to 
>>> explain the significance of a disappearing ad vs. an existing ad with 
>>> status "removed", and I think the question on adid reuse is a question 
>>> which is better answered by the API team.
>>>
>>>
>>> Thanks in advance!
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 

Re: Ids and mutating ads

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Greg,

One instance I can think of is when you clone campaigns in the UI by 
copy-paste. Ad IDs are reused AFAIK in that case.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Tuesday, June 12, 2018 at 2:53:15 PM UTC-4, GregT wrote:
>
> Okay - sorry for the confusion, Anash. I think my confusion came from how 
> we would need an ad group id to identify AdGroupAds uniquely if ad ids are 
> unique, and I forgot about shared ads because AdWords got rid of them 2 or 
> 3 years ago. Are there cases where an ad id can be shared across ad groups 
> nowadays?
>
> And sorry, I realized the criterion id uniqueness question was silly right 
> after posting it, as I've definitely seen reused product partition and 
> keyword ids across ad groups many times.
>
> Thanks again,
> Greg
>
> On Tuesday, June 12, 2018 at 12:56:38 PM UTC-5, Anash P. Oommen (AdWords 
> API Team) wrote:
>>
>> Hi Greg,
>>
>> Yes, the way you read the documentation is correct. Ad Ids may be reused 
>> across ad groups. As I mentioned in my previous post, AdGroupAd is not the 
>> same thing as Ad. Ad is the actual underlying entity, and AdGroupAd is a 
>> link that associates an AdGroup and an Ad. A typical example where you 
>> might see AdId getting reused across AdGroups is when using is shared Ads. 
>>
>> Cheers
>> Anash
>>
>> On Tuesday, June 12, 2018 at 1:01:24 PM UTC-4, GregT wrote:
>>>
>>> Hi Anash.
>>>
>>> Thanks for the quick reply and clearing that up. It makes sense. 
>>>
>>> I will say that I've been using the API for years, and I've always taken 
>>> that page on id uniqueness to mean that we had to be careful within our 
>>> code and database to deal with the possibility that an ad id might be 
>>> reused across ad groups even within a single account -- as that's the way 
>>> the documentation reads to me. Maybe this is what you're saying you guys 
>>> are planning on doing, but it seems like a better way to do the 
>>> documentation is to have 
>>> https://developers.google.com/adwords/api/docs/guides/objects-methods 
>>> really list what it appears it's listing (what scope various ids are unique 
>>> within), and document in the individual SOAP services whether or not you 
>>> need to include something like AdGroupId in the get/set calls even though 
>>> something like the ad id might be globally unique itself.
>>>
>>> So does this also mean that CriterionId (e.g. keyword and product 
>>> partition ids) are also globally unique, even though the documentation says 
>>> that the (AdGroupId, CriterionId) pair is what's globally unique (like it 
>>> does with the [AdGroupId, AdId] pair)? 
>>>
>>> Thanks,
>>> Greg
>>>
>>>
>>> On Tuesday, June 12, 2018 at 11:32:01 AM UTC-5, Anash P. Oommen (AdWords 
>>> API Team) wrote:

 Hi Greg,

 We need to update the Unique IDs documentation a bit, now that 
 AdService is available. The more detailed version is like this:

 - AdId represents a globally unique creative ID. This means that you 
 can edit an Ad using AdService using creativeId without any concern of ID 
 collision.

 - AdGroupAd is a link that associates an Ad to an AdGroup. But we don't 
 expose an AdGroupAdId. You could use the pair (adgroupid, adid) as a proxy 
 ID for AdGroupAd. Hence our warning that when querying using 
 AdGroupAdService.get, you should not consider adId to be a unique Id, you 
 should rather use the pair (adgroupid, adid) as a unique pair.

 So, you are fine if you follow these guidelines:

 1. When using AdGroupAdService.get, use (adGroupid, adId) as a unique 
 ID for querying purposes.
 2. When using AdService.mutate, use adId as a unique ID for updating 
 the ad.

 Hope this helps?

 Cheers
 Anash P. Oommen,
 AdWords API Advisor.

 On Tuesday, June 12, 2018 at 12:22:00 AM UTC-4, GregT wrote:
>
> Hi,
>
> I saw that in the recent v201806 release of the API, there is now the 
> ability to mutate ads. This would make some things simpler for us where 
> we're currently doing removal and adds to accomplish the same thing, so 
> it'd be nice to use it. However, I'm a little hesitant, because something 
> seems wrong about it. According to 
> https://developers.google.com/adwords/api/docs/guides/ad-features#mutating_ads_for_v201806_and_later,
>  
> you can mutate the Ad by using the new AdService, setting the id field of 
> the Ad, setting whatever fields you want to change, and sending it with 
> the 
> SET operator. The part that worries me is that ad ids are not globally 
> unique, even within a single account, but are unique only within an ad 
> group (
> https://developers.google.com/adwords/api/docs/guides/objects-methods). 
> So, it seems unsafe and error prone to be able to modify an ad by 
> specifying just its id, as you could have more than one ad in your 
> account 
> with that id, leading to 

Re: Ids and mutating ads

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Greg,

Yes, the way you read the documentation is correct. Ad Ids may be reused 
across ad groups. As I mentioned in my previous post, AdGroupAd is not the 
same thing as Ad. Ad is the actual underlying entity, and AdGroupAd is a 
link that associates an AdGroup and an Ad. A typical example where you 
might see AdId getting reused across AdGroups is when using is shared Ads. 

Cheers
Anash

On Tuesday, June 12, 2018 at 1:01:24 PM UTC-4, GregT wrote:
>
> Hi Anash.
>
> Thanks for the quick reply and clearing that up. It makes sense. 
>
> I will say that I've been using the API for years, and I've always taken 
> that page on id uniqueness to mean that we had to be careful within our 
> code and database to deal with the possibility that an ad id might be 
> reused across ad groups even within a single account -- as that's the way 
> the documentation reads to me. Maybe this is what you're saying you guys 
> are planning on doing, but it seems like a better way to do the 
> documentation is to have 
> https://developers.google.com/adwords/api/docs/guides/objects-methods 
> really list what it appears it's listing (what scope various ids are unique 
> within), and document in the individual SOAP services whether or not you 
> need to include something like AdGroupId in the get/set calls even though 
> something like the ad id might be globally unique itself.
>
> So does this also mean that CriterionId (e.g. keyword and product 
> partition ids) are also globally unique, even though the documentation says 
> that the (AdGroupId, CriterionId) pair is what's globally unique (like it 
> does with the [AdGroupId, AdId] pair)? 
>
> Thanks,
> Greg
>
>
> On Tuesday, June 12, 2018 at 11:32:01 AM UTC-5, Anash P. Oommen (AdWords 
> API Team) wrote:
>>
>> Hi Greg,
>>
>> We need to update the Unique IDs documentation a bit, now that AdService 
>> is available. The more detailed version is like this:
>>
>> - AdId represents a globally unique creative ID. This means that you can 
>> edit an Ad using AdService using creativeId without any concern of ID 
>> collision.
>>
>> - AdGroupAd is a link that associates an Ad to an AdGroup. But we don't 
>> expose an AdGroupAdId. You could use the pair (adgroupid, adid) as a proxy 
>> ID for AdGroupAd. Hence our warning that when querying using 
>> AdGroupAdService.get, you should not consider adId to be a unique Id, you 
>> should rather use the pair (adgroupid, adid) as a unique pair.
>>
>> So, you are fine if you follow these guidelines:
>>
>> 1. When using AdGroupAdService.get, use (adGroupid, adId) as a unique ID 
>> for querying purposes.
>> 2. When using AdService.mutate, use adId as a unique ID for updating the 
>> ad.
>>
>> Hope this helps?
>>
>> Cheers
>> Anash P. Oommen,
>> AdWords API Advisor.
>>
>> On Tuesday, June 12, 2018 at 12:22:00 AM UTC-4, GregT wrote:
>>>
>>> Hi,
>>>
>>> I saw that in the recent v201806 release of the API, there is now the 
>>> ability to mutate ads. This would make some things simpler for us where 
>>> we're currently doing removal and adds to accomplish the same thing, so 
>>> it'd be nice to use it. However, I'm a little hesitant, because something 
>>> seems wrong about it. According to 
>>> https://developers.google.com/adwords/api/docs/guides/ad-features#mutating_ads_for_v201806_and_later,
>>>  
>>> you can mutate the Ad by using the new AdService, setting the id field of 
>>> the Ad, setting whatever fields you want to change, and sending it with the 
>>> SET operator. The part that worries me is that ad ids are not globally 
>>> unique, even within a single account, but are unique only within an ad 
>>> group (
>>> https://developers.google.com/adwords/api/docs/guides/objects-methods). 
>>> So, it seems unsafe and error prone to be able to modify an ad by 
>>> specifying just its id, as you could have more than one ad in your account 
>>> with that id, leading to modifying the wrong ad or an error (if the AdWords 
>>> API is checking for this and returning a SOAP fault for it)? Or am I 
>>> missing something?
>>>
>>> Thanks in advance,
>>> Greg
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 

Re: Can You Use The AdWords API To Access The Ad Preview & Diagnosis Tool?

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Brian,

It isn't. I can clarify your ask in the feature request.

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Monday, June 11, 2018 at 5:03:42 PM UTC-4, Brian Leonard wrote:
>
> Anash,
>
> I think the better feature is not the preview tool, but the diagnosis 
> portion, like below.  Is this diagnosis data available through the API?
>
>
> 
>
>
> Thanks!
> Brain
>
> On Friday, March 23, 2018 at 1:48:47 PM UTC-6, Anash P. Oommen (AdWords 
> API Team) wrote:
>>
>> Hi Syam,
>>
>> No, this feature is still not supported in AdWords API. Most developers 
>> end up building their own preview tool as a workaround, so we've kept this 
>> feature as lower priority.
>>
>> Anash P. Oommen,
>> AdWords API Advisor.
>>
>> On Thursday, March 22, 2018 at 1:54:20 AM UTC-4, syam...@synchroweb.com 
>> wrote:
>>>
>>> it's 2018 now...
>>> Google still not support ad preview??
>>>
>>>
>>>
>>> On Thursday, September 25, 2014 at 4:36:25 AM UTC+8, Robert O'Kruk wrote:

 Hello,

 I am wondering if you can use the AdWords API to access the data that 
 is provided from the AdWords Ad Preview & Diagnosis Tool?

 Any input is greatly appreciated.

 Thanks.

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/608bc7e0-e98d-4820-b896-34ef8d65b9d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Ids and mutating ads

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Greg,

We need to update the Unique IDs documentation a bit, now that AdService is 
available. The more detailed version is like this:

- AdId represents a globally unique creative ID. This means that you can 
edit an Ad using AdService using creativeId without any concern of ID 
collision.

- AdGroupAd is a link that associates an Ad to an AdGroup. But we don't 
expose an AdGroupAdId. You could use the pair (adgroupid, adid) as a proxy 
ID for AdGroupAd. Hence our warning that when querying using 
AdGroupAdService.get, you should not consider adId to be a unique Id, you 
should rather use the pair (adgroupid, adid) as a unique pair.

So, you are fine if you follow these guidelines:

1. When using AdGroupAdService.get, use (adGroupid, adId) as a unique ID 
for querying purposes.
2. When using AdService.mutate, use adId as a unique ID for updating the ad.

Hope this helps?

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Tuesday, June 12, 2018 at 12:22:00 AM UTC-4, GregT wrote:
>
> Hi,
>
> I saw that in the recent v201806 release of the API, there is now the 
> ability to mutate ads. This would make some things simpler for us where 
> we're currently doing removal and adds to accomplish the same thing, so 
> it'd be nice to use it. However, I'm a little hesitant, because something 
> seems wrong about it. According to 
> https://developers.google.com/adwords/api/docs/guides/ad-features#mutating_ads_for_v201806_and_later,
>  
> you can mutate the Ad by using the new AdService, setting the id field of 
> the Ad, setting whatever fields you want to change, and sending it with the 
> SET operator. The part that worries me is that ad ids are not globally 
> unique, even within a single account, but are unique only within an ad 
> group (
> https://developers.google.com/adwords/api/docs/guides/objects-methods). 
> So, it seems unsafe and error prone to be able to modify an ad by 
> specifying just its id, as you could have more than one ad in your account 
> with that id, leading to modifying the wrong ad or an error (if the AdWords 
> API is checking for this and returning a SOAP fault for it)? Or am I 
> missing something?
>
> Thanks in advance,
> Greg
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/e9109f68-3ba0-4f9d-9dd2-f57d67f69576%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AuthenticationError.CLIENT_CUSTOMER_ID_IS_REGUIRED

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi Joe,

All the services should have the fix in place as of last week. If you 
continue seeing this error, please update this thread and we will look into 
it.

Cheers,
Anash P. Oommen,
AdWords API Advisor.

On Tuesday, April 17, 2018 at 5:12:40 PM UTC-4, j...@tryadhawk.com wrote:
>
> We're still experiencing the issue on our end at this time. 
>
> Still receiving a 'CLIENT_CUSTOMER_ID_IS_REQUIRED' error even though it is 
> being passed in the SOAP body.
>
> Is there an ETA on a full fix? :( 
>
>
> On Thursday, April 12, 2018 at 3:18:04 PM UTC-4, Anash P. Oommen (AdWords 
> API Team) wrote:
>>
>> Hi Igor,
>>
>> This issue should be fixed already, are you still seeing errors? If yes, 
>> could you respond privately to send me a new SOAP request / response XML 
>> for a failing request?
>>
>> Cheers
>> Anash P. Oommen,
>> AdWords API Advisor.
>>
>> On Wednesday, April 11, 2018 at 11:55:46 AM UTC-4, Igor Shamin wrote:
>>>
>>> Dear support. When will it be possible to give an answer?
>>>
>>> вторник, 10 апреля 2018 г., 13:35:10 UTC+3 пользователь Igor Shamin 
>>> написал:

 Hi. We have a problem. We send a *request to ChampaignService*, we 
 receive a response
 *AuthenticationError.CLIENT_CUSTOMER_ID_IS_REGUIRED*
 I ask to help you figure it out. Thank you.

 Our request: 

  http://www.w3.org/2003/05/soap-envelope; xmlns:ns1="
 https://adwords.google.com/api/adwords/cm/v201802; xmlns:xsi="
 http://www.w3.org/2001/XMLSchema-instance;>  <
 ns1:RequestHeader xsi:type="SoapHeader"> >>> >__CUSTOMER_ID__ __DEVELOPER_TOKEN__
  __AGENT__ false
  false >>> ns1:RequestHeader><
 ns1:serviceSelector> Name Status>>> ns1:fields> BudgetId 
 BiddingStrategyId BiddingStrategyType>>> ns1:fields> BiddingStrategyName 
 Amount AdvertisingChannelType <
 ns1:fields>AdvertisingChannelSubType 
 TargetGoogleSearch TargetSearchNetwork>>> ns1:fields> TargetContentNetwork 
 TargetPartnerSearchNetwork BidCeiling>>> ns1:fields> BidType 
 EnhancedCpcEnabled PricingMode <
 ns1:fields>Settings  Name>>> ns1:field> ASCENDING  <
 ns1:paging> 0 500>>> ns1:numberResults>>>> env:Body>  


 Response: 

  http://schemas.xmlsoap.org/soap/envelope/;>  <
 ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201802
 "> 0005697bb2b6b6f00a37a7c1af0e8a4c >>> >CampaignService get >>> >1 51  >>> soap:Header>   soap:Client>>> > [AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED @ ; 
 trigger:'null']  >>> ="https://adwords.google.com/api/adwords/cm/v201802;> 
 [AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED 
 @ ; trigger:'null'] 
 ApiException http://www.w3.org/2001/XMLSchema-instance; xsi:type=
 "AuthenticationError">  null <
 errorString>AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED>>> errorString> AuthenticationError >>> >CLIENT_CUSTOMER_ID_IS_REQUIRED   
 



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/5d920eb1-3e3b-4885-be10-fa71a1cd02d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Many CANCELED for Batch jobs today

['Anash P. Oommen (AdWords API Team)' via AdWords API and Google Ads API Forum]

Hi,

The issue should be fixed at our end now. Could you continue monitoring at 
your end to see if more tasks are failing?

Cheers
Anash P. Oommen,
AdWords API Advisor.

On Wednesday, April 18, 2018 at 5:24:45 PM UTC-4, Ершов Александр wrote:
>
> Hello, Anash!
>
> A lot of jobs failing today
>  [14:00:22 18.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>  [14:00:27 18.04.2018] - [ADWORDS PUSHER]Batch job ID 717691209 has status 
> CANCELED. percents: 0
>
>  [13:57:48 18.04.2018] - [ADWORDS PUSHER]Batch job ID 717644287 has status 
> ACTIVE. percents: 9
>  [13:57:48 18.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>  [13:57:52 18.04.2018] - [ADWORDS PUSHER]Batch job ID 717644287 has status 
> ACTIVE. percents: 9
>  [13:57:52 18.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>  [13:57:56 18.04.2018] - [ADWORDS PUSHER]Batch job ID 717644287 has status 
> ACTIVE. percents: 9
>  [13:57:56 18.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>  [13:58:01 18.04.2018] - [ADWORDS PUSHER]Batch job ID 717644287 has status 
> ACTIVE. percents: 9
>  [13:58:01 18.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>  [13:58:07 18.04.2018] - [ADWORDS PUSHER]Batch job ID 717644287 has status 
> CANCELING. percents: 9
>  [13:58:07 18.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>  [13:58:11 18.04.2018] - [ADWORDS PUSHER]Batch job ID 717644287 has status 
> CANCELED. percents: 9
>
>
> On Thursday, April 12, 2018 at 10:52:23 PM UTC+3, Anash P. Oommen (AdWords 
> API Team) wrote:
>>
>> Hi,
>>
>> Thanks for confirming, I'll investigate.
>>
>> Anash
>>
>> On Thursday, April 12, 2018 at 3:30:13 PM UTC-4, Ершов Александр wrote:
>>>
>>> Hello, Anash P. Oommen!
>>>
>>> This error has came back today
>>>  [11:43:09 12.04.2018] - [ADWORDS PUSHER]Running handler of the adwords 
>>> push. account: TO queue: 2018-04-12 10:32:24
>>>  [11:43:10 12.04.2018] - [ADWORDS PUSHER]run 7241 operations
>>>  [11:43:14 12.04.2018] - [ADWORDS PUSHER]Uploaded 7241. operations for 
>>> batch job with ID: 713387427
>>>  [11:43:14 12.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>>>  [11:43:18 12.04.2018] - [ADWORDS PUSHER]Batch job ID 713387427 has 
>>> status ACTIVE. percents: 0
>>>  [11:43:18 12.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>>>  [11:43:22 12.04.2018] - [ADWORDS PUSHER]Batch job ID 713387427 has 
>>> status CANCELING. percents: 0
>>>  [11:43:22 12.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>>>  [11:43:27 12.04.2018] - [ADWORDS PUSHER]Batch job ID 713387427 has 
>>> status CANCELED. percents: 0
>>>  [11:43:27 12.04.2018] - [ADWORDS PUSHER]report : 
>>> {"SUCCESS":0,"FAILURE":29}
>>>
>>>
>>> On Tuesday, April 10, 2018 at 7:00:54 PM UTC+3, Anash P. Oommen (AdWords 
>>> API Team) wrote:

 Folks,

 We had an issue at our end that might have triggered this error. For 
 now, we rolled back the build, so errors should go away. If it continues, 
 feel free to ping this thread with specific job IDs and I'll investigate.

 Cheers
 Anash P. Oommen,
 AdWords API Advisor.

 On Tuesday, April 10, 2018 at 5:36:59 AM UTC-4, David Fishman wrote:
>
> Noticed this happening randomly since at least April 6. Re-submissions 
> were successful to batch service after waiting a few hours.
>
> On Monday, April 9, 2018 at 2:53:20 AM UTC-7, peey rity wrote:
>>
>> me to, please, helping me to fix this
>>
>> On Thursday, April 5, 2018 at 6:44:24 PM UTC-7, Ершов Александр wrote:
>>>
>>> Hello!
>>>
>>> We have received a number of CANCELED errors today.
>>> Batch job ID 707432799 has status 'CANCELED'.
>>>
>>> Processing error [0]: errorType=BatchJobProcessingError, trigger=, 
>>> errorString=BatchJobProcessingError.INTERNAL_ERROR,fieldPath=, 
>>> reason=INTERNAL_ERROR
>>>
>>> array(1) {
>>>  [0]=>
>>>  object(Google\AdsApi\AdWords\v201802\cm\BatchJobProcessingError)#49352 
>>> (7) {
>>>["reason":protected]=>
>>>string(14) "INTERNAL_ERROR"
>>>["fieldPath":protected]=>
>>>string(0) ""
>>>["fieldPathElements":protected]=>
>>>NULL
>>>["trigger":protected]=>
>>>string(0) ""
>>>["errorString":protected]=>
>>>string(38) "BatchJobProcessingError.INTERNAL_ERROR"
>>>["ApiErrorType":protected]=>
>>>string(23) "BatchJobProcessingError"
>>>   
>>>  ["parameterMap":"Google\AdsApi\AdWords\v201802\cm\ApiError":private]=>
>>>array(1) {
>>>  ["ApiError.Type"]=>
>>>  string(12) "ApiErrorType"
>>>}
>>>  }
>>> }
>>>
>>>  [18:38:18 05.04.2018] - [ADWORDS PUSHER]run 2840 operations
>>> [18:38:20 05.04.2018] - [ADWORDS PUSHER]Uploaded 2840. operations 
>>> for batch job with ID: 707158643
>>> [18:38:20 05.04.2018] - [ADWORDS PUSHER]Sleeping 4 seconds...
>>> [18:38:24 05.04.2018] - [ADWORDS PUSHER]Batch job ID 707158643 has 
>>> status ACTIVE. percents: 0
>>>