Keywords and sitelinks issue

93 views
Skip to first unread message

rafa....@rocketroi.com

unread,
Jun 8, 2017, 6:58:23 AM6/8/17
to AdWords API Forum
Hi

we have dealing with a very strange issue when creating structures on adwords massively. We are creating structures like this: Campaign (with extensions), AdGroup (with Extensions), Keywords, Ads

We are sending the operations to Adwords as follows:

BatchJobUploadStatus startingUploadStatus = new BatchJobUploadStatus(0, URI.create(url))
this.uploadResponse = helper.uploadIncrementalBatchJobOperations(aOperationList, lastUpdate, startingUploadStatus)

The problem is that in the case of a structure where one of the sitelinks extensions has not sitelink name (this is possible because we are getting the data dynamically from a feed), the related keyword with matching type "EXACT" is not created. 

The response from Adwords doesn't contain any error related to the keyword that has not been created. If you check the file (which is attached), you can see that there isn't any reference to the keyword in EXACT matching.  There are only error related to sitelinks extensions, what is normal because as I said before the sitelink name in some cases is empty.

They problematic keyword is 'Apartamentos chania'.

Has it something to do keywords and sitelinks?
509020171.results.xml

Sreelakshmi Sasidharan (AdWords API Team)

unread,
Jun 8, 2017, 3:14:58 PM6/8/17
to AdWords API Forum
Hi, 

Are you saying that, when a sitelink with a blank name and targeting a keyword is being created, the keyword is not getting created as the result of the same operation? As you said, the site link with no value for the 'siteLinkText' will throw an error StringLengthError.TOO_SHORT. If you try to create a sitelink with a valid name and targeting a keyword, it will still not create a keyword in the AdGroup. Instead the CampaignExtension will be created and it will target the specific keyword. If this is not the case, could you please try the same operation outside the Batch job and pass me the SOAP logs so that I get a clear picture of the scenario? 

You could use Reply privately to author while responding.

Thanks,
Sreelakshmi, AdWords API Team

rafa....@rocketroi.com

unread,
Jun 9, 2017, 5:04:25 AM6/9/17
to AdWords API Forum
Hi Sreelakshmi,

thanks in advance for your help

we are sure that the problem is not related to Batch Job as we have been able to create sitelink extensions. We have been created extensions filling all the data (not leaving any blank field) even in the case that I described you before, all the extensions and keywords has been created when all the data has been filled.

Besides that we have created extensions for an AdGroup, in an unitarily way.

So it seems  that something is going wrong with keywords (EXACT matching) when trying to create a sitelink with emtpy fields.

Trying to give you a clear picture of the scenario, it is something like this:



The third case (for instance) is where is ocurring the issue. Both the Sitelink text and the URL are blank and because that, we don't know why but the keyword with EXACT matching is not being created

Thank you!

rafa....@rocketroi.com

unread,
Jun 9, 2017, 8:12:46 AM6/9/17
to AdWords API Forum
Hi Sreelakshmi,

after doing more tests, we have acotated a litlle more the issue:
  • It doesn't matter if the extension being created is a Callout or a Sitelink.
  • We have found out that the keyword that is not created is the first one in the operations list, so it has nothing to do with matching option but with position on operation list.
Following you can see a sample of our operationList (only 2 operation are shown)

 00 = {BudgetOperation@53695} 
 01 = {CampaignOperation@53696} 
 02 = {CampaignCriterionOperation@53697} 
 03 = {CampaignCriterionOperation@53698}
 
 04 = {AdGroupOperation@53699} 
 05 = {AdGroupExtensionSettingOperation@53700} 
 06 = {AdGroupExtensionSettingOperation@53701} 
 07 = {AdGroupCriterionOperation@53702} 
 08 = {AdGroupCriterionOperation@53703} 
 09 = {AdGroupCriterionOperation@53704} 
 10 = {AdGroupCriterionOperation@53705}
 
 11 = {AdGroupOperation@53706} 
 12 = {AdGroupExtensionSettingOperation@53707} 
 13 = {AdGroupExtensionSettingOperation@53708} 
 14 = {AdGroupCriterionOperation@53709} 
 15 = {AdGroupCriterionOperation@53710} 
 16 = {AdGroupCriterionOperation@53711} 
 17 = {AdGroupCriterionOperation@53712}

The problem occurs with the first keyword after a failed extension, e.g.

{AdGroupExtensionSettingOperation@53701} --> Failed (StringLengthError.TOO_SHORT)
{AdGroupCriterionOperation@53702} --> Not created, but not error shown
{AdGroupCriterionOperation@53703} --> Created

Hope it helps!

pedro....@rocketroi.com

unread,
Nov 28, 2017, 4:52:14 AM11/28/17
to AdWords API Forum
Hi Sreelakshmi,

I am currently in charge of this issue.
Could you please update me on the current status.
The last update I have is that you were going to escalate the issue to the IT team.

Thank you,
Pedro Alegre

Sreelakshmi Sasidharan (AdWords API Team)

unread,
Nov 28, 2017, 10:59:49 AM11/28/17
to AdWords API Forum
Hi Pedro, 

The summary of discussions so far is that: we were able to reproduce the issue on our side. Currently, our engineering team is looking into fixing the issue. We are following up with the engineering team and I will keep you posted as soon as I hear back from them. 

In the meantime, since the issue occurs only when you pass an invalid/incomplete input to the AdGroupExtensionSettingOperation in the batchJobService, you could make sure that the inputs are correctly set and avoid the failure of any other operations in the same batchJob because of this failure.
Reply all
Reply to author
Forward
0 new messages